JMS Messaging Dynamic Port Causes Error "Could not register a DisconnectListener for XXX"
Last updated on DECEMBER 11, 2017
Applies to:Oracle Weblogic Server - Version: 10.3
Information in this document applies to any platform.
There are two domains: domain A on Tomcat and domain B on WLS. These domains communicate with one another using a JMS message queue for message transactions through a firewall between them. When domain A sends a message request to Domain B, the request goes through using t3://servername:port and it is successful. However, intermittently the server on Domain B is trying to open a connection back to the client, thus using variable ports. Since there is a firewall between the two domains, this connection is getting dropped, as there are a fixed number of available ports which are opened through the firewall. This issue can occur with any client that is trying to communicate with WebLogic Server via JMS through a firewall.
In these situations, we observe the following error on the client:
Caused by: weblogic.rmi.extensions.DisconnectMonitorUnavailableException: Could not register a DisconnectListener for [Delegate(1280084020) [weblogic.iiop.IOR[RMI:weblogic.messaging.dispatcher.DispatcherImpl:0000000000000000] @10.1.111.100:12345, <0, null>]]
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