You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2014/01/29 23:00:11 UTC

[jira] [Resolved] (AMQ-5003) On overlapping Failover a session can consume large amounts of memory trying to clear consumer state.

     [ https://issues.apache.org/jira/browse/AMQ-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQ-5003.
-------------------------------

    Resolution: Fixed

Added a gate to keep the session from repeating the clear in progress message consumers action until the last one finishes.

> On overlapping Failover a session can consume large amounts of memory trying to clear consumer state.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-5003
>                 URL: https://issues.apache.org/jira/browse/AMQ-5003
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.9.0
>            Reporter: Timothy Bish
>             Fix For: 5.10.0
>
>
> If a consumer onMessage call is blocked waiting for failover to complete and send an ack and the connection to the broker is dropping as attempts to reconnect are happening a session can queue up very large number of scheduler tasks to clear in progress messages for open consumers.  Since the consumer will be holding the lock these can't fire so they just pile on.  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)