Hello,

we are currently dealing with incoming ServletRequests getting stuck in calls to thirdparty libs and filling the FixedThreadPool Grizzly uses. I have already implement a RequestWatcher that keeps track of requests/threads that are currently being handled. This Requestwatcher reports the stuck requests and tries to interrupt them via Thread.interrupt() and sends an error to the client to ensure operation of the server. "Of course" those threads don't react to interrupts and remain in TIMED_WAITING state.

Does Grizzly offer a more general approach to remove those threads from the threadpool? Is it possible to use our own existing implementation of ThreadPool/ExecutorService to achieve this?

 

Best regards,
Marc