Message is sent to wrong broker
-------------------------------
Key: AMQ-2331
URL: https://issues.apache.org/activemq/browse/AMQ-2331
Project: ActiveMQ
Issue Type: Bug
Components: Broker, Connector, Selector
Affects Versions: 5.2.0
Environment: All
Reporter: Pradeep G
Priority: Critical
I have network of brokers configured in Hub/Spoke topology. The Spokes are
connect to the Hub via duplex network connector. Am using only Queues, and
there are same set of Queues on both the Hub and the Spokes. Each of the
Queues on the Spokes have only one consumer, and the consumer subscribes to
messages based on a selector. The selector field is the Spoke ID. The Hub
transmits messages by setting the message selector to the Spoke ID.
The issue am facing is as follows. I have two Spokes A and B, and connect to
a Hub say H via duplex network connector. Most times this setup works fine,
but some times the messages meant for A are sent to B and vice-versa.
Here is what I found in the logs:
2009-07-24 15:48:21,054 DEBUG [org.apache.activemq.store.amq.AMQMessageStore]
[ActiveMQ Transport: tcp:///127.0.0.1:53209]: Journalled message add for:
ID:pgopal-lt-53198-1248427143033-2:6:1:97:27, at: offset = 1032207, file = 1,
size = 444, type = 1
2009-07-24 15:48:21,057 DEBUG [org.apache.activemq.store.amq.AMQMessageStore]
[ActiveMQ Task]: Doing batch update... adding: 1 removing: 0
2009-07-24 15:48:21,057 DEBUG [org.apache.activemq.store.amq.AMQMessageStore]
[ActiveMQ Task]: Batch update done.
2009-07-24 15:48:21,062 DEBUG [org.apache.activemq.store.amq.AMQMessageStore]
[ActiveMQ Transport: tcp:///172.17.0.58:2673]: Journalled message remove for:
ID:pgopal-lt-53198-1248427143033-2:6:1:97:27, at: offset = 1032651, file = 1,
size = 285, type = 1
2009-07-24 15:48:21,062 DEBUG [org.apache.activemq.store.amq.AMQMessageStore]
[ActiveMQ Task]: Doing batch update... adding: 0 removing: 1
2009-07-24 15:48:21,062 DEBUG [org.apache.activemq.store.amq.AMQMessageStore]
[ActiveMQ Task]: Batch update done.
The message was meant for a consumer in the broker running on machine
172.17.0.59, whereas the message is being removed from 172.17.0.58 (line 4).
Is there a workaround ?
Thanks,
Pradeep
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
