Last updated on SEPTEMBER 09, 2017
Applies to:Oracle Service Bus - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, OSB Core Functionality
Messages produced by OSB are stuck in a pending state and an OSB consumer process is unable to consume.
Using OSB 18.104.22.168
Scenario : OSB Business Service posting a message to a WebLogic JMS Queue using JMS Transport.
Another OSB Proxy service is consuming the message from the same queue using the JMS Transport.
When the consumer service is active the messages are going to pending state(with transaction status as -start transaction-)and the consumer is not consuming the message from the queue.
If the consumer service is down then the message posted by the sender service properly going to the current message list.
In the producer process if we set the QualityOfService as BestEffort then consumer is able to consume messages. But there are many duplicate messages are getting created. Some of them going to pending message list and some of them going to current message list.
The issue is only occuring when the JMS queue is hosted on a remote server.
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