"Unable to passivate due to ctx lock" and jboss stops respon

[richbolen]

We're having an issue with JBoss 3.2.3 on Win 2000 server. It appears to be related to "Unable to passivate due to ctx lock" appearing in the log files. Our jboss server stops responding to client requests and we get thousands of these "Unable..." messages in our logs. When the server is working, we don't see any of these messages.

Does anyone know if there's a clear connection between these messages and the server not responding to client requests? Is it a configuration problem?

Our app uses 2 stateful session beans (and one stateless). Our cache limit is 1000000 for stateful beans.

I've seen various posts about the "unable to passivate" messages but no clear solution.

I've enabled trace logging on "org.jboss.ejb.plugins" to see what we find.

Rich

[rcsnti]

Search the email list archives (not the forums) for submissions by me... I submitted a patch a while ago that fixes this problem. AFAIK, the patch was rolled into 3.2.4. If necessary, I can email you the patch. (to be applied to 3.2.3 source).

Regards,
Russ

[rcsnti]

Found the link to the sourceforge bug:

Here it is: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=780746&group_id=22866

You'll need a login to sourceforge to view it.

[richbolen]

Is all I need the revision 1.49.2.9 of org/jboss/ejb/StatefulSessionContai
ner.java dropped on top of the 3.2.3 source (then build)?

If so I can get that from cvs and do the build, etc.

Thanks!

[richbolen]

In the interest of having the correct info for this issue -

To fix the "unable to passivate" issue:

Get the 1.49.2.11 version of the
org/jboss/ejb/StatefulSessionContai
ner.java source file from CVS and drop that on top of the 3.2.3 source and rebuild. Then fix is in the jboss.jar file.

[dsharu]

Hi,
We are currently using JBOSS V 3.2.1. We are getting "Unable to passivate due to ctx lock" error. The server starts to slow down and eventually crashes. We are not using any stateful session beans. We are using only stateless session beans. So, is there any fix/patch related to stateless session beans?