Ok, so to reiterate, the current (3.0 beta 2) classloader for an EJB
will use whatever it knows about, including jars found in
JBOSS_HOME/lib, right? And, the Verifier Errors I'm seeing on the EJB
side (see previous post from a few hours ago) are more than likely a
conflict from the EJB I've deployed requiring the newer log4j jar but
not getting it, right?
As for Log4j 1.2 in JBoss, we are using 1.2 beta 3 and here is the
failure during the early startup of Jboss:
[spawn] [java] 21:16:19,031 ERROR [Server] start failed
[spawn] [java] java.lang.NoSuchMethodError
[spawn] [java] at
org.jboss.logging.Logger.isDebugEnabled(Logger.java:97)
[spawn] [java] at
org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:349
)
[spawn] [java] java.lang.NoSuchMethodError
[spawn] [java] at
org.jboss.logging.Logger.isDebugEnabled(Logger.java:97)
[spawn] [java] at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:249)
[spawn] [java] at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:208)
[spawn] [java] at
org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:349
)
[spawn] [java] at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:249)
[spawn] [java] at org.jboss.Main.boot(Main.java:138)
[spawn] [java] at org.jboss.Main$1.run(Main.java:371)
[spawn] [java] at java.lang.Thread.run(Thread.java:484)
[spawn] [java] at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:208)
[spawn] [java] at org.jboss.Main.boot(Main.java:138)
[spawn] [java] at org.jboss.Main$1.run(Main.java:371)
[spawn] [java] at java.lang.Thread.run(Thread.java:484)
[spawn]
So, looks like an upgrade would require some time to work through any
differences in API changes.
James
> -----Original Message-----
> From: David Jencks [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 16, 2002 9:19 PM
> To: James Higginbotham
> Cc: [EMAIL PROTECTED]
> Subject: Re: Tracing classloading of an EJB
>
>
> On 2002.04.16 21:42:24 -0400 James Higginbotham wrote:
> > Is there any way to trace the classloader for an EJB to determine
> > where a class referred to by the EJB is loaded from? I need to know
> > how/why an EJB that has a newer version of Log4j (1.2beta3
> I think) in
> > its EAR is instead getting the version distributed by Jboss (1.1.3)
> > instead. Should this actually happen? Shouldn't the EJB's
> classloader
> > find the newer version in the EAR first?
>
> Not with our classloader. If its already been loaded, it
> stops looking.
> We might be able to implement some way for the server classes
> to be in a different classloader than application classes at
> some time in the future, but certainly not in 3.0
>
> I'd be interested to know if there are problems running jboss
> on Log4j 1.2.
>
> Thanks
> david jencks.
>
> >
> > Thanks,
> > James
> >
> >
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
