activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Gellings (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-294) durable subscription message loss when master broker fails to slave
Date Thu, 16 Dec 2010 16:37:01 GMT

    [ https://issues.apache.org/jira/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972136#action_12972136
] 

Mark Gellings commented on AMQNET-294:
--------------------------------------

Okay.  I had thought things were working fine for you...in AMQNET-293 you had said "I haven't
been able to reproduce any sort of deadlock using latest trunk and the provided tests in AMQNET-294".
 So good to know you are actually seeing the problem on your end too.

I did test with ActiveMQ v5.3.2 and the same problem occurred.  

It does appear to be something in combination of the clients and broker end as the tagged
1.1, 1.2, and 1.3 versions of NMS do not have this problem when running against the ActiveMQ
v5.4.2 broker.

> 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.


Mime
View raw message