We've been doing some tuning of our Stateful Session Bean cache to learn more about how the standardjboss.xml cache parameters are used. It all seems to make sense as far as the passivation and removal of these beans. However, we've noticed one oddity that we're somewhat confused about.
When activate is called on a bean that was previously passivated, 2 new instances of the bean are created. We can see this using OptimizeIt. Once of these instances seems to be quickly picked up by the remover thread so its not a big deal. However, we're still wondering where this extra instance is coming from? Does this have something to do with how the activation is implemented? Thanks.