Stefan Winter wrote:
I finally also found those on a 2.2.1 which runs a simple, proxy-mostly config. I would rather have expected such things on our complex internal instance, but well. Looks like:
Mon Sep 30 09:05:08 2013 : Error: WARNING: Unresponsive child for request 64232, in component <core> module <thread>
If you could narrow this down, it would be appreciated. Even a simple test case... The blockage seems to the input queue. i.e. requests are put into a queue for worker threads to pick up. If the worker threads never look at the queue, the requests get blocked. The code in threads.c did have some changes, but they shouldn't have affected this. Maybe you could try running 2.2.1 with version 8014870 of that file. If it doesn't have this problem, then there are only two commits to debug. Alan DeKok.