-
1. Re:
rcsnti May 17, 2004 3:18 PM (in response to richbolen)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 -
2. Re:
rcsnti May 17, 2004 3:23 PM (in response to richbolen)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. -
3. Re:
richbolen May 17, 2004 3:45 PM (in response to 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! -
4. Correction...
richbolen May 18, 2004 8:45 AM (in response to 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. -
5. Re:
dsharu Jun 17, 2005 4:11 PM (in response to richbolen)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?