You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/02/27 06:23:50 UTC

DO NOT REPLY [Bug 27281] New: - Mod_jk2 logs a 500 error in apache access log when user presses Stop

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27281>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27281

Mod_jk2 logs a 500 error in apache access log when user presses Stop

           Summary: Mod_jk2 logs a 500 error in apache access log when user
                    presses Stop
           Product: Tomcat 4
           Version: 4.1.27
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:Coyote JK 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: pyropunk@usa.net


If the user presses the stop button in his browser, mod_jk2 will throw an error 
because the stream that it is trying to write to is closed. This error should 
NOT be returned as a 500 error code to Apache (or any other web-server for that 
matter) because it hides real 500 internal server errors (i.e. Tomcat not 
running or something equally drastic).

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