JMS Adapter Is Publishing Message With JMS Correlation ID
(Doc ID 1371425.1)
Last updated on OCTOBER 30, 2019
Applies to:Oracle(R) BPEL Process Manager 10g - Version 10.1.3.5.0 and later
Information in this document applies to any platform.
You are using a BPEL process to publish JMS messages to a queue. Although you are not setting any correlation id, you observe that there is, in fact, a correlation id in the JMS message header. It seems that the JMS adapter is setting a correlation id by default when the message is published.
Since the JMS Adapter is setting the correlation id in the JMS message, the consumer process is delayed at least 2.5 seconds due to <Bug 11795408> and <Bug 11805364>. (See <Note 1301955.1>.)
Where is this correlation id coming from? And can you configure the adapter so that there is no correlation id added when the message is published?
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