Ok the issue appears to be related to the state the connection handler
thinks it is in, after the connection is disconnected the state returned
by org.apache.coyote.http11.Http11Processor.process remains as OPEN, which
causes the underlying poll thread to get notified and repeats.
Breakpointing on
Hi Mark,
Thanks for the response - So far I've narrowed down to this;
0 - ntoskrnl.exe!KeSynchronizeExecution+0x2246
1 - ntoskrnl.exe!KeWaitForMultipleObjects+0x135e
2 - ntoskrnl.exe!KeWaitForMultipleObjects+0xdd9
3 - ntoskrnl.exe!KeWaitForSingleObject+0x373
4 - ntoskrnl.exe!Ke
On 04/01/2017 16:02, David Oswell wrote:
> Hello all,
>
> wondering if anyone has seen similar behaviour - sorry if already reported,
> googling hasn't found much other than a somewhat similar older issue on APR
> going to 100% CPU when idle due to a poll loop/timeout issue - however this
> seems
Hello all,
wondering if anyone has seen similar behaviour - sorry if already reported,
googling hasn't found much other than a somewhat similar older issue on APR
going to 100% CPU when idle due to a poll loop/timeout issue - however this
seems a bit different as this is only occurring with SSL;
