You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mark Gellings (JIRA)" <ji...@apache.org> on 2010/12/14 23:32:10 UTC
[jira] Issue Comment Edited: (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:comment-tabpanel&focusedCommentId=12971446#action_12971446 ]
Mark Gellings edited comment on AMQNET-294 at 12/14/10 5:31 PM:
----------------------------------------------------------------
Tim I revised your unit test slightly to get it to work for me (e.g. changing Broker Uri) and appears to still be a deadlock. Gets to 50 messages and then processes no more.
I've attached my changes to your test.
We had thought maybe this was because we were running the clients on Windows 7, but when running on a Server 2003 machine it still only processed up to 50 messages.
Our brokers run on Windows Server 2008 64-bit. When you run your tests are you running the brokers locally on your machine or across a network? Also are you using the official ActiveMQ 5.4.2 like us?
Maybe you could attach your broker config(s) and I can test on our side.
Let me know.
was (Author: magellings):
Tim I revised your unit test slightly to get it to work for me (e.g. changing Broker Uri) and appears to still be a deadlock. Gets to 50 messages and then processes no more.
I've attached my changes to your test.
We had thought maybe this was because we were running the clients on Windows 7, but when running on a Server 2008 machine it still only processed up to 50 messages.
Our brokers run on Windows Server 2008 64-bit. When you run your tests are you running the brokers locally on your machine or across a network? Also are you using the official ActiveMQ 5.4.2 like us?
Maybe you could attach your broker config(s) and I can test on our side.
Let me know.
> 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, 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.