[
https://issues.apache.org/jira/browse/AMQ-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237229#comment-15237229
]
ASF subversion and git services commented on AMQ-5923:
------------------------------------------------------
Commit 485fcafcdfbb71b254977bbe5a670472aaaa4081 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=485fcaf ]
https://issues.apache.org/jira/browse/AMQ-5923
Updating tests to check prioritized messages as well
> Add Pending Message Size Metrics
> --------------------------------
>
> Key: AMQ-5923
> URL: https://issues.apache.org/jira/browse/AMQ-5923
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.13.0
>
>
> Right now the PendingMessageCursor keeps track of the number of pending
> messages (the size() method). It would be useful to also report back the
> total message size besides just the count so we know how much memory or disk
> space is being used by pending messages.
> Now that KahaDB is keeping track of the size of each message as of 5.12, it
> should be possible to report back this value in a non-blocking way. For a
> Queue this is pretty straightforward but for DurableSubscriptions some work
> will need to be done to keep track of the message size for unacked messages
> for each subscription.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
