Strange behavior JBoss3.2.0

[milowe]

I have a session bean that finds some entity beans
and extracts some data. Transactions are required and CM. It works fine using JBoss3.0.6.

It doesnt work after passivation on JBoss3.2.0.

1. Client calls session bean
2. Session bean finds entity beans
3. Session bean reads data from entity beans

This sequence works fine on both versions.
It doesnt work on 3.2.0 if I wait for the entity beans to get passivated.

1. Client connects to session bean again.
2. Session bean tries to find entity beans.

Stack trace:

2003-04-23 19:42:59,957 ERROR [STDERR] javax.ejb.TransactionRolledbackLocalException: null; CausedByException is:
null; CausedByException is:
null; CausedByException is:
null
2003-04-23 19:42:59,958 ERROR [STDERR] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:204)
2003-04-23 19:42:59,958 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:243)
2003-04-23 19:42:59,959 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:74)
2003-04-23 19:42:59,959 ERROR [STDERR] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:92)
2003-04-23 19:42:59,959 ERROR [STDERR] at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:120)
2003-04-23 19:42:59,960 ERROR [STDERR] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93)
2003-04-23 19:42:59,960 ERROR [STDERR] at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:477)
2003-04-23 19:42:59,960 ERROR [STDERR] at org.jboss.ejb.Container.invoke(Container.java:694)
2003-04-23 19:42:59,961 ERROR [STDERR] at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:272)
2003-04-23 19:42:59,961 ERROR [STDERR] at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:110)

[milowe]

Problem solved.

I expected setEntityContext to be called before any
ejbFind...which is true when deploying using 3.0.6. My beans get their context unset when passivated.

Version 3.2.0 is a bit more strict on following the EJB life cycle and keeps the EntityContext as long as the bean is in pool. No extra unset and set - nice.