activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3998) Incorrect reporting of pendingQueueSize of durable subs after reconnect with unacked
Date Wed, 29 Aug 2012 13:35:07 GMT

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

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

    Resolution: Fixed
    Regression:   (was: Unit Test Broken,Regression)

test regression resolved with http://svn.apache.org/viewvc?rev=1378542&view=rev

duplicate calls to resetBatch on start caused an extra reread of the store which pulled out
a message about to be deleted in error.
resetting is now only called from gc.
                
> 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

Mime
View raw message