The id needs to be unique per Connection from the same host to the same topic
http://www.tomitribe.com - @AndyGeeDe - On a small screen device. On 20 Apr 2015 15:02, "Romain Manni-Bucau" <rmannibu...@gmail.com> wrote: > doesnt jms.clientId=myId works in the broker uri? > > > 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 14:27 GMT+02:00 Andy Gumbrecht <agumbre...@tomitribe.com>: > > > Traveling atm, but seem to recall that there's a way to override the > > activemq generation. Focus search there. > > > > http://www.tomitribe.com - @AndyGeeDe - On a small screen device. > > On 20 Apr 2015 13:51, "hwaastad" <he...@waastad.org> wrote: > > > > > Hi Andy and thx for answering. > > > > > > I've started to realize that. > > > > > > Made simple test using same code and maven profiles for different tomee > > > containers. > > > > > > Switching clientId on MDB makes it work. > > > Now, how to solve the clientId issue? > > > > > > I tried adding an clientId option in tomee.xml resourceadapter config, > > but > > > that does'nt seem to work. > > > > > > Got any recommendations on how to solve this? > > > > > > br hw > > > > > > > > > > > > > > > -- > > > View this message in context: > > > > > > http://tomee-openejb.979440.n4.nabble.com/JMS-Topic-MDB-tp4674499p4674502.html > > > Sent from the TomEE Users mailing list archive at Nabble.com. > > > > > >
