activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQNET-294) durable subscription message loss when master broker fails to slave
Date Wed, 15 Dec 2010 20:20:01 GMT


Timothy Bish commented on AMQNET-294:

Did you actually fail the broker, I have the auto fail part commented out in the Java sample
so you need to do it manually.  You can comment it back in and remove the sleep from onMessage
or just kill the broker when you see the "Failoving broker connection now!" trace, sorry if
that's misleading, it was late.

If you did can you please be specific about what you did, what version of the broker, what
configuration etc.  I'm working more than one issue so I need some help so when I get back
on this I know where to start.  

On my end I generally always use the latest release or a SNAPSHOT build after latest if I
need a specific fix.  I've used canned config when possible as that allows us to add tests
to the NUnit tests that we otherwise can't since we can't depend on specific broker configs
for those tests.

> durable subscription message loss when master broker fails to slave
> -------------------------------------------------------------------
>                 Key: AMQNET-294
>                 URL:
>             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,, 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.
You can reply to this email to add a comment to the issue online.

View raw message