On Mon, 2008-10-06 at 10:51 -0700, Jacob Anderson wrote:
> Hello,
> 
> Last night I saw this error in the pound log:
> 
> Oct  6 03:11:35 angel1 pound: 82.204.3.186 GET / HTTP/1.1 - HTTP/1.1 302
> Moved Temporarily
> (1) Oct  6 03:11:35 angel1 pound: 82.204.3.186 GET /index.html HTTP/1.1 -
> HTTP/1.1 200 OK 
> Oct  6 03:11:35 angel1 pound: (f3bc0003) error copy server cont: Connection
> reset by peer
> 
> The BE handling this connection reported:
> 
> 2008-10-06 03:11:36 StandardWrapperValve[default]: Servlet.service() for
> servlet default threw exception
> ClientAbortException:  java.net.SocketException: Broken pipe
>         at
> org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:370)
> 
> When (1) occurs, there is a client-side javascript that redirects the user
> to the correct "https" URL that requests login.
> 
> I saw it again this morning, but on a different URL:
> 
> Oct  6 09:21:20 angel1 pound: 203.92.60.130 POST /login.do;jsessionid=[...]
> HTTP/1.1 - HTTP/1.1 302 Moved Temporarily
> Oct  6 09:21:21 angel1 pound: (f5014006) error copy server cont: Connection
> reset by peer
> 
> On the BE:
> 
> 2008-10-06 09:21:22 StandardWrapperValve[default]: Servlet.service() for
> servlet default threw exception
> ClientAbortException:  java.net.SocketException: Broken pipe
>         at
> org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:370)
> 
> The time on these servers are synchronized. The pound server is the time
> server for all of the BE servers.
> 
> This definitely looks as if the pound process is killing the BE connection
> prematurely. Clearly the error is not originating in the BE as was suspected
> in the past. Either the connection is being killed on the client, or else
> pound is cutting off the connection.
> 
> This is Pound 2.4.3 on Centos 4 using kernel 2.6.9-67.0.15.ELsmp

Increase your BE time-out to avoid this.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904


--
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.

Reply via email to