On Wed, 16 Jul 2003 14:04, Brian Wallis wrote: > JBoss 3.0.7, JDK 1.4.1_01, Mandrake linux 9.0 with 2.4.7 kernel.
Another seemingly unrelated multiple classloaders issue. We have an EJB jar file that requires access to another jar (ojdbc14.jar) to deploy successfully so we define a Class-Path entry in the manifest the refers to that other jar file like so Class-Path: ojdbc14.jar This in effect defines the deployment ordering. We also have ojdbc14.jar in the same deploy directory as the EJB jar file. This seems to result in ojdbc14 being loaded by two instances of UnifiedClassLoader3. Once for the Class-Path entry in the EJB jar file (3eec1a, addedOrder=22) and once because it is present in the deploy directory (bc9673, addedOrder=0) I've attached part of the log output showing these two deployments. There seems to be far too many classloaders. Is a new one created for each EJB deployment? I thought it was all meant to run within the one class loader unless scoped loaders were explicitly used. brian wallis... ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
