> Rick,
> In the deployment descriptor (e.g WebLogic for instance) can I specify
> something like below to limit the number of beans in the pool to 1. Will
> this not work ?. I am not sure if this part of the EJB 1.1 spec. Will have
> to verify this.
>
> <MAX_BEANS_IN_FREE_POOL>1</MAX_BEANS_IN_FREE_POOL>
> <MAX_BEANS_IN_CACHE>1</MAX_BEANS_IN_CACHE>
This has nothing to do with the EJB 1.1 spec. This is a specific to the
WebLogic container. And if I remember correct the max-beans-in-cache
setting is not "hard", so it is possible to have more in the pool.
In any case, what I was referring to was stateless session beans (which
typically has a pool, but no cache). What are you referring to above?
EntityBeans? Seems like it...
And the max-beans-in-free-pool setting you're referring to is definitely
a max on how many instances can be contained in the pool, not how many
can be extracted from it at any given time (e.g. you can do 500
concurrent calls on 500 separate instances, it's just that it's not
gonna use pooled instances but instead create new ones all the time).
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
