[
https://issues.apache.org/jira/browse/QPID-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022647#comment-16022647
]
Lorenz Quack edited comment on QPID-7689 at 5/24/17 1:53 PM:
-------------------------------------------------------------
The scope of this JIRA has been expanded (and the title adjusted to reflect
this).
Places that currently use message size without headers that should also
consider the header size are:
* Queue depth alerting
* Message based queue alerting
* QueueStatistics: en-/dequeued, persistent, unacked, and available
* Consumer: unacknowledged and delivered stats
* Exchange: routed, dropped, and received stats
* -Connection: received, delivered- see below
MessageInfo currently only exposes the message size without header. It should
also expose the size of the header.
CreditManagers will continue to use only the size of the message body without
the header.
was (Author: lorenz.quack):
The scope of this JIRA has been expanded (and the title adjusted to reflect
this).
Places that currently use message size without headers that should also
consider the header size are:
* Queue depth alerting
* Message based queue alerting
* QueueStatistics: en-/dequeued, persistent, unacked, and available
* Consumer: unacknowledged and delivered stats
* Exchange: routed, dropped, and received stats
* Connection: received, delivered
MessageInfo currently only exposes the message size without header. It should
also expose the size of the header.
CreditManagers will continue to use only the size of the message body without
the header.
> [Java Broker] Consider message header size where appropriate
> ------------------------------------------------------------
>
> Key: QPID-7689
> URL: https://issues.apache.org/jira/browse/QPID-7689
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> The changes introduced by QPID-7618 have the broker track the size of each
> queue including header. The new ring queue policy and producer flow
> control now consider messages sizes including header. The queue depth
> alerting and flow to disk ought to be consistent.
> Is there actually value tracking queue size and queue size including header
> separately?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
