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=42218>. 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=42218 Summary: CLIENT_DISCONNECT event missing Product: Tomcat 6 Version: 6.0.11 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The behavior is easily reproducible for both Http11AprProtocol and Http11NioProtocol by running my corrected test webapp from bug 42198 ( http://issues.apache.org/bugzilla/attachment.cgi?id=20025 ) in Tomcat 6 compiled from trunk with the Servlet init parameter 'maxTimeout' set to 100 in web.xml. Load the index page into a browser. When the page has started polling, close the browser. The Servlet's event method will get a READ event, tries to read from the input stream, but there is nothing to read. Therefore, it simply returns. However, it gets the READ presented again and again (with 100% CPU) until the response is closed by the response provider thread. Should the Servlet itself interpret a READ event with no bytes to read as a client disconnect and close the event? -- 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]
