activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQNET-394) Zombie Consumer is created after failover
Date Mon, 20 Aug 2012 22:24:38 GMT


Timothy Bish commented on AMQNET-394:

The other thing that we want to avoid is sending multiple removeInfo's in the case where the
broker has async dispatch enabled and the consumer has a prefetch, you'd likely get a batch
of messages for that consumer out before your remove gets fired off and then end up sending
several removes and creating a lot of log spam on the broker.
> Zombie Consumer is created after failover
> -----------------------------------------
>                 Key: AMQNET-394
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ, Stomp
>    Affects Versions: 1.5.6
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>            Priority: Critical
>              Labels: consumer, failover
>             Fix For: 1.5.3, 1.5.7, 1.6.0
>   Original Estimate: 24h
>          Time Spent: 24h
>  Remaining Estimate: 0h
> Steps to reproduce:
> 1. Create a consumer on a topic.
> 2. Disconnect the broker (easiest is to shut it down).
> 3. Destroy the consumer while the low-level failover is retrying to connect.
> 4. Bring the broker online and let the failover reconnect.
> Result:
> A zombie consumer is re-created on the topic.  This will eventually lead to producer
flow-control kicking in because it will never acknowledge messages sent to it.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message