Transaction Fails with javax.transaction.SystemException: Could Not Contact Coordinator
(Doc ID 2778791.1)
Last updated on JUNE 10, 2024
Applies to:
Oracle WebLogic Server - Version 12.2.1.3.0 to 14.1.1.0.0 [Release 12c]Information in this document applies to any platform.
Symptoms
SOA Business Service puts a messages in Request Queue (UDQ) the message then transferred to IBM MQ. The message has order details.
Order gets processed at MQ end and the response message corresponding to the order placed on the Response Queue (UDQ) in the OSB domain.
The same SOA Business Service consumes the message from the ResponseQueue.
It is observed that the messages in the Response Queue remain in send transaction expired or receive transaction expired state.
This is pointing to that SOA Business Service unable to send the acknowledgement back to the JMS Server that hosts the Response Queue.
The Request Queue (UDQ) and Response Queue (UDQ) targeted to a cluster of 2 managed server in the OSB domain.
Issue only happens when both the managed servers in the cluster are up & Running.
If only one of the managed server is running then issue does not happen.
Below is the exception:
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |