[AMQNET-294] durable subscription message loss when master broker fails to slave

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.4.1
• Component/s: ActiveMQ

Environment

Windows 7 (client), Windows Server 2008 64-bit (server brokers run on), Sql Server 2008 (database)

• Regression: Regression, Unit Test Broken
• Assignee: Jim Gomes
• Reporter: Mark Gellings
• Created: 26/Nov/10 18:16
• Updated: 01/Nov/11 18:21
• Resolved: 01/Nov/11 18:21

Description

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.

Issue Links

• is broken by: AMQ-3106 Failover with a durable consumer can lose Messages