4 Replies Latest reply on Oct 23, 2002 1:17 PM by Jay Wright

    JMS / MDB Config (jboss 3.0)

    David Stoleson Newbie

      In the standardjboss.xml file the MDB config has a MaximumSize of 15 and a MaxMessages of 1.

      I understand what MaximumSize is, but what does the MaxMessages of 1 mean?

        • 1. Re: JMS / MDB Config (jboss 3.0)
          Jay Wright Newbie


          I have been wondering this for quite some time. Have you ever got an answer?

          I was told that in 2.4.4 MaxMessages wasn't even used. Interestingly enough I WASNT told what it WASNT used for.

          I don't know if it's still NOT used in 3.0.3.

          I have just ported code (mostly a MDB) from 2.4.4 to 3.0.3 and have found that in using a MaximumSize of 50, 2.4.4 has all 50 beans are engaged, while in 3.0.3, only about 20 on average are in use. In both cases the queues are full, between 1000 and 10,000 messages on the queue.

          I have just begun the research into how the jms container has changed such that not all 50 beans are engaged.

          It's not a load issue on the machine, as far as I can tell. Load, io, idle diagnostics all look good.

          > In the standardjboss.xml file the MDB config has a
          > MaximumSize of 15 and a MaxMessages of 1.
          >
          > I understand what MaximumSize is, but what does the
          > MaxMessages of 1 mean?
          >

          • 2. Re: JMS / MDB Config (jboss 3.0)
            Joel Vogt Master

            It 'wasn't' used to determine how many messages a session is loaded with at one time.

            From the docs:

            The last two entries looks like this:

            15
            1

            The first of these - "MaximumSize" - defines how large the pool will be, i.e how many session it will have ready to serve incoming messages. The second one is used to configure the maximum number of messages a session is allowed to handle at once.

            • 3. Re: JMS / MDB Config (jboss 3.0)
              Jay Wright Newbie


              Is there any gain in having a session handle more than one Message at a time? I am assuming each session has one MessageConsumer (or MDB).

              Also, is there a document that describes changes to JBossMQ from 2.4.x to 3.0.x? I am running with the same configuration in both 2.4.x and 3.0.x, but with large performance differences. I don't know if further functionality of the JBossMQ has been built out that would affect the configuration, or if Memory management has changed within the app, which would affect the size of the pool. In 2.4.x the MaximumSize would always be working on a queue, but in 3.0.x (with my config) the MaximumSize is not reached.

              I am not sure if this is good or bad, perhaps the system is managing itself to maximize performance?

              Thanks.

              • 4. Re: JMS / MDB Config (jboss 3.0)
                Jay Wright Newbie


                Is there any gain in having a session handle more than one Message at a time? I am assuming each session has one MessageConsumer (or MDB).

                Also, is there a document that describes changes to JBossMQ from 2.4.x to 3.0.x? I am running with the same configuration in both 2.4.x and 3.0.x, but with large performance differences. I don't know if further functionality of the JBossMQ has been built out that would affect the configuration, or if Memory management has changed within the app, which would affect the size of the pool. In 2.4.x the MaximumSize would always be working on a queue, but in 3.0.x (with my config) the MaximumSize is not reached.

                I am not sure if this is good or bad, perhaps the system is managing itself to maximize performance?

                Thanks.