Don't think that is strictly true about client id as it must be unique from the same host
http://www.tomitribe.com - @AndyGeeDe - On a small screen device. On 20 Apr 2015 09:50, "hwaastad" <[email protected]> wrote: > Hi, > I've startet to play around clearing jcs cache on multiple installations > using a JMS topic. > It's non-durable. > I've seen that clientId is only needed for durable topic. > > However, I see that if I have two webapps deployed(having a MDB), activemq > complains about: > javax.jms.InvalidClientIDException: Client: WebCacheMdb already connected > from.... > > The MDB has: > @MessageDriven(activationConfig = { > @ActivationConfigProperty(propertyName = "destinationType", > propertyValue = "javax.jms.Topic"), > @ActivationConfigProperty(propertyName = "destination", propertyValue = > WebConstants.WEB_CACHE_TOPIC), > @ActivationConfigProperty(propertyName = "maxSessions", propertyValue = > "1") > }) > > Having a two broker network I also have an issue with messages delivered > twice, but that might be solved by using virtualtopics. (maxsessions has no > effect) > > If someone have an idea, please let me know :-) > It might be that I'm not too familiar with topics. Queues is working fine. > > br hw > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/JMS-Topic-MDB-tp4674499.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
