ASF subversion and git services commented on ARTEMIS-1663:

Commit 9b104930c25beeba646d92ab38c6038a11f1e227 in activemq-artemis's branch 
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=9b10493 ]

ARTEMIS-1663 Fixing Encoding on PageCountPendingImpl

The PageCountPendingImpl was increasing the encode size without using its full 
This was causing issues on replication as the encode is also used to determine 
the size of the packets.
however the packets were not receive the full allocated data causing missing 
packets on the replication
and test failures.

This is fixing the issue

> Add enhanced message count and size metrics for Queues
> ------------------------------------------------------
>                 Key: ARTEMIS-1663
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1663
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 2.4.0
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Major
>             Fix For: 2.5.0
> The purpose of this Jira is to enhance the message count metrics and to add 
> size metrics for Queues.   By size metrics I mean the encoded size of all the 
> messages (for large messages this will include body as well).  Right now we 
> track memory usage but it is also very useful to know exactly how much data 
> is pending on a Queue to be consumed.  
> The scope of this will be support for tracking the count/size of pending 
> messages, count/size of delivering messages, and count/size of scheduled 
> messages.  For each of these categories durable size metrics will be tracked 
> as well. The paging store will also support tracking of size metrics as well.
> These new metrics will be exposed through JMX to allow users to view the 
> statistics.  Also by tracking these new values it will allow for enhanced 
> features in the future (ie new flow control options)

This message was sent by Atlassian JIRA

Reply via email to