[
https://issues.apache.org/jira/browse/AMQ-6097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068108#comment-15068108
]
ASF subversion and git services commented on AMQ-6097:
------------------------------------------------------
Commit 041191679301554c669451cd0a628c49e07bb039 in activemq's branch
refs/heads/activemq-5.12.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=0411916 ]
https://issues.apache.org/jira/browse/AMQ-6097
remove un-needed import statements
(cherry picked from commit 370b1810995c48129521d1c86d7b0a31d1d966d9)
> 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
> Fix For: 5.12.2, 5.13.1, 5.14.0
>
>
> 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)
