AMQ uses org.apache.activemq.util.IdGenerator, normally it should be unique excepted if forced with the same value on multiple instances in ActiveMQResourceAdapter (Clientid=xxx) . This is not the case by default so not sure where you get the MDB name from. If you can share your setup to let us reproduce quickly it should be easily solvable from org.apache.openejb.resource.activemq.ActiveMQResourceAdapter
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-04-20 18:44 GMT+02:00 hwaastad <[email protected]>: > I'll be damned.... > That was it! > > This actually solves quite an issue I have. > I'm deploying topic MDBS in a network of brokers and as long as every MDB > is > on a separate broker its working however when a failover situation occurs, > the clientid issue appears. > > Thanks alot. > > BTW, I've noticed that weblogic has an generate-unique-jms-client-id > property...where would that possibly fit the pussle? > > br hw > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/JMS-Topic-MDB-tp4674499p4674529.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
