I have a stateless session bean that is being removed, ejbRemove called, after every method invocation. I thought it should be putting the bean in to the object pool. Indeed JRun does this. Have I deployed it incorrectly ? I looked at the websphere container code, ( i.e. reverse engineered it), and it seems to call ejbRemove if the bean is not 'reentrant'. Otherwise it goes in to the pool. I thought session beans are not 'reentrant' so does this mean something different here ?
WebSphere has instance pool size setting for the EJB container, by default it is minimum 50, maximum 500. It is configurable after FP4 for WAS4.0 through admin.config file.
Simon Song
Certified Entperise Developer of Websphere
Ok.... but what does that mean ? Minimum of 50 what ? And maximum of 500 what ? Ultimately I would like me stateless session bean to hang around between calls.
So a minium of 50 instances means it should create 50 instances on start up, creating more as necessary, but never going over a limit of 500. That's not happening... there's only ever one instance and it's removed after every call on the bean. Is this normal behaviour ?