[
https://issues.apache.org/jira/browse/QPID-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8316:
-----------------------------
Description:
A regression in heap memory utilization was introduced in message validation
functionality implemented as part of IBAMQ-8318. The message metadata is loaded
into heap for message validation and continue to remain in heap until message
is consumed. The flow to disk functionality does not clean metadata objects as
message is not considered as being resided in memory.
The issue can be mitigated by increasing heap size.
was:A regression in heap memory utilization was introduced in message
validation functionality implemented as part of IBAMQ-8318. The message
metadata is loaded into heap for message validation and continue to remain in
heap until message is consumed. The flow to disk functionality does not clean
metadata objects as message is not considered as being resided in memory.
> [Broker-J][AMQP 0-8..0-91] The meta data of flowed to disk messages continue
> to occupy heap memory
> --------------------------------------------------------------------------------------------------
>
> Key: QPID-8316
> URL: https://issues.apache.org/jira/browse/QPID-8316
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-7.0.7, qpid-java-broker-7.1.1,
> qpid-java-broker-7.1.2, qpid-java-broker-7.1.3
> Reporter: Alex Rudyy
> Priority: Critical
> Fix For: qpid-java-broker-7.0.8, qpid-java-broker-7.1.4
>
>
> A regression in heap memory utilization was introduced in message validation
> functionality implemented as part of IBAMQ-8318. The message metadata is
> loaded into heap for message validation and continue to remain in heap until
> message is consumed. The flow to disk functionality does not clean metadata
> objects as message is not considered as being resided in memory.
> The issue can be mitigated by increasing heap size.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
