-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
When confluence returns HTTP 404 via /fourohfour.action and client aborts the connection as soon as it receives HTTP status code an IllegalStateException. This is really cluttering the logs. Please catch the exception and log it only in when the logging level is DEBUG.
It would be great to have this fix similarly to CONF-9984.
thanks!
An example of the exception:
[13/Jun/2008:09:48:55] failure (10952): for host 76.191.145.205 trying to GET /display/JapanSoftwareCommunity/.bookmarks/register.php/, service-j2ee reports: org.apache.catalina.core.StandardHostValve@772746: Exception Processing ErrorPage[errorCode=404, location=/fourohfour.action] ClientAbortException: java.io.IOException: WEB8001: Write failed at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:385) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:404) at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:334) at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:313) at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java:622) at com.sun.webserver.connector.nsapi.NSAPIResponse.flushBuffer(NSAPIResponse.java:127) at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFacade.java:291) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:389) at org.apache.catalina.core.StandardHostValve.postInvoke(StandardHostValve.java:207) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:587) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:556) at com.sun.webserver.connector.nsapi.NSAPIProcessor.service(NSAPIProcessor.java:160) Caused by: java.io.IOException: WEB8001: Write failed at com.sun.webserver.connector.nsapi.NSAPIResponseStream.doWrite(NSAPIResponseStream.java:61) at org.apache.coyote.Response.doWrite(Response.java:575) at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:380) ... 11 more
- relates to
-
CONFCLOUD-12147 IllegalStateException from fourohfour.action
- Closed
[CONFSERVER-12147] IllegalStateException from fourohfour.action
Workflow | Original: JAC Suggestion Workflow 4 [ 3569626 ] | New: JAC Suggestion Workflow 3 [ 4333422 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3174975 ] | New: JAC Suggestion Workflow 4 [ 3569626 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3031924 ] | New: JAC Suggestion Workflow 2 [ 3174975 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2534050 ] | New: JAC Suggestion Workflow [ 3031924 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2294152 ] | New: Confluence Workflow - Public Facing v4 [ 2534050 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2189055 ] | New: Confluence Workflow - Public Facing v3 [ 2294152 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1919142 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2189055 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1755005 ] | New: Confluence Workflow - Public Facing v3 [ 1919142 ] |
Description |
Original:
When confluence returns HTTP 404 via /fourohfour.action and client aborts the connection as soon as it receives HTTP status code an IllegalStateException. This is really cluttering the logs. Please catch the exception and log it only in when the logging level is DEBUG.
It would be great to have this fix similarly to [ thanks! An example of the exception: {noformat} [13/Jun/2008:09:48:55] failure (10952): for host 76.191.145.205 trying to GET /display/JapanSoftwareCommunity/.bookmarks/register.php/, service-j2ee reports: org.apache.catalina.core.StandardHostValve@772746: Exception Processing ErrorPage[errorCode=404, location=/fourohfour.action] ClientAbortException: java.io.IOException: WEB8001: Write failed at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:385) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:404) at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:334) at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:313) at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java:622) at com.sun.webserver.connector.nsapi.NSAPIResponse.flushBuffer(NSAPIResponse.java:127) at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFacade.java:291) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:389) at org.apache.catalina.core.StandardHostValve.postInvoke(StandardHostValve.java:207) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:587) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:556) at com.sun.webserver.connector.nsapi.NSAPIProcessor.service(NSAPIProcessor.java:160) Caused by: java.io.IOException: WEB8001: Write failed at com.sun.webserver.connector.nsapi.NSAPIResponseStream.doWrite(NSAPIResponseStream.java:61) at org.apache.coyote.Response.doWrite(Response.java:575) at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:380) ... 11 more {noformat} |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-12147]. {panel} When confluence returns HTTP 404 via /fourohfour.action and client aborts the connection as soon as it receives HTTP status code an IllegalStateException. This is really cluttering the logs. Please catch the exception and log it only in when the logging level is DEBUG. It would be great to have this fix similarly to [ thanks! An example of the exception: {noformat} [13/Jun/2008:09:48:55] failure (10952): for host 76.191.145.205 trying to GET /display/JapanSoftwareCommunity/.bookmarks/register.php/, service-j2ee reports: org.apache.catalina.core.StandardHostValve@772746: Exception Processing ErrorPage[errorCode=404, location=/fourohfour.action] ClientAbortException: java.io.IOException: WEB8001: Write failed at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:385) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:404) at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:334) at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:313) at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java:622) at com.sun.webserver.connector.nsapi.NSAPIResponse.flushBuffer(NSAPIResponse.java:127) at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFacade.java:291) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:389) at org.apache.catalina.core.StandardHostValve.postInvoke(StandardHostValve.java:207) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:587) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:556) at com.sun.webserver.connector.nsapi.NSAPIProcessor.service(NSAPIProcessor.java:160) Caused by: java.io.IOException: WEB8001: Write failed at com.sun.webserver.connector.nsapi.NSAPIResponseStream.doWrite(NSAPIResponseStream.java:61) at org.apache.coyote.Response.doWrite(Response.java:575) at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:380) ... 11 more {noformat} |
Link |
New:
This issue relates to |