At 07:52 PM 2/15/2005, James Stauffer wrote:
On Tue, 15 Feb 2005 19:47:56 +0100, Ceki Gülcü <[EMAIL PROTECTED]> wrote:
>
> The most basic thing you could try is to place log4j
What?

Please ignore my comment above.


> I'd place commons-logging.jar and log4j.jar on the CLASSPATH by modifying
> catalina.sh and see what happens. Note that there must be no other copies
> of commons-logging.jar and log4j.jar anywhere else, not in Tomcat and not
> in the WEB-INF/lib directory of your web-apps.
So are you suggesting that or only suggesting it if
org.apache.commons.logging.LogFactory is set?

You are trying to give hints to JCL by setting the LogFactory system property. Don't ever do that. It will just cause Tomcat to crash.


Place commons-logging.jar and log4j.jar on the CLASSPATH by modifying catalina.sh. Make sure that no other copy of commons-logging.jar or commons-logging-api.jar or log4j exists in your system visible to Tomcat.

Try that and see what happens.

--
Ceki Gülcü

  The complete log4j manual: http://www.qos.ch/log4j/



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to