IP_IN_QUEUE Using B2BERRORUSER doesn't Return the Correct MessageID
Last updated on JANUARY 26, 2018
Applies to:Oracle SOA Platform - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Customers are observing that in certain scenarios the exception message enqueued to IP_IN_QUEUE is referring to the ack instead of the original request whereas if we query the B2B runtime data then it refers to the id correctly.
Expected Behavior - Exception message being passed to back-end must refer to the failed request instead of the ack
Observed Behavior - Exception message being passed to back-end is referring to the ACK instead of failed request
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