[jboss-jira] [JBoss JIRA] Resolved: (JBAS-4633) ClientAbortException stacktrace lines log as separate Log4J events.

[Remy Maucherat (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4633?page=all ]

Remy Maucherat resolved JBAS-4633.
----------------------------------

    Resolution: Rejected

This occurs because the exception is, somewhere, caught and printed to the standard error stream (intended to go to the console), and is captured and reprocessed by log4j. You need to look and find where this happens.

> ClientAbortException stacktrace lines log as separate Log4J events.
> -------------------------------------------------------------------
>
>                 Key: JBAS-4633
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4633
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.0.5.GA
>         Environment: SuSE Linux 10.0
>            Reporter: Matthew Robinson
>         Assigned To: Remy Maucherat
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira