Scott,
Thanks very much for your prompt response! I upgraded my app's version of log4j to 1.3a (just like Chainsaw's), but to no avail. Any other thoughts as to what the "broken pipe" might refer to?
Thanks again!
~Tom
Scott Deboy wrote:
SocketAppender sends serialized loggingEvents over the wire, and serialization of loggingEvents from 1.2.8 to 1.3 has been broken - both MDC and LocationInfo (file/line/method/class) are not available.
You might be able to use a 1.2.8 socketappender if you make sure you aren't creating LocationInfo (the socketappender is the first appender in the list and locationinfo is not set to true), and you aren't using MDC.
If you're using MDC or want location info, I'd suggest using a fileappender that contained your MDC keys and location info patterns, and use a LogFilePatternReceiver on the Chainsaw side (see the JavaDoc for LogFilePatternReceiver for info, available from Chainsaw's help menu).
There's a sample config file available from Chainsaw's Welcome tab that shows how to set up a LogFilePatternReceiver.
Hope this helps, Scott
-----Original Message----- From: Tom Hallman [mailto:[EMAIL PROTECTED]
Sent: Mon 1/24/2005 2:02 PM To: [email protected] Cc: Subject: Chainsaw and a broken pipe Hey guys,
That might be the greatest code-related subject line I've ever used.
Anyhow, probable newbie question here. I just got log4j set up for a webapp of mine. The log4j.properties file says, in part:
----
################################################ # By default, log everything of INFO or higher log4j.rootLogger=INFO,chainsaw
######################### # Appender for Chainsaw
log4j.appender.chainsaw=org.apache.log4j.net.SocketAppender log4j.appender.chainsaw.remoteHost=localhost log4j.appender.chainsaw.port=4445 log4j.appender.chainsaw.locationInfo=false
----
Now, when I load up Chainsaw, it asks me if I'd like to set up a SocketReceiver on port 4445. Sounds great! So I do, but nothing happens after that. I see a "SimpleReceiver" but even when my logger
is happily spitting out details to files, it doesn't seem to be
getting to Chainsaw.
I tried watching the 4445 port via ethereal, and it sees that "connections" are indeed being made, but it doesn't look like actual
data is being sent.
When I deploy my webapp (to Tomcat), the log files come alive, but I get this message:
Jan 24, 2005 4:06:31 PM org.apache.catalina.startup.HostConfig
deployWAR INFO: Deploying web application archive Myapp.war log4j:WARN Detected problem with connection:
java.net.SocketException: Broken pipe
Any idea why this might be happening? I'm really quite new to this, so any help would be appreciated!
For reference, I'm using log4j 1.2.8 in my webapp, and it appears that Chainsaw is using 1.3a.
Thanks VERY much!
~Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
