Setting max-beans-in-freepool to 1 would give you a singleton (per
server) stateless session bean in WebLogic Server 5.1.
The cache is used only for stateful session beans and entity beans.
The minimum size of 8 in the EJB cache is a result of the internal
implementation of the cache. Essentially allowing it to assume (max-beans-in-cache
/ 8) >=1 made it possible to avoid a number of special cases in the cache code.
If you have WebLogic-specific questions, I would recommend that you either
contact [EMAIL PROTECTED] or post to weblogic.developer.interest.ejb
-- Rob
Rob Woollen
Senior Software Engineer
BEA WebLogic
[EMAIL PROTECTED]
Jean-Baptiste Nizet wrote:
> Sunil Kuchipudi wrote:
>
> > 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.
>
> It's not part of the spec, since the spec doesn't force the container to use any
> particular pooling or caching technique.
> And, in the case of Weblogic, it won't work, because I've found that the minimum
> numbers of beans in cache can't be set to anything less than 8 (if it's set to
> one, it won't be respected: the number will grow to 8). Don't ask me why.
>
> JB.
>
===========================================================================
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".
