Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <9864617.140331292436961998.JavaMail.jira@thor>
Date: Wed, 15 Dec 2010 13:16:01 -0500 (EST)
From: "Mark Gellings (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQNET-294) durable subscription message loss when
 master broker fails to slave
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Gellings updated AMQNET-294:
---------------------------------

    Attachment: NMSLog.txt

Tim I've attached a log file with NMS tracing enabled...You can see it gets to message 50, then no more.

2010-12-15 12:10:38,054 [16] [DEBUG] Apache.NMS.Tracer - Consumer:  At message 50
2010-12-15 12:10:38,054 [16] [DEBUG] Apache.NMS.Tracer - *** Failoving broker connection now! ***

Maybe you could compare my log with a log of your own to see if there are any differences.

> durable subscription message loss when master broker fails to slave
> -------------------------------------------------------------------
>
>                 Key: AMQNET-294
>                 URL: https://issues.apache.org/jira/browse/AMQNET-294
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.4.1
>         Environment: Windows 7 (client), Windows Server 2008 64-bit (server brokers run on), Sql Server 2008 (database)
>            Reporter: Mark Gellings
>            Assignee: Jim Gomes
>             Fix For: 1.5.0
>
>         Attachments: Apache.NMS.Test (2).zip, Apache.NMS.Test.zip, DurableConsumerTest.cs, DurableSubscriberFailoverTest.java, NMSLog.txt, TimsTestRevisedSlightly.zip
>
>
> We are seeing message loss on a durable subscription when using NMS ActiveMQ v1.4.1 and ActiveMQ v5.4.1.
> Please run the included NUnit test and watch the console output.  When it says "Failover the broker now!" do as it says.  About 75% of the time less than half of the expected 250 messages come through.
> Using version 1.1 of NMS the majority of the time the test passes.  I have seen it fail only a few times with this earlier version, and when it does there are only a couple messages that don't come through.
> In the zip file will be the unit test, and a config directory containing the master and slave activemq configurations.  We are using JDBC master/slave.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.