Uploaded image for project: 'JBoss Messaging'
  1. JBoss Messaging
  2. JBMESSAGING-1685

jboss messaging / memory leak on session.rollback() operation

    Details

      Description

      we run a transacted jms application using jboss 5.1.0.GA and jboss messaging 1.4.3.GA. if a received message could not be successfully processed, e.g. because another subsystem is not available, the application issues a rollback() operation on the session. by default it is presented again 10 times until it is discarded/removed. as the jms workload is quite high sooner or later the application server ends up in out of memory conditions in heap space.

      the case can easily be reproduced with a small test application (one program sending messages, the other one receiving). the following cases/setups have been tested and ran into this memory leak

      • close session/connection after this many rollback() operations, e.g. 100
      • close session/connection after all messages have been received (and removed)
      • clustered vs. not clustered makes no difference
      • hypersonic vs. db2 makes no difference
      • adding a DLQ makes no difference
      • DeliveryMode.NON_PERSISTENT makes no difference

      the same problem can also be seen with jboss 4.2.3.GA and jboss messaging 1.4.2.GA.
      session.commit() operations (x thousands and more) do not lead to a leak
      we do not use XA.

      thanks for your help.

        Gliffy Diagrams

          Attachments

          1. FullSize200_Server.log
            140 kB
          2. FullSize200.jpeg
            FullSize200.jpeg
            1.11 MB
          3. QueueExample.java
            5 kB
          4. QueueExampleLong.java
            6 kB
          5. QueueExampleLong2.java
            6 kB
          6. QueueExampleLong3.java
            6 kB
          7. Test100K.jpg
            Test100K.jpg
            1.02 MB
          8. Test10K.jpg
            Test10K.jpg
            645 kB

            Issue Links

              Activity

                People

                • Assignee:
                  gaohoward Howard Gao
                  Reporter:
                  martin.gysel Martin Gysel
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: