Chainsaw and a broken pipe

[Tom Hallman <ha...@dm.org>]

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: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org