Thread.interrupt() is called in many places in code.
jetty-ant
org.eclipse.jetty.ant
AntBuild
stop()
_process.interrupt();
jetty-server
org.eclipse.jetty.server
AbstractConnector
interruptAcceptors()
thread.interrupt();
AsyncRequestLogWriter
doStop()
_thread.interrupt();
ResponseWriter
write(int)
Thread.currentThread().interrupt();
write(char[], int, int)
Thread.currentThread().interrupt();
write(String, int, int)
Thread.currentThread().interrupt();
println()
Thread.currentThread().interrupt();
println(char)
Thread.currentThread().interrupt();
println(char[])
Thread.currentThread().interrupt();
println(String)
Thread.currentThread().interrupt();
format(Locale, String, Object...)
Thread.currentThread().interrupt();
jetty-servlets
org.eclipse.jetty.servlets
DoSFilter
onRequestTimeout(HttpServletRequest, HttpServletResponse, Thread)
handlingThread.interrupt();
jetty-util
org.eclipse.jetty.util
LeakDetector
doStop()
thread.interrupt();
SocketAddressResolver.Async
resolve(String, int, Promise<List<InetSocketAddress>>)
thread.interrupt();
org.eclipse.jetty.util.component
Graceful
shutdown(ThrowingRunnable)
thread.interrupt();
org.eclipse.jetty.util.thread
QueuedThreadPool
doStop()
thread.interrupt();
interruptThread(long)
thread.interrupt();
ReservedThreadExecutor
doStop()
.forEach(Thread::interrupt);
What are you trying to do? or are concerned about?
Know that there's no expectation that 1 request/response exchange is handled by 1 thread in Jetty.
It can be 1..n threads over its lifetime (depends on the technology used during that request/response exchange)
Gets even more complex with your choice of protocols in use too. (websocket vs http/1.1)
