[
https://issues.apache.org/jira/browse/AMQ-6097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068086#comment-15068086
]
ASF subversion and git services commented on AMQ-6097:
------------------------------------------------------
Commit a73ada062960e72b5f22bb8cbb914997f72f4a37 in activemq's branch
refs/heads/activemq-5.13.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=a73ada0 ]
https://issues.apache.org/jira/browse/AMQ-6097
Fixing JournalCorruptionEofIndexRecoveryTest class
Because of the size being stored in the message order index, the test
testRecoveryAftercorruptionCheckSumExistingIndex was no longer passing
as that test was corrupting the size value in the journal, but not the
size value in the index. The test now corrupts both values so that the
expect exception occurs again.
(cherry picked from commit 507d40a79f15449ba6d79ef85d7fdf6bf50a3a65)
> 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)
