ClientAbortException (broken pipe) serving error pages

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

ClientAbortException (broken pipe) serving error pages

Hansen
Hi,

I frequently receive the following exception. It indicates that the
connection is reset when sending the error page to the client. This kind of
exception is normal OK to ignore. But before I change the log level for the
corresponding package to get rid of the noise, I want to make sure that this
dose not imply other similar problems that anyone has experience and which I
should not ignore.

For further information, I am running ofbiz on port 8080/8443 and have
iptables to forward 80/443 to them.

Thanks,
Hansen

2009-03-10 14:54:46,651 (http-0.0.0.0-8080-Processor287) [
StandardHostValve.java:288:WARN ] Exception Processing
ErrorPage[errorCode=404, location=/]
ClientAbortException:  java.net.SocketException: Broken pipe
        at
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:327)
        at
org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293)
        at
org.apache.catalina.connector.Response.flushBuffer(Response.java:537)
        at
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:286)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
        at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
        at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
        at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
        at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:636)
Reply | Threaded
Open this post in threaded view
|

Re: ClientAbortException (broken pipe) serving error pages

Jacques Le Roux
Administrator
I'd recommend to use this instead of iptables
http://docs.ofbiz.org/display/OFBIZ/FAQ+-+Tips+-+Tricks+-+Cookbook+-+HowTo#FAQ-Tips-Tricks-Cookbook-HowTo-Howtousemodproxyajp

Jacques

From: "Hansen Wang" <[hidden email]>

> Hi,
>
> I frequently receive the following exception. It indicates that the
> connection is reset when sending the error page to the client. This kind of
> exception is normal OK to ignore. But before I change the log level for the
> corresponding package to get rid of the noise, I want to make sure that this
> dose not imply other similar problems that anyone has experience and which I
> should not ignore.
>
> For further information, I am running ofbiz on port 8080/8443 and have
> iptables to forward 80/443 to them.
>
> Thanks,
> Hansen
>
> 2009-03-10 14:54:46,651 (http-0.0.0.0-8080-Processor287) [
> StandardHostValve.java:288:WARN ] Exception Processing
> ErrorPage[errorCode=404, location=/]
> ClientAbortException:  java.net.SocketException: Broken pipe
>        at
> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:327)
>        at
> org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293)
>        at
> org.apache.catalina.connector.Response.flushBuffer(Response.java:537)
>        at
> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:286)
>        at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136)
>        at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>        at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>        at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
>        at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>        at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>        at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>        at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>        at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>        at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>        at java.lang.Thread.run(Thread.java:636)
>

Reply | Threaded
Open this post in threaded view
|

Re: ClientAbortException (broken pipe) serving error pages

Hansen
I do not think there are advantages to use apache in front of tomcat just
for port forwarding unless there are other concerns using iptables.

Thanks,
Hansen

On Wed, Mar 11, 2009 at 1:17 AM, Jacques Le Roux <
[hidden email]> wrote:

> I'd recommend to use this instead of iptables
>
> http://docs.ofbiz.org/display/OFBIZ/FAQ+-+Tips+-+Tricks+-+Cookbook+-+HowTo#FAQ-Tips-Tricks-Cookbook-HowTo-Howtousemodproxyajp
>
> Jacques
>
> From: "Hansen Wang" <[hidden email]>
>
>  Hi,
>>
>> I frequently receive the following exception. It indicates that the
>> connection is reset when sending the error page to the client. This kind
>> of
>> exception is normal OK to ignore. But before I change the log level for
>> the
>> corresponding package to get rid of the noise, I want to make sure that
>> this
>> dose not imply other similar problems that anyone has experience and which
>> I
>> should not ignore.
>>
>> For further information, I am running ofbiz on port 8080/8443 and have
>> iptables to forward 80/443 to them.
>>
>> Thanks,
>> Hansen
>>
>> 2009-03-10 14:54:46,651 (http-0.0.0.0-8080-Processor287) [
>> StandardHostValve.java:288:WARN ] Exception Processing
>> ErrorPage[errorCode=404, location=/]
>> ClientAbortException:  java.net.SocketException: Broken pipe
>>       at
>> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:327)
>>       at
>> org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293)
>>       at
>> org.apache.catalina.connector.Response.flushBuffer(Response.java:537)
>>       at
>>
>> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:286)
>>       at
>>
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136)
>>       at
>>
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>>       at
>>
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>>       at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
>>       at
>>
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>>       at
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>>       at
>>
>> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>>       at
>>
>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>>       at
>>
>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>>       at
>>
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>>       at java.lang.Thread.run(Thread.java:636)
>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: ClientAbortException (broken pipe) serving error pages

Jacques Le Roux
Administrator
Yes, I suggested because mod_rewrite and let HTTPD deals with static content are often needed also...

Jacques

From: "Hansen Wang" <[hidden email]>

>I do not think there are advantages to use apache in front of tomcat just
> for port forwarding unless there are other concerns using iptables.
>
> Thanks,
> Hansen
>
> On Wed, Mar 11, 2009 at 1:17 AM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> I'd recommend to use this instead of iptables
>>
>> http://docs.ofbiz.org/display/OFBIZ/FAQ+-+Tips+-+Tricks+-+Cookbook+-+HowTo#FAQ-Tips-Tricks-Cookbook-HowTo-Howtousemodproxyajp
>>
>> Jacques
>>
>> From: "Hansen Wang" <[hidden email]>
>>
>>  Hi,
>>>
>>> I frequently receive the following exception. It indicates that the
>>> connection is reset when sending the error page to the client. This kind
>>> of
>>> exception is normal OK to ignore. But before I change the log level for
>>> the
>>> corresponding package to get rid of the noise, I want to make sure that
>>> this
>>> dose not imply other similar problems that anyone has experience and which
>>> I
>>> should not ignore.
>>>
>>> For further information, I am running ofbiz on port 8080/8443 and have
>>> iptables to forward 80/443 to them.
>>>
>>> Thanks,
>>> Hansen
>>>
>>> 2009-03-10 14:54:46,651 (http-0.0.0.0-8080-Processor287) [
>>> StandardHostValve.java:288:WARN ] Exception Processing
>>> ErrorPage[errorCode=404, location=/]
>>> ClientAbortException:  java.net.SocketException: Broken pipe
>>>       at
>>> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:327)
>>>       at
>>> org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293)
>>>       at
>>> org.apache.catalina.connector.Response.flushBuffer(Response.java:537)
>>>       at
>>>
>>> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:286)
>>>       at
>>>
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136)
>>>       at
>>>
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>>>       at
>>>
>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>>>       at
>>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
>>>       at
>>>
>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>>>       at
>>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>>>       at
>>>
>>> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>>>       at
>>>
>>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>>>       at
>>>
>>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
>>>       at
>>>
>>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>>>       at java.lang.Thread.run(Thread.java:636)
>>>
>>>
>>
>