At 13:19 13.07.2002 -0400, you wrote:
>I've been playing around with a simple configuration of a program sending 
>its logging info
>to a central JVM and it appears that SocketAppender does what I want.
>
>However, if the central JVM is not running, the SocketAppender gives the 
>following msg:
>
>log4j:ERROR Could not connect to remote log4j server at [localhost]. We 
>will try again later.
>java.net.ConnectException: Connection refused: connect
>  at java.net.PlainSocketImpl.socketConnect(Native Method)
>  at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295)
>  at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:161)
>  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148)
>  at java.net.Socket.connect(Socket.java:425)
>  at java.net.Socket.connect(Socket.java:375)
>  at java.net.Socket.<init>(Socket.java:290)
>  at java.net.Socket.<init>(Socket.java:146)
>  at org.apache.log4j.net.SocketAppender.connect(SocketAppender.java:195)
>  at org.apache.log4j.net.SocketAppender.<init>(SocketAppender.java:145)
>  at benchmark.WorkloadConfiguration.run(WorkloadConfiguration.java:68)
>  at benchmark.WorkloadManager.main(WorkloadManager.java:186)
>
>I tried to install an ErrorHandler so that I could possibly detect this 
>situation and
>install a backup Appender, but it appears that SocketAppender is ignoring 
>the ErrorHandler
>I installed.

Correct, the SocketAppender is ignoring the error handler you installed. 
This is an omission that can be considered as a bug.


>Mike Norman

--
Ceki


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to