This is a similar question.
How to find out who kills my threads
You can run it while the pool is running . If the pool that supports the thread reboots, it waits until all the threads exit, but the web service to start the pages stops working at the moment, and you have problems. Also, if you configured your pool, then overwrite the pool, if the thread does not stop after a while, it kills it.
In my program, one index thread worked for more than 26 hours, doing hard work with the database, and was included in a static function.
source
share