3 Replies Latest reply on Jul 18, 2008 11:01 AM by bfach

    Performance Tuning for Jboss Messaging

    bfach

      Hello,

      I am running Jboss4.2.2.GA with 1.4.0.SP3.

      I have 2 MDBs running. The first MDB accepts the message from a remote client, determines which queue it needs to go to and sends it to the appropriate queue. The second MDB prepares it and sends it to a third party monitoring software.

      The issue i am having is that the second MDB requires much more resources than the first. I am trying to tweek the performance to give the second MDB more resources and speed up processing.

      So far i have two properties "maxPoolSize" and "maxSessions"

      The performance tuning notes for messaging are a bit thin. I am looking for a rule of thumb on these parameters as well as others I might have not mentioned.

      The goal is to increase performance for the second MDB. I have tried a variation of the parameters with varried results.

      Any help would be greatly appreciated!

      Thanks!

        • 1. Re: Performance Tuning for Jboss Messaging
          bfach

          Does anyone know where to point me for documentation on the optimum use of maxPoolSize and maxSessions?

          I have found that maxSessions limits the amount of beans created.

          i.e. maxPoolSize = 200
          maxSessions = 25

          25 beans are created.

          Any ideas what the best approach with these parameters is?

          Thanks in advance,

          • 2. Re: Performance Tuning for Jboss Messaging
            timfox

            The reason you don't see documentation for this in the JBM documentation, is the MDB pooling stuff is a part of JBoss App server, not JBoss messaging. It's not part of the JBM project or code.

            I believe this is documented in the app server documentation somewhere. There are also wiki pages on this I beleive.

            • 3. Re: Performance Tuning for Jboss Messaging
              bfach

              Tim,

              Thanks i will take a look.