Hi,
Using 5.7.0 I find that the problem exists in the following way:
2 brokers connected via network.
Broker A
has consumer connected to a /queue/foo.test
Broker B
has a producer connected to /queue/foo.test
the producer is producing message for /queue/foo.test and the consumer will
receive them just fine. The producer is configured to stuff messages into
the queue one after the other, the consumer on purpose consumes messages
slowly.
Once we have several hundred messages in /queue/foo.test we abort the
producer and consumer.
Looking at queue sizes on both brokers, broker A has a large number of
messages and broker B has some number of messages or none.
Take the consumer that was previously talking via broker A and connect him
to broker B. That consumer will now only see the messages that are in broker
B and will NOT receive ANY of the messages stuck in broker A.
The only way I can get out of this problem is to restart both brokers and
all messages are then process correctly.
I have spent quite a bit of time on this problem and if there is only one
broker this is not a problem - the moment you have a network of 2 brokers
this problem exists.
Here are my network connectors, one for topics and one for queues:
<networkConnectors>
<networkConnector name="net-node1-node2-queues"
uri="static:(ssl://activemq-node2.amherst.edu:61615)"
networkTTL="3"
dynamicOnly="true"
prefetchSize="1"
duplex="false"
userName="${netlink.username}"
password="${netlink.password}"
conduitSubscriptions="false"
>
<dynamicallyIncludedDestinations>
<queue physicalName=">"/>
</dynamicallyIncludedDestinations>
</networkConnector>
<networkConnector name="net-node1-node2-topics"
uri="static:(ssl://activemq-node2.amherst.edu:61615)"
networkTTL="3"
dynamicOnly="true"
prefetchSize="1"
duplex="false"
userName="${netlink.username}"
password="${netlink.password}"
conduitSubscriptions="false"
>
<dynamicallyIncludedDestinations>
<topic physicalName=">"/>
</dynamicallyIncludedDestinations>
</networkConnector>
</networkConnectors>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Stuck-messages-Dispatch-issues-tp2367852p4661679.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
