Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-1845

Proton transport objects leaked if client disconnects abruptly leading to OutOfMemoryError: Java heap space

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • AMQ 7.4.0.CR2
    • None
    • None
    • None
    • AMQ Broker 1119

      https://issues.apache.org/jira/browse/ARTEMIS-2002

      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 Artemis upstream (both 2.6.2 and master (f0c13622ac7e821a81a354b0242ef5235b6e82df)).

              dbruscin Domenico Francesco Bruscino
              keithbwall Keith Wall
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: