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=42754>. 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=42754 Summary: Infinite loop after comet event breaks Product: Tomcat 6 Version: unspecified Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P1 Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Tomcat version: 6.0.13 When a handling a Comet BEGIN event and not reading all bytes and returning, a SEVERE error is caused by Tomcat. However the CometProcessor does not get notified of this error (it receives no further events at all). Resources allocated in the BEGIN event cannot be freed, causing a possible resource leak. Also (at least when there is data in the buffer), Tomcat enters a busy handling loop eating 100% CPU time. Preliminary debugging showed that the Comet event type is set to END in this loop, but only the event() method on an ErrorValve is called, and the event method of the CometProcessor which received the BEGIN event is not called. -- 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]
