How to achieve singleton behaviour with MDB deployed in cluster?
Issue
- A MDB is deployed in a JBoss EAP two node cluster and bound to a topic. When a message is published on the topic it triggers the MDB on all cluster nodes. This is unnecessary since it is duplicating the business logic. How to stop it?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7.2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.