Failed ESB Process is Not Retryable (Doc ID 1169343.1)

Last updated on AUGUST 30, 2010

Applies to:

Oracle ESB - Version: 10.1.3.1 to 10.1.3.5 - Release: AS10gR3 to
Information in this document applies to any platform.

Symptoms

In case of any fault or exception on a synchronous BPEL process which is invoked by a synchronous ESB routing service, the message is not retryable in ESB.  The fault can be simulated by changing the password in the connection pool which will be used by BPEL to insert data into a database table as follows:

1) Create and Publish/Subscribe model where the publisher puts the data into an AQ.
2) A synchronous ESB consumes the data from AQ and invokes a synchronous BPEL process.
3) The synchronous BPEL process inserts the data received from ESB into a table.
4) Make sure that the BPEL fails to insert data into the table.

Whenever the failure happens the ESB instance must be retryable rather than non-retryable in the ESB console.  It is noticed that the ESB instance is not retryable.

Cause

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