[jira] [Comment Edited] (ARTEMIS-2002) Proton transport objects leaked if client disconnects abruptly leading to OutOfMemoryError: Java heap space

["Keith Wall (JIRA)" <ji...@apache.org>]

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

Keith Wall edited comment on ARTEMIS-2002 at 7/31/18 4:26 PM:
--------------------------------------------------------------

Program that demonstrates ARTEMIS-1993 demonstrates this issue.  Run the program as described in the README.md except reduce the Xmx parameter back to 2GB (so the heap fills in a timely way), and add the {{-XX:+HeapDumpOnOutOfMemoryError}} to {{JAVA_ARGS}} within {{etc/artemis.profile}}.  Run the program.  The Broker will crash with an OOM (heap).   See attached visual vm screenshot.


was (Author: k-wall):
Program that demonstrates ARTEMIS-1993 demonstrates this issue.  Run the program as described in the README.md except reduce the Xmx parameter back to 2GB (so the heap fills in a timely way), and add the {{-XX:+HeapDumpOnOutOfMemoryError}} to {{JAVA_ARGS}} within {{etc/artemis.profile}}.  Run the program.  The Broker will crash with an OOM (heap). 

> Proton transport objects leaked if client disconnects abruptly leading to OutOfMemoryError: Java heap space
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-2002
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2002
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 2.6.2
>            Reporter: Keith Wall
>            Priority: Major
>         Attachments: ARTEMIS-2002-OOMEHeap-ProtonObjectsLeaked.png
>
>
> If an AMQP client with an attached receiving link disconnects abruptly (i.e. closes socket without sending the AMQP close performative), {{TransportImpl}} and other Proton class instances remain referenced within the heap.  If many such clients do this, an OutOfMemoryError: Java heap space occurs.  This occurs even though the underlying socket connection has been closed.
> I have reproduced this issue against both 2.6.2 and master (f0c13622ac7e821a81a354b0242ef5235b6e82df).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)