[
https://issues.apache.org/jira/browse/AMQ-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372957#comment-15372957
]
ASF subversion and git services commented on AMQ-6352:
------------------------------------------------------
Commit 9c483fa477fd0202cd311d044e22d62eddd5d25f in activemq's branch
refs/heads/activemq-5.13.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=9c483fa ]
https://issues.apache.org/jira/browse/AMQ-6352
Fixing PList size tracking by moving the null assignment on removal to
after the onRemoval method is called to make sure that the decrement is
done properly.
(cherry picked from commit d635a369404db25e1c450283a224ed89abf3c5a7)
> Temporary message store cursor does not track store message size properly
> -------------------------------------------------------------------------
>
> Key: AMQ-6352
> URL: https://issues.apache.org/jira/browse/AMQ-6352
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.3
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Minor
> Fix For: 5.14.0, 5.13.4
>
>
> The PList implementation for the temporary store that is used by the
> FilePendingMessageCursor has a bug that causes the message size to not be
> accurate. On removal of an item from the PList, a null reference is always
> passed to the onRemove method by mistake. This causes the message size
> counter to not decrement properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
