I noticed that both servicemix 3.1 and 3.1.1 utilizing jetty 6.0.1, which has a pretty nasty bug that has to do with Java 1.5 NIO bug. We replaced the library and CPU seemed to go back to 0% on Windows.
Anybody has any comments on this? Is servicemix team planning to put newer version of jetty in http-bc in future versions? http://jira.codehaus.org/browse/JETTY-256 -- View this message in context: http://www.nabble.com/HTTP-BC-Jetty-6.0.1-100--CPU-BUG-tf4497623s12049.html#a12826656 Sent from the ServiceMix - User mailing list archive at Nabble.com.
