[EMAIL PROTECTED] wrote:
>
> I am somewhat new to log4j but am looking forward to gaining experience with it
> and possibly contributing to the product itself. Being a totally blind
> programmer, many interactive debugging tools are not productively useful to me
> through my speech/Braille output software. However, log4j seems to give me a
> controllable output which is very easy to read and understand.
>
> I have setup a script on an AIX machine to run the SimpleSocketServer class and
> configured my client application (running on Windows NT) to send log records to
> that server. The log records are coming through to the server just fine and
> everything looks good until the client application ends. Then I get the error
> message below on the output of the log server.
>
> [2001-06-21 11:12:21] net.SocketNode() - Unexpected exception. Closing
> conneciton.
> java.io.IOException: A connection with a remote socket was reset by that socket.
> at java.net.SocketInputStream.read(Compiled Code)
> at java.net.SocketInputStream.read(Compiled Code)
> at java.io.ObjectInputStream.peekCode(Compiled Code)
> at java.io.ObjectInputStream.refill(Compiled Code)
> at java.io.ObjectInputStream.readObject(Compiled Code)
> at java.io.ObjectInputStream.readObject(Compiled Code)
> at org.apache.log4j.net.SocketNode.run(Compiled Code)
> at java.lang.Thread.run(Compiled Code)
The SimpleSocketServer handles EOFException and SocketExceptions as
indicative of a graceful shutdown, but not IOExceptions. This is why it
logs the exception stacktrace. This is probably not the best behaviour
given that current log4j clients will not usually close the sockets
before exiting.
>
> I have tried putting a finalize method in my application with a .shutdown() call
> to the two category names being used.
Category.shutdown is a static method -- no point in invoking it twice.
Cheers,
Anders
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
