2 Replies Latest reply on Dec 16, 2008 12:03 PM by Prabhu Natarajan

    configuring BasicThreadPool

    Prabhu Natarajan Newbie

      Hi,

      We are using Jboss 4.2.3 with Jboss MQ.

      When ever there are more messages to process, our server goes to a hung state and not responding. The server status shows that it is running but it is not responding to any aplication calls. Even the Jmx console is not opening.

      I am thinking if increase the MaximumPoolSize/MaximumQueueSize attributes in the jbossmq-service.xml file we may get a better performance.

      The following is the configuration we have,

      <!-- A Thread pool service -->

      JMSThread
      JBossMQ Server Threads
      <!-- The max number of threads in the pool -->
      10
      <!-- The max number of tasks before the queue is full -->
      1000
      run



      My questions are,

      How much I can increase the MaximumPoolSize/MaximumQueueSize values?

      Is there any limit?

      Regards,
      Prabhu

        • 1. Re: configuring BasicThreadPool
          Adrian Brock Master

           

          "prabhun" wrote:

          When ever there are more messages to process, our server goes to a hung state and not responding. The server status shows that it is running but it is not responding to any aplication calls. Even the Jmx console is not opening.


          If the symptoms are really as you assert then it sounds to me like a jvm issue,
          i.e. it has crashed or hung internally?

          The limit on the number of threads is determined by your available virtual memory.
          http://jboss.org/community/docs/DOC-11566

          • 2. Re: configuring BasicThreadPool
            Prabhu Natarajan Newbie


            Hi Adrian,

            Thank you.

            We use the following JVM options

            -Xms3g -Xmx3g -XX:ThreadStackSize=128 -XX:+UseParallelGC -XX:MaxPermSize=256m -XX:NewRatio=1

            And we use SunOS.

            I am not sure whether these parameters matches between them and with the operating system.

            Can you please shed some light on this?

            We observed that the server goes to a hung state after an application exception is thrown. Earlier the server was not hanging even after the same exception was thrown. So we ignored that time.

            The exception was not handled in that bit of code and it goes back to the jvm and sever fails after some time. We are in the process of improving that part of code.

            Thanks,
            Prabhu