JTA Transaction Timeout
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
WLS 12.1.3 - JMS client
OSB 220.127.116.11 (WLS 10.3.6) -- JMS Server side
WLS 12.1.3 (acting as a JMS client)------(t3s)------>Firewall--------(t3s)------->OSB 18.104.22.168 (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:
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