-
1. Re: Stateless Session Bean pooling
jaikiran Mar 15, 2012 3:20 AM (in response to ktfan)1 of 1 people found this helpfulfan 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
-
2. Re: Stateless Session Bean pooling
shidani Jul 30, 2012 9:29 AM (in response to jaikiran)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 Jul 30, 2012 10:06 AM (in response to shidani)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 Jul 31, 2012 1:11 AM (in response to sfcoy)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 Jul 31, 2012 5:07 AM (in response to shidani)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.