5 Replies Latest reply on Jul 31, 2012 5:07 AM by wdfink

    Stateless Session Bean pooling

    ktfan

      By default the slsb-strict-max-pool is set to slsb-strict-max-pool="20", is it the recommended maximum pool size ?

       

      Is there a way to check the number of "live" session bean instances ? I dont see such a feature in the Admin management console.

        • 1. Re: Stateless Session Bean pooling
          jaikiran

          fan kam thong wrote:

           

          By default the slsb-strict-max-pool is set to slsb-strict-max-pool="20", is it the recommended maximum pool size ?

           

           

          It's not a recommended size, since each bean in each application would have to tune it accordingly. It's just a default value we setup.

           

          fan kam thong wrote:

           

           

          Is there a way to check the number of "live" session bean instances ? I dont see such a feature in the Admin management console.

          I don't think it's available since the metrics aren't exposed yet. There's some work going on for this here https://issues.jboss.org/browse/AS7-2281

          1 of 1 people found this helpful
          • 2. Re: Stateless Session Bean pooling
            shidani

            What if I set the slsb-strict-max-pool to a high number, say 1000 to be sure many concurrent request may be run at same time ?

            • 3. Re: Stateless Session Bean pooling
              sfcoy

              That would depend upon what your slsb is doing. Is it performing database access? Do you have access to 1000 database connections?

              • 4. Re: Stateless Session Bean pooling
                shidani

                So in case of performing database access the slsb-strict-max-pool should be less than or equal to max-pool-size of datasource. is it right?

                • 5. Re: Stateless Session Bean pooling
                  wdfink

                  Yes and no,

                  yes if you do not want to wait for a DB connection.

                  no if you can accept to wait for the 'blocking time'

                  but this depend to the application whether the datasource is used the whole time and how long it is.

                   

                  It make not a big sense to have lots of getConnection timeouts in the logfile.