activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Commented] (AMQNET-394) Zombie Consumer is created after failover
Date Fri, 17 Aug 2012 23:08:38 GMT

    [ https://issues.apache.org/jira/browse/AMQNET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437127#comment-13437127
] 

Jim Gomes commented on AMQNET-394:
----------------------------------

The simplest and most robust solution is to simply send a RemoveInfo command to the broker
when a message is dispatched for a non-existent consumer.  This will clean up any zombie consumers.
                
> Zombie Consumer is created after failover
> -----------------------------------------
>
>                 Key: AMQNET-394
>                 URL: https://issues.apache.org/jira/browse/AMQNET-394
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ, Stomp
>    Affects Versions: 1.5.6
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>            Priority: Critical
>              Labels: failover
>             Fix For: 1.5.7, 1.6.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message