BPM 12.1.3: Event Not Handled By Mediator In Its Own Transaction With Consistency 'guaranteed'

(Doc ID 2201727.1)

Last updated on JANUARY 04, 2017

Applies to:

Oracle Business Process Management Suite - Version and later
Information in this document applies to any platform.


Problem Summary
BPM 12.1.3: event not handled by Mediator in its own transaction with consistency 'guaranteed'

Problem Description
There is a Mediator that is subscribed to an event with consistency level 'guaranteed'. According to the documentation the behavior should be like this: "Events are delivered to the subscriber asynchronously without a global transaction. The subscriber can choose to create its own local transaction for processing, but it is committed independently of the rest of event processing.".

According to us this means that the event should be handled, and its transaction successfully ended, even when the transaction of the publisher is rolled back. However this is not what we see happening. When the transaction of the publisher is rolled back the event is not handled either. We also tried with consistency level 'one and only one'. Apart from this not being an acceptable level, this also appears to rollback. We therefore consider this to be a bug.

Because the event is used for some custom logging solution, it is important that events are processed even when the publisher's transaction is rolled back.


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