How to Force Message Ordering in an ESB Service in an Error Scenario (Doc ID 731430.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle ESB - Version: 10.1.3.3
Information in this document applies to any platform.

Goal

Describe how to enforce message ordering in an ESB service in an error case.

Use this scenario as an example:
1.  A polling DB adapter initiates an ESB process by consuming a row from the database tables.
2.  The message is going to the ESB_JAVA_DEFERRED queue (perform asynchronous call).
3.  Due to a network or hardware failure the database (here and after we will call it DB1) is not available
(the ESB process performs a PL/SQL procedure call in order to gather the required data).
4.  ESB instance fails at step 3.
5.  The database DB1 becomes available.
6.  The consequent message from the polling DB adapter is consumed, passes through the ESB_JAVA_DEFERRED queue and then comes the error due to this message.  The error message depends on the message from step 3.

The idea is that at the Step 3 the ESB message processing should be stopped until the message is resubmitted successfully.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms