Comment 9 for bug 322887

There is apparently a Zope3 component called DeadlockDebugger which claims to add a hook so that a deadlocked process can be debugged. The component is available from the Zope svn repository:

  svn co svn://svn.zope.org/repos/main/z3c.deadlockdebugger/trunk

After having enabled the module and starting the appserver, it indeed seems to live up to its claim. However, once the appserver is locked, the page no longer responds. This makes sense because the pool of threads is probably locked which prevents another thread from being acquired from the pool for debugging purposes.