Hi All,
We are currently having issues with a MDB application deployed to a gf-v2ur1 application server cluster which uses a REMOTE JMS 2-broker MQ cluster configuration (non-ha). Both connection factories and destinations are replicated in the MQ cluster. Specifically we see behavior that when the application is deployed, it will set up MDB listeners on the brokers in an unbalanced manner. Sometimes one broker will have all the MDB listeners for a given destination, and another broker won't get any. However messages are still being sent to the destination without an MDB listener, and this results in queues with messages that never get processed.
Are there any ways to induce the glassfish EJB container to guarantee that all brokers in a MQ cluster have at least one MDB listener for every destination resource?
Cheers,
-J
[Message sent by forum member 'jmetcalf' (jmetcalf)]
http://forums.java.net/jive/thread.jspa?messageID=272553