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=4663>.
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=4663

Broken Pipe under some load

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
          Component|Catalina                    |Connector:Coyote JK 2
         OS/Version|Solaris                     |Linux
           Platform|Sun                         |All
         Resolution|INVALID                     |
            Version|4.1.29                      |4.1.30



------- Additional Comments From [EMAIL PROTECTED]  2004-07-25 22:03 -------
I have a servlet which takes a couple of seconds to execute.
When I request this servlet thro browser, and press stop button after a moment, 
I see the exception with stack trace.

org.apache.jk.server.JkCoyoteHandler action
SEVERE: Error in action code
java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)


The problem here is not with the exception, but I clearly notice that the 
request comes to tomcat again and gets processed successfully, but the response 
is not given to the client (browser).

We are on Apache 2 + Tomcat 4.1.30 + Mod_jk2 on Linux (RHEL 3).

I have done this testing for a week, and I am able to reproduce this bug at 
will and also I am 100% sure about the servlet getting invoked twice.

I can cleary see in apache access log that the request came from client only 
once, but in apache error log (mod_jk log), I can see mod_jk openign connection 
twice to tomcat. :-(

Can you please suggest me a solution for this problem.

Thanks
Surendra

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to