[
https://issues.apache.org/jira/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971740#action_12971740
]
Timothy Bish commented on AMQNET-294:
-------------------------------------
All I did was setup a pure master/slave as described here:
http://activemq.apache.org/pure-master-slave.html
All tests are on the local machine.
If inactivity is on then you shouldn't need to change anything, the standard
period is 30secs. If you want to play with settings, the reference is here:
http://activemq.apache.org/nms/configuring.html
At this point I'm kind of confused as to what issue we are working on, Lockup
is different that what the title of this issue is so if that's what's happening
then maybe we need a new issue with the simplest possible test case that
reproduces the issue (preferably with no master / slave stuff to confuse
things) From the client side master / slave is transparent, client is just
connecting and reconnecting to brokers.
Code changed between 1.3 and 1.4 yes, bugs could be anywhere, that's why we
need test cases. With version 1.4 you should running against a 5.4+ broker,
otherwise client reconnect will not work right for consumers because of a fix
for AMQ-2579.
> 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.
