[
https://issues.apache.org/jira/browse/AMQ-6097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064428#comment-15064428
]
Christopher L. Shannon commented on AMQ-6097:
---------------------------------------------
I did some debugging and the problem is that in certain cases, the wrong
marshaller is being used for the messages keys in the message order index.
During updates in KahaDB the size is being read as -1 and not initialized since
the used marshaller doesn't know how to serialize the message size. Normally
the location index is used for size information so this problem doesn't always
show up.
> KahaDB message size metrics can be inaccurate
> ---------------------------------------------
>
> Key: AMQ-6097
> URL: https://issues.apache.org/jira/browse/AMQ-6097
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, KahaDB
> Affects Versions: 5.12.1, 5.13.0
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
>
> I have found during testing that the reported size of the messages in a
> KahaDB store can be shown as too high in certain cases. The message count
> values are accurate, however.
> My testing as shown that when publishing a large quantity of messages with
> several producers (a couple hundred thousand) and then consuming them with
> several consumers, when all the messages are consumed and the count is 0, the
> reported size will still be greater than 0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
