Resolve Message Time Out Errors

The following errors can occur during both design time (in both the inbound and outbound directions) and runtime.

  • Message not received within X seconds of wait interval

    There can be multiple reasons for a time out occurring, such as connectivity issues between Oracle Integration and the connectivity agent or the connectivity agent being disabled. Ensure that the connectivity agent is up and running if you see this error. Check the status of the agent under Dashboards > Agents in Oracle Integration.

    Note:

    When using the adapter to connect to an Oracle E-Business Suite database instance and this error continuously occurs, review the SQL query plans and other SQL tuning aspects. The adapter relies on JDBC driver APIs to fetch metadata such as table details, stored procedure details, and so on. This involves execution of certain SQL queries by the JDBC driver involving SYS tables such as the ALL_TYPES table. Since Oracle E-Business Suite has a large data dictionary, these metadata queries requires tuning consideration to improve overall performance of the adapter.
  • SQLState: 08006 errorCode: 17002 message: IO Error: Connection timed out

    This error can occur when database sessions are terminated by a network firewall or some other reason. The adapter automatically recovers during this state and new connections are created. However, a few requests using old connections may time out. Ensure that the firewall is not terminating idle connections.

  • Timeouts can also occur due to design problems. Avoid certain antipatterns. For example, do not explicitly update the same table as an invoke operation when the same table is getting polled on the trigger side.