This content has been marked as final.
Show 4 replies
-
1. Re: Unable to passivate due to ctx lock
davidmboon Jul 15, 2004 4:33 PM (in response to davidmboon)We only get these warnings when we extend a container, if we leave the container configuration blank the jboss.xml, which means we're using 'Standard CMP EntityBean' container, we don't get these warnings.
However when I extend the 'Standard CMP EntityBean' container, I also get these wranings....<container-configuration extends="Standard CMP EntityBean"> <container-name>Dave CMP EntityBean</container-name> <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager> <commit-option>C</commit-option> </container-configuration>
so it seems that I get these warnings anytime I extend a container... -
2. Re: Unable to passivate due to ctx lock
atait Jul 23, 2004 6:08 PM (in response to davidmboon)Numerous posts about this. Even a bug report regarding memory leaks, fixed in 3.2.4. I have upgrade from 3.2.2 to 3.2.5 Using the same config as davidmboon. CMP1.1 EJBs with commit option C. Jboss continues to report "Unable to passivate due to ctx lock". I have found little help in the documentation.
Could really use some direction with this. -
3. Re: Unable to passivate due to ctx lock
aloubyansky Jul 24, 2004 3:38 AM (in response to davidmboon)I don't see it in a simple testcase. Any more info/instructions?
-
4. Re: Unable to passivate due to ctx lock
artism101 Aug 13, 2004 5:05 PM (in response to davidmboon)I too am having this problem.