Community
Participate
Working Groups
Build Identifier: Attached you'll find a jetty proxy provided by a client. This proxy's setup is a bit strange, but it's good to reproduce the issue. When doing a couple of page requests to different https sites jetty starts spinning and consuming cpu. Sometimes it recovers, sometimes the cpu usage stays high for a while. The DEBUG log is full of these: (don't have the logs available anymore, will reproduce the issue and add the logs). It was something like SSL_NULL_WITH_NULL messages. Reproducible: Sometimes
r2719 Fix committed. Override setWritable to stop the endpoint being scheduled for write notification on the basis that no output was written (if we are handshaking and there is no output to flush).