ClientAbortException stacktrace lines log as separate Log4J events.

A ClientAbortException is raised legitimately when an end-user closes thier browser before the web app is finished responding to the request.

However, when the stacktrace is generated, it seems that each line is being logged using separate Log4J logger.log() call. This results in a nice looking file-base log:

2007-08-27 09:10:31,402 ERROR [STDERR] ClientAbortException: java.net.SocketException: Broken pipe
2007-08-27 09:10:31,640 ERROR [STDERR] at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366)
2007-08-27 09:10:31,937 ERROR [STDERR] at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:353)
2007-08-27 09:10:32,131 ERROR [STDERR] at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392)
2007-08-27 09:10:32,326 ERROR [STDERR] at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381)
2007-08-27 09:10:32,607 ERROR [STDERR] at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:88)
...

But it causes unnecessary grief and clutter when using SMTP to log errors. Each line results in a separate email! So my inbox fills with an average of 60 emails per ClientAbortException!

This problem seems to confined to the ClientAbortException. Other errors log the stacktrace as a single Log4J event. Please may I have this error logged in the same way?

Ta.