[ 
https://issues.apache.org/jira/browse/QPID-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010241#comment-17010241
 ] 

ASF subversion and git services commented on QPID-8398:
-------------------------------------------------------

Commit a57d085b669d91936627ae1fab7d258fa75a2746 in qpid-broker-j's branch 
refs/heads/master from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=a57d085 ]

QPID-8398: [Broker-J][AMQP 0-9] Use SoftReferences to access decoded message 
heades in order to GC them before running into OutOfMemory conditions


> [Broker-J] [AMQP 0-9] Improve heap usage utilization by small transient 
> messages with headers
> ---------------------------------------------------------------------------------------------
>
>                 Key: QPID-8398
>                 URL: https://issues.apache.org/jira/browse/QPID-8398
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.1.1, 
> qpid-java-broker-7.1.2, qpid-java-broker-7.1.3, qpid-java-broker-7.1.4, 
> qpid-java-broker-7.1.5, qpid-java-broker-7.1.6
>            Reporter: Alex Rudyy
>            Priority: Major
>             Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.7
>
>
> The Qpid Broker can crash with OutOfMemoryError when small  transient 
> messages with decoded headers occupy the entire heap without triggering the 
> flow to disk. The direct memory utilization by the messages is below the flow 
> to disk threshold. As result, the decoded message headers  are accumulated in 
> heap and can cause OutOfMemoryError.
> The heap utilization can be improved by using {{SoftReferences}} for decoded 
> headers. That should allow to GC the headers on running into heap OutOfMemory 
> conditions
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to