[
https://issues.apache.org/jira/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971822#action_12971822
]
Mark Gellings commented on AMQNET-294:
--------------------------------------
Oops. Nope. When I uncomment the auto failover, then I see the same behavior
as with the NMS test, except it gets to only 40 messages.
run:
Durable Consumer Failover Test Started:
Dec 15, 2010 2:22:45 PM
org.apache.activemq.transport.failover.FailoverTransport doReconnect
INFO: Successfully connected to tcp://127.0.0.1:61616?trace=true
Dec 15, 2010 2:22:46 PM
org.apache.activemq.transport.failover.FailoverTransport doReconnect
INFO: Successfully connected to tcp://127.0.0.1:61616?trace=true
Produced message 10
Produced message 20
Produced message 30
Produced message 40
Produced message 50
Produced message 60
Produced message 70
Produced message 80
Produced message 90
Produced message 100
Dec 15, 2010 2:22:46 PM
org.apache.activemq.transport.failover.FailoverTransport doReconnect
INFO: Successfully connected to tcp://127.0.0.1:61616?trace=true
Consumer: At message 10
Consumer: At message 20
Consumer: At message 30
Consumer: At message 40
*** Failoving broker connection now! ***
Dec 15, 2010 2:22:50 PM
org.apache.activemq.transport.failover.FailoverTransport handleTransportFailure
WARNING: Transport (/127.0.0.1:61616) failed to
tcp://127.0.0.1:61616?trace=true , attempting to automatically reconnect due
to: java.net.SocketException: socket closed
Dec 15, 2010 2:22:51 PM
org.apache.activemq.transport.failover.FailoverTransport doReconnect
INFO: Successfully reconnected to tcp://QG076619:61616
OnException: Could not correlate acknowledgment with dispatched message:
MessageAck {commandId = 8, responseRequired = false, ackType = 0, consumerId =
ID:QG076619-60372-1292444565609-0:3:1:1, firstMessageId =
ID:QG076619-60372-1292444565609-0:2:1:1:31, lastMessageId =
ID:QG076619-60372-1292444565609-0:2:1:1:40, destination =
topic://DurableConsumerTest-TopicId, transactionId = null, messageCount = 10}
Dec 15, 2010 2:23:46 PM
org.apache.activemq.transport.failover.FailoverTransport doReconnect
INFO: Successfully connected to tcp://127.0.0.1:61616?trace=true
Messages consumed were 40, not 100 as expectedDurable Consumer Failover Test
Complete:
BUILD SUCCESSFUL (total time: 1 minute 2 seconds)
> 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.
