Your problem might be that the two brokers are in a network of brokers
due to this line
in the configuration (discovery via multicast).
However your config for broker B shouldn't do multicast discovery, but still..
Else you'll need to use jms/QueueConnectionFactory for all operations
related t
48|org.apache.activemq.broker.region.AbstractRegion|||Adding
destination: queue://QueueOne
which apparently the queue client subscribes to, instead of the queue on
BrokerA.
How can I prevent this?
Thanks.
--
View this message in context:
http://www.nabble.com/queue-connecting-to-wrong-broker.-t
