I have defined a very simple SocketAppender to a log4J 1.2.8 client application
log4j.appender.SockLog=org.apache.log4j.net.SocketAppender log4j.appender.SockLog.RemoteHost=localhost log4j.appender.SockLog.Port=4451 #log4j.appender.SockLog.LocationInfo=true log4j.appender.SockLog.Threshold=WARN
A very simple SocketReceiver is configured for the "listener" server
<plugin name="Log4JSocketReceiver" class="org.apache.log4j.net.SocketReceiver"> <param name="Port" value="4451"/> </plugin>
1) I have read about a bug in log4J 1.3 that prevents the LocationInfo propertery being set to true. When will this be fixed ? I need the location info for remote debugging
You are mixing 1.2.8 and 1.3 on the client and server side? This won't work.
2) When I have the listener server down and run the client application, I
expect only a "couldn't connect" terse error message.
Instead I get the full java.net.ConnectException + stack trace .
Not exactly simply dropped.
Note this is from the initialization code, not subsequent
loggings.
Is there anyway to avoid this message. I want the application to
use the socket if it is available, else ignore it.
(Note that log4perl handles this very situation very cleanly)
This was supposed to be fixed in 1.3.
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/eclm
Professional log4j support: http://qos.ch/log4jSupport
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
