The issue will be classloading, a war is supposed to be self contained, so it should contain the activemq classes. If the activemq classes are shared, part of the container system libraries and not contained in the war, then the vm transport should work across wars. The vm transport keeps track of servers in a static map, so this map needs to be shared across the wars to be visible.
On 10 August 2010 20:26, cmdr <spc...@yahoo.fr> wrote: > > Hi > > Is it possible to configure the communication between two war using activeMq > VM protocol. > > I try vm://localhost?create=false for one war and vm://localhost for the > second war but that does not work. The firts war is not able to connect to > the broker. > > Regards > -- > View this message in context: > http://old.nabble.com/VM-communication-between-two-war-tp29401361p29401361.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
