activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6097) KahaDB message size metrics can be inaccurate
Date Fri, 18 Dec 2015 19:46:46 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064623#comment-15064623
] 

ASF subversion and git services commented on AMQ-6097:
------------------------------------------------------

Commit 246ccb8e04515c6e85544b32035537f60d92b5b9 in activemq's branch refs/heads/master from
[~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=246ccb8 ]

https://issues.apache.org/jira/browse/AMQ-6097

Fixing KahaDB so that the correct marshaller is used for the message
keys inside of the message order index.  This will ensure that message
size metrics are accurate.


> 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)

Mime
View raw message