I have applications A and B running in two different instances of Resin.
Each has a broker.
Application A puts messages onto a distributed queue and application B
consumes the messages using message driven pojo's. Both are configured
using Spring 2.0
What we've found is that when we stop Application B and then start it up
again(which starts up its broker)
messages no longer get through until I restart application A.
Our network connector config for broker in application A was as follows:
<amq:networkConnectors>
<amq:networkConnector uri="static://(tcp://url-of-broker-in-app-B)"
failover="true"
name="NotificationsBridge"
dynamicOnly="false"
conduitSubscriptions="true"
decreaseNetworkConsumerPriority="false">
</amq:networkConnector>
</amq:networkConnectors>
Then i saw this posting
http://www.nabble.com/Disconnection-and-reconnection-in-a-network-of-brokers-tf2704774.html#a7582937
so I tried changing failover to false
<amq:networkConnectors>
<amq:networkConnector uri="static://(tcp://url-of-broker-in-app-B)"
failover="false"
name="NotificationsBridge"
dynamicOnly="false"
conduitSubscriptions="true"
decreaseNetworkConsumerPriority="false">
</amq:networkConnector>
</amq:networkConnectors>
And amazingly this did the trick. Now if I application B goes down for a
time and application A continues to put message on the queue and then
application B comes back up the two brokers synch up as expected.
In the thread listed above they talk about potentially reporting this issue
as a bug. Is this a known issue? I haven't found anything yet. Any ideas
why this might be happening?
--
View this message in context:
http://www.nabble.com/Failover-not-working-with-distributed-queue-tf3176112.html#a8812231
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
