As per Jetty Issue#4492 which was created to report the failure to process requests we have been told that our code is wrong.
Jesse Glick verified the fix in [ https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96]6 (https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe
We need to
slack: https://cloudbees.slack.com/archives/CBXU9VCGL/p1579285074024500?thread_ts=1579193579.070300&cid=CBXU9VCGL
removing the thread naming means the threadpool uses threads starting with "qtp" rather than "Jetty Thread Pool"
maven-hpi-plugin seems unaffected
winstone allows for configuration of the acceptors and selectors and the max # threads (which by default uses Jetty defaults)
James Nord Winstone fix was shipped in 2.218. Do we need to keep this issue open?
Jenkins test harness has not been released yet but happy to close as it's been merged, just not sure on the process for jth
I will cut the Jetty release
The links provided in the issue description are broken. I assume they are private links.
According to the CHANGELOG, we are able to update the status of this issue. It is already released.
the link to jetty issue is public. the verification was a private repo