I had the same problem using TomCat. You are right to remove it from the jar. To log to a file you will need to modify the log4j.properties file as well (e.g. uncomment line 3).
You might try setting the system property log4j.debug=true when the JVM starts. This will show what Log4J is trying to do (on stdout or stderr). What I ended up doing is creating an "Initialization servlet" as suggested in the Log4J "introductory manual" because I didn't want to monkey with the TomCat startup script. But if you can customize your application's or server's CLASSPATH I would try including the directory where log4j.properties resides. -----Original Message----- From: Herrick, Mike [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 12:33 PM To: '[EMAIL PROTECTED]' Subject: problem with logging Hi, I have an odd problem. I've installed Axis on a number of machines running WLS 7.2 and Axis logs to the console "out of the box". On the particular machine I'm working on, I can't get it to log. I tried removing the log4j.properties from the axis.jar and adding it to the axis/WEB-INF/classes directory, but it didn't help. Am I missing something? Any ideas? Best regards, Mike
