Message-Driven Bean (MDB) Not Discovering All Uniform Distributed Queue (UDQ) Members Via Foreign JMS When Members Start After MDB
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.4 and later
Information in this document applies to any platform.
A Message-Driven Bean (MDB) is not discovering all Uniform Distributed Queue (UDQ) members via foreign JMS when the members start after the MDB.
Steps to reproduce
- There are two domains, JMS cluster and JMS client.
- The JMS Cluster has the physical UDQ and the JMS Client has the Foreign JMS Server, where the CF and UDQ are mapped.
When the JMS Server starts after the MDB is started, then the MDB will only ever discover one of the members and will never attempt to connect to all of the members. When the JMS Server is started before the MDB, then the MDB is able to discover the members.
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