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] [Commented] (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:comment-tabpanel&focusedCommentId=16563907#comment-16563907 ]
Keith Wall commented on ARTEMIS-2002:
-------------------------------------
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
>
> 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)