JMS Messages Are Stuck in Receive Transaction State
Last updated on JUNE 16, 2017
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
Two Weblogic domains are configured and they participate in global transaction using JTA.
In domain1 Weblogic has JMS queues configured and Golden Gate publishes JMS messages to the queues. In domain2 Oracle Service Bus (OSB) proxy service consumes those messages and then route them to business services in OSB.
XA Connection factory is used in Domain2 and its transaction manager maintains a global transaction and co-ordinates with all XA enabled endpoints in the flow including data sources configured for data retrieval and storage. The Transaction manager will let end systems know whether it has to commit or rollback the transaction.
Intermittently JMS messages shows as Receive Transaction in Domain1 when monitoring the JMS queues via the Admin Console. The messages remain in such state and are not getting cleared until all the participants in the transaction have been restarted. See screenshot below:
There are no obvious errors in the Weblogic server with the JMS queues configured in Domain1. But in Domain2 where OSB is deployed the Weblogic server logs has the following error:
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