[ 
https://issues.apache.org/jira/browse/ARTEMIS-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated ARTEMIS-2002:
--------------------------------
    Description: 
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).



  was:
If an AMQP client 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.

I have reproduced this issue against both 2.6.2 and master 
(f0c13622ac7e821a81a354b0242ef5235b6e82df).




> 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)

Reply via email to