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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ARTEMIS-2002:
----------------------------------------------------------

Commit 74c79625b89000729e6541f8e25ee397bd06447f in activemq-artemis's branch refs/heads/master from brusdev
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=74c7962 ]

ARTEMIS-2002 Proton transport objects leaked

Remove scheduled tasks when a client disconnects to allow garbage
collector to delete the unused proton objects. Add a the unity test
AMQPConnectionContextTest to check leaks after close.


> 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
>
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> 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)