ServiceMix
  1. ServiceMix
  2. SM-1842

Memory leak when using the JMS binding component

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.3
    • Fix Version/s: None
    • Component/s: servicemix-jms
    • Labels:
      None
    • Environment:

      Windows XP Pro
      JDK 1.6.0_07

      Description

      I think there is a memory retention problem in the JMS binding component.

      Here is my test scenario.

      I have a JMS provider service unit and a JMS consumer service unit linked together.
      I have a simple Java program that continuously sends text messages to a JMS topic (managed by the servicemix embedded activemq server). My consumer listens on this topic and sends the received message to the JMS provider.
      I have another simple Java program that listens to another JMS topic (the one the provider is writing to).
      The consumer endpoint uses a in only MEP (in a first attempt, I used an in/out MEP, but I rapidly realized that messages were accumulating inside ther servicemix/activemq server).

      I use 2 message sizes.
      I'm using jconsole to monitor the memory consumption of servicemix (and the state of my topics through JMX beans).
      With short messages (20Kb xml text), I have a 200Mb memory retention after sending about 1 million messages.
      Same problem with 1Mb messages (approximatively same memory retention and number of messages).

      Using visualvm (to count instances), I found a map (JMSComponent.knownExchanges) that contains roughtly as many entries as the number of messages who did pass through servicemix. This map contains message IDs.

      I think the memory retention problem is proportional to the number of messages exchanged. With bigger messages, the time to reach 200Mb memory leak will be far longer than with 20Kb messages.

      Here are 2 archives :

      • my maven project for my SA and my 2 SUs,
      • Java source code for the JMS emitter and the JMS receiver. The main class is Main. The emitter receives "EMITTER" as argument, and the receiver receives "RECEIVER".
      1. src.zip
        6 kB
        Damien MORCELLET
      2. jms2jms.zip
        5 kB
        Damien MORCELLET

        Activity

        Hide
        Chris Custine added a comment -

        Just out of curiosity, have you tried the new JMS component?
        http://servicemix.apache.org/servicemix-jms-new-endpoints.html

        Slightly different syntax for configuring the endpoints, but this is what we recommend for new projects. I would just be curious if you have the same issues with this one.

        Show
        Chris Custine added a comment - Just out of curiosity, have you tried the new JMS component? http://servicemix.apache.org/servicemix-jms-new-endpoints.html Slightly different syntax for configuring the endpoints, but this is what we recommend for new projects. I would just be curious if you have the same issues with this one.
        Hide
        supertallal@hotmail.com added a comment -

        Hi,
        I"m using the newest version of servicemix (4) and I think I'm having the same problem of memory leak. I'd like to know if you solved it or if you found a way to bypass it.
        Regards,
        Tarek.

        Quoted from:
        http://www.nabble.com/-jira--Created%3A-%28SM-1842%29-Memory-leak-when-using-the-JMS-binding-component-tp22949795p22949795.html

        Show
        supertallal@hotmail.com added a comment - Hi, I"m using the newest version of servicemix (4) and I think I'm having the same problem of memory leak. I'd like to know if you solved it or if you found a way to bypass it. Regards, Tarek. Quoted from: http://www.nabble.com/-jira--Created%3A-%28SM-1842%29-Memory-leak-when-using-the-JMS-binding-component-tp22949795p22949795.html
        Hide
        Damien MORCELLET added a comment -

        Hi Tarek,

        I didn't solved it.
        I didnt find a way to bypass it.

        I've tried to use the new servicemix-jms binding component (with ServiceMix 3.3), as Chris suggested. It does not show this memory leak problem but has some strange connection/deconnection problems.
        I did not investiguate further (in the end, we decided to use a pure JMS solution with no ServiceMix, especially due to our required message volume/count).

        If I use the same scenario with HTTP/SOAP binding components instead of JMS ones, the memory leak does not appear (millions of messages are OK).
        Regards,
        Damien.

        Show
        Damien MORCELLET added a comment - Hi Tarek, I didn't solved it. I didnt find a way to bypass it. I've tried to use the new servicemix-jms binding component (with ServiceMix 3.3), as Chris suggested. It does not show this memory leak problem but has some strange connection/deconnection problems. I did not investiguate further (in the end, we decided to use a pure JMS solution with no ServiceMix, especially due to our required message volume/count). If I use the same scenario with HTTP/SOAP binding components instead of JMS ones, the memory leak does not appear (millions of messages are OK). Regards, Damien.
        Hide
        Gert Vanthienen added a comment -

        Bulk-closing older issues for Apache ServiceMix 3.x since we're no longer actively working on these at the moment.

        Show
        Gert Vanthienen added a comment - Bulk-closing older issues for Apache ServiceMix 3.x since we're no longer actively working on these at the moment.

          People

          • Assignee:
            Chris Custine
            Reporter:
            Damien MORCELLET
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development