From: SourceForge.net <no...@so...> - 2003-01-09 15:10:39
|
Bugs item #665067, was opened at 2003-01-09 16:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=665067&group_id=22866 Category: JBossCX Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Michael Ukpong (michaelukpong) Assigned to: Nobody/Anonymous (nobody) Summary: Managed Connection equals Null! Problems in JBOSS 3.0.3 Initial Comment: The .remove() method of some Entity beans I wrote and deployed in JBoss 3.0.0 is now throwing a "Managed Connection = null" exception in Jboss 3.0.3. I earlier noticed that these entities gave a "you are not getting the semantics you expect" warning (both in Jboss 3.0.0 and 3.0.3) but I ignored this warning in Jboss 3.0.0. Could this be the cause of the exception now thrown in Jboss 3.0.3? The funny thing is that if you keep looping on the remove (), where the number of iterations is the record length of the underlying table + 1, it eventually works! So its like the managed connection is restored after a certain number of failed attempts. What could this mean? Note that this remove() method is NOT called directly from a servlet, but through a stateless session bean. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=665067&group_id=22866 |