You aren't perchance using Handle.getEJBObject() in your client app/webapp are you?
If so, search this mailing lists archive for my prior post about Handle.getEJBObject().
I think that there may be a new bug introduced in the 3.2 series that causes an additional extra ref lock on the stateful bean.
If you're not using that call, then there is likely a chance that some ivars of your session bean can't be serialized...
Regards, Russ Chan
Marek Lange wrote:
After switching from 3.0.6 to 3.2.3 we experience warning messages in our logfiles:
WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=127.0.0.1:1099:dq6o9s7q-x
This seems to be a problem to passivate (a stateful session?) bean. Looking into the code, the context of the bean seems to be locked:
protected boolean canPassivate(EnterpriseContext ctx) { if (ctx.isLocked()) { // The context is in the interceptor chain return false; } ...
Is there a way to discover what is holding the lock on the context? What is the impact of that warning for our application?
Thanks,
-marek
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
-- -- Russell Chan, Navaho Networks Inc. 416 542 1590 x108
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
