Wrong Co-ordinator URL Formed Due to t3 Outbound Enabled Checked on Target Giving "Cannot obtain Coordinator" Error

(Doc ID 2310523.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.

Symptoms

JMS Bridges are in forwarding state. While posting messages, the error below is seen in the logs and the messages are in Pending state (receive-transaction):

####<30-Aug-2017 12:49:17 o'clock BST> <Debug> <JTANaming> <hostname> <managed1_tstsmart> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <BEA1-0002D98BDD7594F8506D> <> <1504093757151> <BEA-000000> <java.lang.Exception: DEBUG: ServerCoordinatorDescriptor.getOrCreate(managed4_rcdesb24+xx.xx.xx.xx:yyyy+rcdesb24+t3+)

 

Full stack trace is as below:


yyyy is the target server t3 channel port.

Changes

 

Cause

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