tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28790] New: - "connection reset by peer" and "ajp13.service() ajpGetReply recoverable error 3"
Date Wed, 05 May 2004 18:36:16 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28790>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28790

"connection reset by peer" and "ajp13.service() ajpGetReply recoverable error 3"

           Summary: "connection reset by peer" and "ajp13.service()
                    ajpGetReply recoverable error 3"
           Product: Tomcat 4
           Version: 4.1.29
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Connector:Coyote JK 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: alain@reqwireless.com


We have a successfully deployed servlet servicing 1000s of users.  We recently
switched from the following (working reasonably well) configuration:

Apache 1.3
JRE 1.4.0_03
Tomcat 4.1.29
mod_jk

to:

Apache 2.0
JRE 1.4.0_03
Tomcat 4.1.29
mod_jk2

Since making the switch, we have noticed a marked increase (5-fold) in the
number of "java.io.IOException: Connection reset by peer" instances in our
servlet logs.

We've also noticed a correlation between occurrences of these exceptions in the
servlet logs, and the following entries in the apache error log:

[Tue May 04 10:54:00 2004] [error] ajp13.service() ajpGetReply recoverable error 3
[Tue May 04 10:54:00 2004] [error] ajp13.service() Error  forwarding
ajp13:216.16.231.79:11009 1 0
[Tue May 04 10:54:00 2004] [error] mod_jk2.handler() Error connecting to tomcat
3, status 200

We aren't sure yet, but we have to assume that each such occurrence represents a
failed request by one of our users.  We have since reverted to using mod_jk
instead of mod_jk2:

Apache 2.0
JRE 1.4.0_03
Tomcat 4.1.29
mod_jk

But we are still quite interested in moving to mod_jk2, and hope to find the
solution to this problem.  We are willing to help w/ further information and
assistance.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message