I have a situation that we have a web app/the JMS publisher, and a MDB the subscriber, both deployed into a glassfish cluster. The MDB should consume the JMS message only ONCE. But with the current deployment configuration, which is with JMS resources running in EMBEDDED mode, we observe the JMS messages are consumed multiple times.
- My question is how would I enable only one MDB in the cluster?
- If MDB failover is not a concern, is it possible to deploy the MDB in the standalone instance, and let it subscribe to the topic in the JMS brokers in the cluster? How to configure this?
- If I set the client_id for the MDB, then all MDB instances would be considered the same? In this case, would only one MDB instance consume the same message at a time?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Need messge to be consumed once by MDB deployed in a glassfish cluster?