Problems with org.apache.log4j.net.SocketAppender

[Thomas Tuft Muller <tt...@online.no>]

Log4j gurus,

I am experiencing some problems transferring log-entries across a network
connection using org.apache.log4j.net.SocketAppender. The log-files on the
server-side "miss" a lot of entries, probably due to serialization problems
on the client-side. This is what I found in stderr:

2002-01-30 09:34:03,973 - "log4j:WARN Detected problem with connection:
java.io.NotSerializableException: org.apache.log4j.spi.VectorWriter"
2002-01-30 09:39:06,578 - "log4j:WARN Detected problem with connection:
java.io.NotSerializableException: org.apache.log4j.spi.VectorWriter"
2002-01-30 09:39:49,259 - "log4j:WARN Detected problem with connection:
java.io.NotSerializableException: org.apache.log4j.spi.VectorWriter"
2002-01-30 09:41:22,243 - "log4j:WARN Detected problem with connection:
java.io.NotSerializableException: org.apache.log4j.spi.VectorWriter"
2002-01-30 09:42:43,831 - "log4j:WARN Detected problem with connection:
java.net.SocketException: Connection reset by peer: socket write error"
2002-01-30 09:50:35,328 - "log4j:WARN Detected problem with connection:
java.io.NotSerializableException: org.apache.log4j.spi.VectorWriter"
2002-01-30 09:51:16,718 - "log4j:WARN Detected problem with connection:
java.io.NotSerializableException: org.apache.log4j.spi.VectorWriter"
2002-01-30 09:52:01,743 - "log4j:WARN Detected problem with connection:
java.io.NotSerializableException: org.apache.log4j.spi.VectorWriter"
2002-01-30 09:52:38,155 - "log4j:WARN Detected problem with connection:
java.io.NotSerializableException: org.apache.log4j.spi.VectorWriter"

The number of entries in std err does not reflect the number of missing
entries. This number is massive. When I compare the log-files produced
locally where the application resides and the log-files produced by the
log-server (it uses the exact same log4j.xml file), approximately 50% of the
entries are missing on the log-server side.

I've used this code for 6 months with no problems, these problems appeared
after we created a new version of the core application, and introduced some
changes to the log4j.xml file.

Regards,

--

Thomas

Please find log4j.xml file attached.

Any ideas why this is happening and fix would be much appreciated.


*************************************************************************
Copyright ERA Technology Ltd. 2001. (www.era.co.uk). All rights reserved. 
Confidential. No liability whatsoever is accepted for any loss or damage 
suffered as a result of accessing this message or any attachments.