My Oracle Support Banner

OnAlarm in Cluster environment trigger transaction rollback when Callback return to the second node (Doc ID 1629312.1)

Last updated on OCTOBER 27, 2021

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


Running in a clustered environment, project contains a pick with an OnAlarm that waits for "onResult" for an Asynchronous callback.  This process is triggered on node 1.

Scenario 1: The Asynchronous callback is returned to node 1

    The process completes without errors and no rollbacks are observed.

Scenario 2: The Asynchronous callback is returned to node 2 

    The process completes and is marked as completed.  However, after the OnAlarm expires (on node 1) the following error is logged, the transaction is rolled back and the instance status is marked as faulted.

        "The transaction was rolled back. The work performed for bpel instance "ID_INSTANCE" was rolled back to the previous dehydration point"

The OnAlarm on node 1 seems to be waiting for a response (like in a synchronous call) and does not get the response, which triggers the issue.

No faults are logged in the Audit trail and it has not been marked (i.e. no red mark)


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.