Uploaded image for project: 'AMQ Clients'
  1. AMQ Clients
  2. ENTMQCL-511

[jms] Memory leak after remote connection close

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.2.0.GA
    • 1.0.0-GA
    • qpid-jms
    • Hide
      In earlier releases of the product, various concurrent AMQP operations were triggering memory leaks. As a consequence, client memory use was growing.

      In this release, the leaks are fixed and client memory use is now stable.
      Show
      In earlier releases of the product, various concurrent AMQP operations were triggering memory leaks. As a consequence, client memory use was growing. In this release, the leaks are fixed and client memory use is now stable.
    • Documented as Resolved Issue
    • Hide

      repeat trying to send a message e.g. into a full queue, so that it can't get send.

      see the attached sources which is the customers reproducer.

      Show
      repeat trying to send a message e.g. into a full queue, so that it can't get send. see the attached sources which is the customers reproducer.

      Multiple open/close of connections to send messages using AMQP 1.0 protocol in a JEE application cause a “out of memory” problem using qpid-jms-client-0.21.0.redhat-1 and proton-j-0.18.0.redhat-1 on a JBoss EAP 6.4.5. with MRG 3.2.

      On regular sending messages the clients seems to be ok.
      If the message can't get send (customer tested full queue) there seems to be a leak as due to re-tries the used mem is growing until an out-of-mem. This happens even if the session is closed when the msg can't get send.

        1. MemoryProblemQPIDDemo.java
          7 kB
        2. SendMessageToBrokerForMemoryTest.java
          6 kB
        3. AMQP_testproject.ear
          3.46 MB
        4. qpidd.conf
          2 kB

              tbish@redhat.com Timothy Bish (Inactive)
              clichybi@redhat.com Carsten Lichy-Bittendorf
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: