toClient.close();
} catch (Exception e) {
System.err.println("Exception in doGet: "+e.toString());
} finally {
servedThreads--;
}
}
}
-Original Message-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: den 13 januari 2010 18:46
To:
essage-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: den 13 januari 2010 16:13
To: Tomcat Users List
Subject: Re: NIO-connector problems (excessive CPU-usage)
yes, the issue is known. However, we have not been able to create a use
case for it, since I've never been
at java.lang.Thread.run(Thread.java:619)
/Tobias
-Original Message-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: den 13 januari 2010 16:13
To: Tomcat Users List
Subject: Re: NIO-connector problems (excessive CPU-usage)
yes, the issue is known. However, we have not b
yes, the issue is known. However, we have not been able to create a use
case for it, since I've never been able to reproduce it.
One of the work arounds would be to close the selector, but that is a
royal pain, since you'd then have to reregister all keys and you'd end
up in a synchronization ni
Hi!
We've been using Tomcat on Linux for a very long time (and the good old
JServe before it), and we recently started testing the NIO-connector instead
of the old blocking one. We are currently running the latest Tomcat v6.0.20.
We have a pretty large website with quite a lot of traffic, and s
