Assuming you're using a 1.3 log4j.jar, this config looks fine. If somehow you're still using a 1.2.8 jar, making these changes might fix it:
Change this line: log4j.appender.chainsaw.locationInfo=true to this: log4j.appender.chainsaw.locationInfo=false Just in case you change your pattern layout some time in the future to include line/file/method etc., move the chainsaw appender to the first appender in this list - change this line: log4j.rootLogger=INFO,all,chainsaw to this: log4j.rootLogger=INFO,chainsaw,all One way to see if you're using 1.3 is to try an appender that's only available with 1.3 - like org.apache.log4j.net.MulticastAppender. If it's available, you're using 1.3. (there may be a better way, but I'm not sure how). Scott -----Original Message----- From: Tom Hallman [mailto:[EMAIL PROTECTED] Sent: Tue 1/25/2005 10:22 AM To: Log4J Users List Cc: Subject: Re: Chainsaw and a broken pipe Hello again Scott, Thank you for your continued support in getting Chainsaw working properly! > Upgrading your app's version of log4j doesn't necessarily mean that's > the version of log4j being used by your app (if you're using the > parent-first classloader behavior and log4j is loaded by a parent > classloader). Okay. I replaced 1.2.8's jar file in my Tomcat server with the 1.3a, and restarted it. So at this point, the only version being used in my project should be 1.3a. Is there a way I can verify this programmatically? > Recycling your web app could be causing the broken pipe. Recycling - is that when I redeploy the app? > If you include your complete config file and more stack trace > information we might be able to figure it out. Great! Attached is the complete log4j.properties file located in my WEB-INF/classes/ directory. It correctly generates all output to the log files specified. When I load up Chainsaw, I just create the socketreceiver on 4445. Is there anything else I need to do? Whenever I try to use the logger (with or without redeploying), I get this message: log4j:WARN Detected problem with connection: java.net.SocketException: Broken pipe Is there other info I could send you? Thanks again Scott. ~Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
