ah ok, my mistake. Wonder if it is a classloading issue then, both of the webapps having their own activemq jars and seeing their own broker registry so both creating a broker. You may want to push the activemq jars into the tomcat lib directory so they are shared.
On 3 September 2010 09:48, jsvaughan <jsvaug...@gmail.com> wrote: > > Would that result in both my applications waiting for the broker to start > though (and just postpone the problem)? I only have vm:localhost defined > once, in the brokerurl of the connectionfactory found by jndi. > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Want-one-broker-two-turn-up-tp2525279p2525323.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com Open Source Integration http://fusesource.com
