Hi all.

Using Orion 1.5.2, I'm having some difficulty making sense of how the entity
instance caching works.  I've seen a lot of messages on this list referring
to almost the exact same issues, but no real resolution.

Orion never seems to call passivate on my entity beans under normal
circumstances.  Even when all remote refs have been destroyed.  I put a log
message in ejbPassivate to make sure.  However, if I add
exclusive-write-access="false" to the deployment descriptor in
orion-ejb-jar, it appears to always passivate the bean immediately after I
use it.  The orion console also shows 0 instances in the ready state in this
case.

Unfortunately all I can manage as far as controlling this is "all or
nothing".  I can get it to not cache any beans, or to keep them all cached
forever.  I have played with max-instances as well as the timeout settings,
with no consistent effect (sometimes a few beans get passivated but it
appears to have no relationship to the max-instances setting value).

Anyone have a definitive answer here?  Am I doing something wrong?

Thanks,
Eric

Reply via email to