JMS Bridges Failing to Forward Messages in WebLogic Server 12c
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 12c]
Information in this document applies to any platform.
JMS bridges fail to forward messages to other domains in WebLogic Server 220.127.116.11.0. The same functionality was successfully implemented in WebLogic Server version 18.104.22.168.0.
- Source Environment WLS Version 22.214.171.124.0 to Target Environment WLS Version 10.3.6.0.13 -> Messages getting forwarded.
- Source Environment WLS Version 126.96.36.199.0 to Target Environment WLS Version 10.3.6.0.13 -> Messages not getting forwarded.
The bridge's source destination is correctly configured, by making sure that the following fields on the JMS Bridge Destination Configuration console page have been properly completed: Connection URL, Destination JNDI Name, Connection Factory JNDI Name. The actual source queue or topic destination mapped to the source bridge destination is running and healthy.
However, the console shows the Queue state as Inactive and throws a Warning: Failed to connect to the target. The logs show the following warnings:
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