[
https://issues.apache.org/jira/browse/AMQ-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Earls updated AMQ-2210:
-----------------------------
Attachment: AMQ2149LevelDBTest.stack
> Infinite loop: WARN PrefetchSubscription - Ack before disaptch,
> waiting for recovery dispatch: MessageAck
> --------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2210
> URL: https://issues.apache.org/jira/browse/AMQ-2210
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Environment: solaris 10 trunk version 764403
> Reporter: ying
> Assignee: Gary Tully
> Priority: Blocker
> Fix For: 5.3.0
>
> Attachments: AMQ2149LevelDBTest.stack
>
>
> Reproduce steps:
> 1. setup 4 network of brokers with multicast discovery
> 2. start client consumers and producers
> 3. let the producer produce message constantly
> 4. in jconsole, stop() the broker the consumers are connecting to
> 5. after the consumers failover to another broker, the newly connected broker
> will get into an infinite loop:
> WARN PrefetchSubscription - Ack before disaptch, waiting for
> recovery dispatch: MessageAck {commandId = 1232, responseRequired = true,
> ackType = 2, consumerId = ID:host01-39430-1239887122787-0:0:2:1,
> firstMessageId = ID:host01-39430-1239887122787-0:0:87:1:5, lastMessageId =
> ID:host01-39430-1239887122787-0:0:87:1:5, destination =
> queue://Consumer.A-host01-1527-1239887124983.VirtualTopic.B, transactionId =
> TX:ID:host01-39430-1239887122787-0:0:38, messageCount = 1}
> This broker will stop functioning and consumer is not processing messages.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
