[
https://issues.apache.org/jira/browse/QPID-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022923#comment-16022923
]
Lorenz Quack commented on QPID-7689:
------------------------------------
Connections have stats {{bytesIn}} and {{bytesOut}} that currently record the
message content (without headers) sizes coming in/out on that connection.
The name suggests it would be the amount of bytes regardless of nature of the
bytes (content, header, TLS overhead, ...) going over the connection.
Changing this is out of scope for this JIRA. Therefore, the old behaviour
(message content without headers) is kept.
> [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]
