hi,
I confirm is two the same message, because their message id is the same, is not 
only the message content is the same, there is no test of other ways to store, 
because my way is to use a zookeeper + leveldb deployment, when because of 
dirty data, leading to the master node and slave node frequent switching, there 
will be a lot of this kind of duplicate messages, four consumers, two or three, 
even four consumer receives the message with the same message id, and the 
receiving time difference about 1 ms


原始邮件
发件人:Tim [email protected]
收件人:ActiveMQ [email protected]
发送时间:2017年9月11日(周一) 21:51
主题:Re: Message repetition consumption:Four consumers consume the same queue 
message, with two consumers receiving the same message at the same time, 
receiving a gap of 1ms


Also, I'd want to know if the two messages had the same JMSMessageID (i.e. were 
they the same message, or were they two different messages with the same 
content). On Sep 11, 2017 7:50 AM, "Tim Bain" [email protected] wrote:  Do 
you see the same behavior if you switch to KahaDB or JDBC? As Tim Bish  said on 
that JIRA bug, LevelDB is no longer supported, so you're only going  to get a 
fix if you can demonstrate that it's still a problem if you switch  to one of 
the supported store types.   Tim   On Sep 11, 2017 7:05 AM, "youngzil" 
[email protected] wrote:   hi,all:  Does anyone have this problem:  Summary: 
Message repetition consumption:Four consumers consume the same  queue message, 
with two consumers receiving the same message at the same  time, receiving a 
gap of 1ms Key: AMQ-6807 URL:  https://issues.apache.org/jira/browse/AMQ-6807  
broker version:5.13.2  Deployment way:zookeeper+levelDB,A master with two slave。

Reply via email to