activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <>
Subject [jira] Updated: (AMQNET-294) durable subscription message loss when master broker fails to slave
Date Mon, 07 Feb 2011 22:24:57 GMT


Jim Gomes updated AMQNET-294:

    Component/s:     (was: NMS)

> durable subscription message loss when master broker fails to slave
> -------------------------------------------------------------------
>                 Key: AMQNET-294
>                 URL:
>             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,, DurableConsumerTest.cs,, NMSLog.txt, NMSLogLocalFreshCannedActiveMQ542Broker.txt,
> 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.
For more information on JIRA, see:


View raw message