[
https://issues.apache.org/jira/browse/AMQ-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376895#comment-15376895
]
ASF subversion and git services commented on AMQ-6356:
------------------------------------------------------
Commit f1642b4244b0bbbdeaaec6fe4808c9e54835fbf7 in activemq's branch
refs/heads/activemq-5.13.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=f1642b4 ]
https://issues.apache.org/jira/browse/AMQ-6356
Fixing store size calculation on KahaUpdateMessageCommand processing so
that the size won't increase inadvertently if the existing location of
the command in the journal is the same as the new location
(cherry picked from commit a5050a8bc5b5f45852269867dd9bf46b9381912d)
> Processing a KahaUpdateMessageCommand can lead to wrong store size being
> reported
> ----------------------------------------------------------------------------------
>
> Key: AMQ-6356
> URL: https://issues.apache.org/jira/browse/AMQ-6356
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, KahaDB
> Affects Versions: 5.13.3
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Minor
>
> When KahaDB processes a KahaUpdateMessageCommand it's possible for the size
> statistic to be inadvertently increased in size. This can happen if the
> location in the journal of the message command matches the new location.
> This bug won't show up in normal usage as typically an update message command
> is only processed when a new command is written to the journal (and hence a
> new location) but should still be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
