Bugs item #641740, was opened at 2002-11-21 01:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=641740&group_id=22866
Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Later Priority: 5 Submitted By: Vladimir Korenev (vkorenev) Assigned to: Scott M Stark (starksm) Summary: jboss-3.0.4 classloader bug Initial Comment: The same bug was submitted against v.3.0.2 (see #606359) and it appeared again in v.3.0.4 ---------------------------------------------------------------------- >Comment By: Scott M Stark (starksm) Date: 2002-11-25 11:58 Message: Logged In: YES user_id=175228 Looking more at the server.log I see: 2002-11-21 12:20:28,271 WARN [org.jboss.deployment.MainDeployer] The manifest e ntry in file:/D:/java/jboss- 3.0.4/server/default/tmp/deploy/server/default/deplo y/cboss.ear/66.cboss.ear-contents/client-core-ejb.jar references URL file:/D:/ja va/jboss- 3.0.4/server/default/tmp/deploy/server/default/deploy/cboss.ea r/66.cbos s.ear-contents/client-common.jar which could not be opened, entry ignored Run the attached ListJar class on the cboss.ear so I can see the complete structure and manifest references. You should be able to attach the output to this bug unless your ear is huge. ---------------------------------------------------------------------- Comment By: Scott M Stark (starksm) Date: 2002-11-25 11:39 Message: Logged In: YES user_id=175228 The attached ia.log is a distillation of the server.log and ucl.log sent to me by Vladimir. It shows the CurrentUser class being loaded from the client-core-ejb.jar and the CbUser being loaded from the admin-ejb.jar. Presumably the classes are redundantly included in both of the jars. In order for this to work with the current class loading scheme the common classes that use package protected or protected access must be loaded by the same class loader. This means these utility classes must be factored out into a seperate jar that is referenced by the ejb-jars manifest Class- Path attribute. In 3.2 we will be looking at either transforming the deployment into a canonical set of classes or using a single UnifiedClassLoader for all of the jars in the top level deployment to avoid this. ---------------------------------------------------------------------- Comment By: Vladimir Korenev (vkorenev) Date: 2002-11-21 01:43 Message: Logged In: YES user_id=622967 I have got an IllegalAccessError when accessing a field with package access. IMHO it is a classloader bug. I have attached an archive with logs an 2 source files. P.S. The source files are ugly (they are not mine), but they worked fine on Orion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=641740&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
