From users-return-30578-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Mon Apr 2 14:53:02 2012 Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 290879E7D for ; Mon, 2 Apr 2012 14:53:02 +0000 (UTC) Received: (qmail 85364 invoked by uid 500); 2 Apr 2012 14:53:01 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 85342 invoked by uid 500); 2 Apr 2012 14:53:01 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 85334 invoked by uid 99); 2 Apr 2012 14:53:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 14:53:01 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qc0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 14:52:57 +0000 Received: by qcsp15 with SMTP id p15so1853435qcs.2 for ; Mon, 02 Apr 2012 07:52:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=iGnRMC02TzTXNAJrd+BcmaEGyDlTuVNi7VYpwSMCglg=; b=LPOy7S3ufG3VJuNox0quqs0VbtW8KqC683YbRuzFcg1fvd2XRpQ6WDCiLneKcrugS1 dA7zMHfWtmd20cmA8LAwI7qzTKFjsvEKFDNi/JiVQ0+ulKjmi8uX8SqUAaw1AfUiMIVf dqhgBtcNdAzTwmwhKp/l5x1lOrYEMHH5MntLHYeR0wLbS9gvKkSc4g+eqnuhxy6y7B4a a+rYvL2X2UR2NXb0vPnRkrD4ue0Vov/GmSkx8DBcpinMJzIfsMFZcc/rxM5KRJA7ztNi A2va7TuzMER5VYN7PsN7OPEfq9z2Fs+DMPVb9jCwwjgM644JjsAyNmPSePDZBKFVoCCe OGoA== MIME-Version: 1.0 Received: by 10.229.115.21 with SMTP id g21mr3357875qcq.77.1333378003675; Mon, 02 Apr 2012 07:46:43 -0700 (PDT) Received: by 10.229.158.4 with HTTP; Mon, 2 Apr 2012 07:46:43 -0700 (PDT) In-Reply-To: <1333148749838-4520697.post@n4.nabble.com> References: <1333148749838-4520697.post@n4.nabble.com> Date: Mon, 2 Apr 2012 15:46:43 +0100 Message-ID: Subject: Re: AMQ 5.5.1 - Duplicate Messages After Network Outage and Broker Restart From: Gary Tully To: users@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org the best way to validate your back port is to verify that the problem is resolved with a 5.6-SNAPSHOT[1], there are some tests that exercise that feature, in particular: org.apache.activemq.usecases.TwoBrokerQueueClientsReconnectTest#testDuplica= teSend maybe give that a run on your branch. If you can produce a unit test that fails on trunk or a 5.6-SNAPSHOT, please reopen https://issues.apache.org/jira/browse/AMQ-3576 [1] https://repository.apache.org/content/repositories/snapshots/org/apache= /activemq/apache-activemq/5.6-SNAPSHOT/ On 31 March 2012 00:05, brucent wrote: > After resolving my previous problem with the a network connector reconnec= tion > after a network outage I am now seeing duplicate messages being delivered > from a queue. =A0The situation is this: > > I have a spoke instance which has a network connector to a hub instance. > For testing purposes I have them running on different ports and am using = a > port forwarder to allow me to simulate a network outage. > I have a queue producer connect to the spoke instance and as fast as it c= an > send messages. =A0Those are routed through the network connector to the h= ub > instance and consumed there. =A0While messages are flowing, the port forw= arder > is killed and brought back simulating an outage. > > If I send 1000 messages I always see 1000 messages being received by the > hub's consumer. =A0However when I look at the hub queue's JMX bean it say= s > that there are a few extra messages still in the queue that have not been > delivered to the consumer. =A0These are duplicates that are apparently st= uck > in some state in the hub's broker. =A0That have apparently been correctly > identified as duplicates because they are not delivered, but neither have > they been discarded. =A0I was about convinced that it was just a problem = with > the JMX bean's statistics until I restarted the hub instance and reconnec= ted > the consumer. =A0The duplicate messages were then delivered. > > Are there any settings that I can use in 5.5.1 to allow these duplicate > messages to be discarded? =A0I see some discussion of features in 5.6 tha= t may > help. =A0I tried back-porting the auditNetworkProducers setting but eithe= r I > didn't get all of the code changes or the setting isn't applicable in thi= s > case. > > Thanks, > Bruce > > > -- > View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-5= -5-1-Duplicate-Messages-After-Network-Outage-and-Broker-Restart-tp4520697p4= 520697.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. --=20 http://fusesource.com http://blog.garytully.com