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

[LTS] Leak of HttpAcceptorHandler instances when using websocket connections

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • AMQ 7.4.0.GA
    • None
    • None
    • False
    • False
    • +
    • Hide
      Cause: The broker is leaking an object on every WebSocket connection, Consequence: Heap memory would fill up and eventually cause an OutOfMemoryError, Fix: Clean up all objects properly when accepting WebSocket connections, Result: Heap memory no longer fills with leaked objects.
      Show
      Cause: The broker is leaking an object on every WebSocket connection, Consequence: Heap memory would fill up and eventually cause an OutOfMemoryError, Fix: Clean up all objects properly when accepting WebSocket connections, Result: Heap memory no longer fills with leaked objects.
    • Verified in a release

      We are running Artemis 2.9.0 and we noticed the memory grows continuously after getting a heap we discovered there are a leak of multiple instances of type org.apache.activemq.artemis.core.remoting.impl.netty.HttpAcceptorHandler which are keep in a list inside org.apache.activemq.artemis.core.remoting.impl.netty.HttpKeepAliveRunnable.

      Those instances are removed in the channelInactive method but this method is not called because when doing the upgrade to websocket the handler is removed.

              rhn-support-jbertram Justin Bertram
              dbruscin Domenico Francesco Bruscino
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: