Hi Not sure i get it. There is no link between deployment id of the ejb and connection number.
The topic name (and type BTW) are activation properties you can configure whatever EJB name you use. Is that your case? N different MDB listening the same topic? Then forcing the destination name and type should work Le 5 févr. 2017 05:01, "Dignesh" <[email protected]> a écrit : Hi, I have a cluster set up with TomEE 7.0.2 with 3 nodes. I have a MBD (MyTopic) deployed on all the 3 nodes. What I have observed is Each MDB (MyTopic) that is deployed to a server instance in cluster environment creates a single JMS connection. - This is due to the unique deployement id we assign to the bean.So when a JMS message is raised, all the MDB's deployed in each node receives the message. So Is it possible to replicate the message on all nodes for some topics which are deployed ? I was able to do it by having same clientID assigned to the MDB in all nodes. - is this is correct ? OR is there any cleaner way to acheive this. With the above approach I am seeing the alreadyconnected exceptions in the log.. can this be ignored . OR is there any better way to address this usecase. P.S. I dont want to use Queues :) Thank you very much. -- View this message in context: http://tomee-openejb.979440. n4.nabble.com/Deploy-MDB-topic-in-non-clustered-way-tp4681016.html Sent from the TomEE Dev mailing list archive at Nabble.com.
