Hi all,
We have a problem with JBoss 2.4.6 with Tomcat 4.0.3. In our Cactus
unit-test suites, tests of the EJB Remove method have started failing.
Further investigation indicate that this is the same regardless of
whether the remove is called on the Home or the Remote interface. We
are running the integrated JBoss-Tomcat configuration.
We are getting a ClassCastException casting our primary key to the
correct type from the EntityContext. The debugger shows that the
returned key object is of the correct class, indicating that there is
some classloader issue involved. The following log traces confirm this...
// successful ejbLoad for business method, listing classloader class and
system identity hashcode
[14:50:42,962,EjbCompoundUserBean] EJB Classloader Identity =
org.jboss.web.WebClassLoader - 4977982
[14:50:42,962,EjbCompoundUserBean] PK Classloader Identity =
org.jboss.web.WebClassLoader - 4977982
// trace for ejbLoad prior to remove being called, again listing
classloader class and system identity hashcode
[14:50:46,118,EjbCompoundUserBean] EJB Classloader Identity =
org.jboss.web.WebClassLoader - 4977982
[14:50:46,118,EjbCompoundUserBean] PK Classloader Identity =
org.apache.catalina.loader.WebappClassLoader - 10714218
Note that the PK we are being given by the EntityContext is indeed using
a different classloader instance (and indeed class...) from that of the EJB.
The other point to note is that the EJB being removed is one that has
just been newly created.
We have not seen this behaviour with 2.4.4. Any thoughts would be
appreciated.
Thanks in advance
David
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
