Periodic Messages Canceled on Delivery Message Table (orabpel.DLV_MESSAGE) in High Availability (Doc ID 748430.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version 10.1.3.3 and later
Information in this document applies to any platform.

Symptoms

In a BPEL High Availability (HA) environment some messages that need to be consumed by BPEL end up in a canceled state (state 3 in the orabpel.DLV_MESSAGE table) and are never processed by the entire BPEL flow resulting in lost messages.

When this happens the following error is in the $ORACLE_HOME/bpel/domains/<domain name>/logs/domain.log:

:<2008-09-29 10:01:22,834> <ERROR> <b2bsecuresync.collaxa.cube.engine.delivery>[WorkExecutorWorkerThread-4] <DeliveryService::handleCallback> Activity for conversation MD5{eec964adaed2fc69507fbdcba97646ce} has been closed ... marking message 7388a14974ab67de:-75eb34cf:11cac140a2f:-5104 as cancelled, subscriberId= bpel://localhost/b2bsecuresync/SendEnrollmentBatchB2BProvABCSImpl~1.0/891391-BpOMs0-BpPDB0.9-1
 


This error comes out but does not stop the process. 

As already stated, you will see canceled state 3 messages in the orabpel.DLV_MESSAGE table. 

In an example use case:  you use a database adapter to make inserts into a table for each message received.  Since messages are being canceled and lost by BPEL, the table that should be updated is missing rows that should have been inserted by the BPEL process.


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