AQ - JMS adapter: messages are not getting destroyed after dequeue
Last updated on AUGUST 23, 2013
Applies to:Oracle(R) BPEL Process Manager - Version 10.1.2.2 to 10.1.3.5.0
Information in this document applies to any platform.
***Checked for relevance on 04-Apr-2011***
You have a process flow that looks like:
BPEL1 -> JMS ADAPTER1 -> AQ -> JMS ADAPTER2 -> BPEL2
Messages are successfully enqueued by process BPEL1 and successfully dequeued by process BPEL2. However, messages are not removed from the queue after the successful dequeue and sometimes messages can be dequeued and processed more than once, resulting in duplicate transactions.
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