[
https://issues.apache.org/jira/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972149#action_12972149
]
Mark Gellings commented on AMQNET-294:
--------------------------------------
When testing with the older NMS clients all the messages come through and the
NUNit test passes. This is even with just a prefetch of 5 in which all the
messages should not have been sent to the client. So the test gets to 50
messages, restarts, and then message 50 and above come through. The test only
adds messages to the received message list if the id of the message is
different, which asserts that all the unique messages came through.
short id = Convert.ToInt16(((ActiveMQTextMessage) message).Text);
if(!consumedMessageList.Contains(id))
{
consumedMessageList.Add(id);
}
Maybe the problem is due to a newer version of the OpenWire protocol being
used? Should an issue be created for the java client too, or created for the
broker?
What is your opinion of rolling with NMS 1.3 and ActiveMQ 5.4.2 instead of NMS
1.4.1? We're moving to a later version of ActiveMQ due to bug
https://issues.apache.org/jira/browse/AMQ-2082. We have an idempotent message
pattern built into our framework resting on top of NMS to detect duplicate
messages and send them through as redelivered so the clearing out of the in
progress message list may not be of concern.
> 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.
