You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2012/08/28 14:09:07 UTC

[jira] [Resolved] (AMQ-3998) Incorrect reporting of pendingQueueSize of durable subs after reconnect with unacked

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

Gary Tully resolved AMQ-3998.
-----------------------------

    Resolution: Fixed

fixed in http://svn.apache.org/viewvc?rev=1378085&view=rev

issue was recalculating size and also reading messages back into pending. Deferring size recalculation to resetBatch resolves.
                
> Incorrect reporting of pendingQueueSize of durable subs after reconnect with unacked
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-3998
>                 URL: https://issues.apache.org/jira/browse/AMQ-3998
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.6.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.7.0
>
>
> A durable sub that does not ack messages, so uses a transaction of client ack and connects then disconnects results in duplicate tally of the pending message count for the active sub (keepdurablesubsactive must be at default true). This issue emerged post fixes for https://issues.apache.org/jira/browse/AMQ-3871

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira