DO NOT REPLY [Bug 45661] NioBlockingSelector uses all CPU after a socket connection is killed

https://issues.apache.org/bugzilla/show_bug.cgi?id=45661 Filip Hanik <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 45661] NioBlockingSelector uses all CPU after a socket connection is killed

https://issues.apache.org/bugzilla/show_bug.cgi?id=45661 Filip Hanik <[EMAIL PROTECTED]> changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |tomcat-

DO NOT REPLY [Bug 45661] NioBlockingSelector uses all CPU after a socket connection is killed

https://issues.apache.org/bugzilla/show_bug.cgi?id=45661 Filip Hanik <[EMAIL PROTECTED]> changed: What|Removed |Added AssignedTo|tomcat- |[EMAIL PROTECTED]

DO NOT REPLY [Bug 45661] NioBlockingSelector uses all CPU after a socket connection is killed

https://issues.apache.org/bugzilla/show_bug.cgi?id=45661 Filip Hanik <[EMAIL PROTECTED]> changed: What|Removed |Added Status|RESOLVED|REOPENED

DO NOT REPLY [Bug 45661] NioBlockingSelector uses all CPU after a socket connection is killed

https://issues.apache.org/bugzilla/show_bug.cgi?id=45661 --- Comment #2 from Alan Yu <[EMAIL PROTECTED]> 2008-08-22 21:01:11 PST --- I am using the latest JDK 1.6.0_07 already and the problem still exists. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ---

DO NOT REPLY [Bug 45661] NioBlockingSelector uses all CPU after a socket connection is killed

https://issues.apache.org/bugzilla/show_bug.cgi?id=45661 Filip Hanik <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |RESOLVED