Comment 3 for bug 430637

In my test configuration, it seems to be a consequence of the problem described in bug#430641.

A real stress test in addition to the main test flow also sets up several events which are run with different intervals (1-10 minutes).
The test is run with 50 client connections. When it gets stuck at the point described in bug#430641, processes started by client connections lock some data; since the same data is supposed to be used by the events, new events cannot finish and pile up as running processes, Thus, even also the number of connected threads is fixed, the number of running threads keeps increasing and eventually hits the limit.