[
https://issues.apache.org/jira/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973833#action_12973833
]
Timothy Bish commented on AMQNET-294:
-------------------------------------
You are welcome to take what's in trunk right now and do some testing. There
is still an edge case that allows a stale messageAck to get to the broker which
is the root of the problem in both Java and .Net clients. The fix that's in
there now will catch some of them, but I still need to figure out a way to get
the reset without impacting anything else. If 1.4.1 does everything else you
need it to then I'd go with that, the way that 1.3 is doing the failover can
cause issues inside of transacted sessions such as missing messages so it has
its own set of problems.
This should all be smoothed out in 1.5 which I hope to release sometime in
January once I get the Distributed TX stuff ironed out.
> 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,
> NMSLogLocalFreshCannedActiveMQ542Broker.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.
