[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-user
Subject:    RE: SocketHubAppender support in Chainsaw
From:       Mark Womack <mwomack () bevocal ! com>
Date:       2002-06-27 17:22:59
[Download RAW message or body]

I left the existing Chainsaw code in place that created a default receiver
on port 4445 for SocketAppenders.  Actually, it looks for a property of
"chainsaw.port" and uses that number for the default port.  If it does not
find the property, it defaults to 4445.  You can set this to a different
number to avoid the clash.

It is creating a SocketReceiver, not a SocketHubReceiver.  In the future, it
would be nice if Chainsaw could read a configuration/property file to set up
a default set of receivers defined by the user.

-Mark

> -----Original Message-----
> From: Frissaer, Jeroen [mailto:jeroen.frissaer@be.unisys.com]
> Sent: Thursday, June 27, 2002 3:49 AM
> To: Log4j Mailing List (E-mail)
> Subject: RE: SocketHubAppender support in Chainsaw
> 
> 
> Mark, I quickly tested out your modifications to Chainsaw to support
> connections to the SocketHub.   Here are some issues I found 
> when testing
> locally (app and chainsaw):
> 
> When using a socket port other than 4445, everything works fine.
> When using the socket port 4445 however, things will not work:
> 
> - first starting Log4J application, afterwards Chainsaw: 
> Chainsaw gives the
> error : Unable to create socket on port 4445, quitting.  Is 
> this because by
> default Chainsaw will startup listening to port 4445 that is 
> in used by the
> SocketHubAppender?  (This issue should be resolved then when 
> using Chainsaw
> remotely)
> - first starting Chainsaw, afterwards Log4j application: 
> Log4J application
> gives the error:
> Log4J:ERROR exception setting timeout, shutting down server socket.
> java.net.BindException: Address in use: JVM_Bind
> 	at java.net.PlainSocketImpl.socketBind(Native Method)
> 	at java.net.PlainSocketImpl.bind(Unknown source)
> 	at java.net.ServerSocket.<init>(Unknown Source)
> 	at java.net.ServerSocket.<init>(Unknown Source)
> 	at
> org.apache.log4j.net.SocketHubAppender$ServerMonitor.run(Socke
> tHubAppender.j
> ava:315)
> 	at java.lang.Thread.run(Unknown Source)
> 
> 
> What do you think?
> 
> Regards 
> Jeroen
> 
> -----Original Message-----
> From: Mark Womack [mailto:mwomack@bevocal.com]
> Sent: Wednesday, June 26, 2002 7:24 PM
> To: 'Frissaer, Jeroen'; 'Eric Pugh'
> Subject: SocketHubAppender support in Chainsaw
> 
> 
> This work is preliminary, and I know that Eric is more interesting in
> modifications to LF5...but here are some modifications to 
> Chainsaw that will
> support connections to both SocketAppender and SocketHubAppender.  I'm
> sending it out to you directly instead of the whole user list 
> to get some
> initial feedback.
> 
> There is a new "Connect" menu with 2 menu items: "Connect 
> to..." connects to
> SocketHubAppenders; "Accept connection on..." supports 
> connections from
> SocketAppenders.
> 
> You will need to place the included jar in front of the 
> log4j.jar in your
> classpath for these changes to take affect.  Use at your own 
> risk as I have
> not performed a lot of testing.  Review the changes if you 
> have a chance.
> It needs to be cleaned up some, but the basic idea is there.
> 
> Eric, I am going to look at LF5 next.  Do you have any 
> recommendations?
> 
> -Mark
> 
>  <<chainsaw_mods_v2.zip>> 
> 
> --
> To unsubscribe, e-mail:   
<mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>

--
To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>

[prev in list] [next in list] [prev in thread] [next in thread]