JTA Transaction Timeout
(Doc ID 2178267.1)
Last updated on MAY 08, 2023
Applies to:
Oracle WebLogic Server - Version 10.3.6 and laterInformation in this document applies to any platform.
Symptoms
WLS 12.1.3 - JMS client
OSB 11.1.1.6 (WLS 10.3.6) -- JMS Server side
WLS 12.1.3 (acting as a JMS client)------(t3s)------>Firewall--------(t3s)------->OSB 11.1.1.6 (WLS 10.3.6)
Cluster of 8 managed servers (JMS Distributed Queue). JMS Server has Filestore. Two different JMS client domains (on different hosts) with exact same domain name, server names and port are configured. Only one client domain is active at any given point of time.
When the switch from one JMS client domain to another happened, in production environment, even for a single message transfer from client to server, the transaction is timed out. See the following in the server side logs:
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 |