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=41923>. 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=41923 Summary: Tomcat doesnt recognized client abort Product: Tomcat 5 Version: 5.5.16 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Connector:AJP AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Hi, i'm using an apache WS with mod_jk 1.2.20 and a tomcat 5.5.xx on a linux system. I configured a loadbalancer with a worker. On this worker i set "recovery_options=4". I try to catch in my application the client abort ( the client close of http connection), but cant get it. In my application i cant recognize the close of http connection on client side. Tomcat is writing every time succesfully the response, if the client connection is alive or not. The status of the response is in every case without an error (error=false) and it's commited. The recovery_option 4, should be used to inform servlet engine about a broken client connection but it doesnt work. I tried additionally the JKoption DiableReuse, but it doesnt change the situation. Hope you can help or fix it or you have a workaround for this problem. thanks a lot for your help greeting thomsen -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
