activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Network of Brokers - Duplicate message add attempt rejected
Date Mon, 29 Aug 2011 11:00:31 GMT
When you get the WARN message, it is expected that the stats are wrong
because the store should not be getting duplicates. At the point that
the store recognizes the duplicate, the stats and cursors may have
already processed the message.

The producerAudit should eliminate the duplicates at an earlier stage,
so this needs to be enabled, and may need to be large to accommodate
larger transactions.

Can you build a simple junit tests case and attach it to one of the
existing jiras or create your own.

There is a SocketProxy that you can use to simulate a network glitch.

example usage in a test that sounds very like your use case,
org.apache.activemq.usecases.BrokerQueueNetworkWithDisconnectTest

maybe you can use a variant of that test to validate configuration
and/or easily reproduce.

On 26 August 2011 17:01, oseymen <ozan.seymen@tdpg.com> wrote:
> Hi all,
>
> I tried the below simple network of brokers test with ActiveMQ 5.5,
> Activemq-5.5.0-fuse-00-43 and Activemq-5.5.0-fuse-00-27 and get the same
> behavior with all of them.
>
> I deployed ActiveMQ (above versions) to a virtual machine and my local box.
> I made no changes in local instance. I only add the following network
> connector to the virtual machine instance which forwards messages in Q1 from
> virtual machine instance to local instance:
>
> <networkConnectors>
>        &lt;networkConnector
>                name=&quot;nc&quot;
>                uri=&quot;static:(tcp://&lt;local machine IP&gt;:61616)"
>                >
>                <staticallyIncludedDestinations>
>                        <queue physicalName="Q1" />
>                </staticallyIncludedDestinations>
>        </networkConnector>
> </networkConnectors>
>
> That's it...
>
> I start a producer on the virtual machine which sends 10000 transactional
> messages to Q1 in virtual machine instance. When I disable the network
> interface and enable it back (simulating network glitch), I get this on the
> local instance:
>
>  WARN | Duplicate message add attempt rejected. Destination: Q1, Message id:
> ID:MSGTEST02-56791-634499717928681758-1:0:1:1:1003
>  WARN | Duplicate message add attempt rejected. Destination: Q1, Message id:
> ID:MSGTEST02-56791-634499717928681758-1:0:1:1:1004
>  WARN | Duplicate message add attempt rejected. Destination: Q1, Message id:
> ID:MSGTEST02-56791-634499717928681758-1:0:1:1:1005
>  WARN | Duplicate message add attempt rejected. Destination: Q1, Message id:
> ID:MSGTEST02-56791-634499717928681758-1:0:1:1:1006
>
> Messages are not lost and successfully reach the local machine but queue
> statistics are all wrong. If I get x "duplicate..." messages, I end up
> (10000 + x) messages reported on the local machine. When I attach a consumer
> to Q1 on the local instance, it can consume 10000 messages but x messages
> still remain reported in admin console and QueueSize in JConsole. Those x
> messages cannot be consumed. Statistics drop back to 0 when local broker is
> restarted.
>
> Have you experienced this problem yourselves? Is this a known/unknown bug or
> am I doing something wrong?
>
> There is an old JIRA which explains this issue
> (https://issues.apache.org/jira/browse/AMQ-2803) but this is apparently
> fixed for v5.4. I've reported this in
> https://issues.apache.org/jira/browse/AMQ-3469 for a more complex case (I
> didn't know it was this easy to demonstrate!!). Also reported by someone
> else in https://issues.apache.org/jira/browse/AMQ-3473.
>
> I've tried adding failoverProducersAuditDepth="0" and
> maxFailoverProducersToTrack="0" settings to kahadb but I still get duplicate
> suppression and still get incorrect statistics. Are there any other settings
> that I can try?
>
> I really need your comments here urgently as this is a blocker for us from
> health and activity monitoring POV. I just can't tell by looking at the
> QueueSize whether there are really x messages pending (consumers/network
> experiencing problems), or everything is fine but there are zombie messages
> reported.
>
> Thanks in advance.
> Ozan
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-Brokers-Duplicate-message-add-attempt-rejected-tp3771301p3771301.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
http://fusesource.com
http://blog.garytully.com

Mime
View raw message