You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Closed) (JIRA)" <ji...@apache.org> on 2011/11/01 19:23:32 UTC
[jira] [Closed] (AMQNET-294) durable subscription message loss when
master broker fails to slave
[ https://issues.apache.org/jira/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQNET-294.
-------------------------------
Resolution: Not A Problem
This issue is tracked by AMQ-3106 and is not fixable on the .NET client side. I'm closing this out as there isn't anything more we can do here.
> 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: ActiveMQ
> 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
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira