MDB connection failure when local and remote destination JNDI names are same while using foreign JMS Server
(Doc ID 1114003.1)
Last updated on FEBRUARY 08, 2019
Applies to:Oracle WebLogic Server - Version 10.0 to 10.0
Information in this document applies to any platform.
The MDB connects to a local destination of the same name when the remote destination server is down.
Server-A (in Domain-A) has a foreign JMS Server to Server-B (in Domain-B). Server-A has a topic/queue destination with the same JNDI name in a remote topic/queue destination which is used in the foreign JMS Server. The MDB deployed to Server-A uses the foreign JMS Server. The MDB is connected to the remote topic/queue while Server-B is running. Whenever server-B is stopped, the MDB is connected to the local topic/queue which is available with the same JNDI name. The MDB reports a LostServerException and PeerGoneException nested with SocketResetException: however, its status is "connected and running."
The MDB does not reconnect back to the remote destination even after the remote server is running and reachable. Server-A must be restarted so that the MDB connects back to the remote destination.
In summary, the issue is that the MDB connection falls back to the local JNDI whenever the remote JNDI is lost abruptly, This happens when the local destination's JNDI name and the remote destination's remote JNDI name is the same.
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