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

["clebert suconic (Jira)" <ji...@apache.org>]

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

clebert suconic closed ARTEMIS-2002.
------------------------------------
    Fix Version/s: 2.10.0
       Resolution: Fixed

> 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
>             Fix For: 2.10.0
>
>         Attachments: ARTEMIS-2002-OOMEHeap-ProtonObjectsLeaked.png
>
>          Time Spent: 4h 10m
>  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
(v8.3.2#803003)