OK, little description
1. JBoss load /lib/ext/log4j.jar for it's own use
2. My ejb need log4j classes, but can't use classes loaded by jboss
3. If I add log4j.jar in JBOSS_CLASSPATH, I get an error (i'm not in office
to post the trace) cause I load twice the .jar
4. All 'external application' (for example, caucho's resin) that load jboss
client jars stop logging to log4j, it seems they do not see their private
That's a real problem. Up to jboss version 2.2.2 all works fine.
[mailto:jboss-user-admin@... Behalf Of Guy
Sent: jeudi, 29. novembre 2001 19:07
Subject: Re: [JBoss-user] Eternal problem : JBoss 2.4.3 and Log4J
Sorry, I don't understand the issue. JBoss using log4j for logging - you
can't delete it from lib/ext. What is the original problem you were trying
to solve by deleting lib/ext/log4j.jar? Can't you just add JBoss's
lib/ext/log4j.jar to the classpath used by your apps?
----- Original Message -----
From: "Gianni Gottardi" <gianni.gottardi@...>
To: "JBoss" <jboss-user@...>
Sent: Thursday, November 29, 2001 11:04 AM
Subject: [JBoss-user] Eternal problem : JBoss 2.4.3 and Log4J
> I already read a lot of messages of people having problems like mine. I'm
> trying to update from jboss 2.2.2 to 2.4.3 to take advantage from the
> JBossMQ devel. but no way my ejb will deploy!!
> JBoss load it's private log4j.jar, any try to get it works with my apps
> Any other suggestion ?
> - Deleted the MLET CODE : JBOSS does not log (apps work with classpath's
> - Deleted the log4j.jar from /lib/ext : : JBOSS does not log JBOSS does
> log (apps work with classpath's log4j)
> - No log4j in classpath : JBOSS works, apps do not find the
> ......all apps that load the jboss-clients jar to connect to
> (jbosssx-client,jboss-client, etc) did not log anymore ! It seems they
> completely ignore their private log4j.properties file.
> Please help
> JBoss-user mailing list
JBoss-user mailing list