You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2018/07/31 16:18:00 UTC

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

     [ 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 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.



  was:
If an AMQP client disconnects abruptly (i.e. closes socket without sending the AMQP close performative), {{TransportImpl}} and other Proton classes referenced within the heap.  If many such clients do this, an OutOfMemoryError: Java heap space occurs.




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



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