You are not logged in Log in Join
You are here: Home » Members » Nuxeo on » Products » Debugging a running or deadlocked Zope » DeadlockDebugger 1.0 » README.txt » View Document

Log in





*$Id: README.txt,v 1.1 2005/02/23 15:35:21 fguillaume Exp $*

This product adds a hook so that a deadlocked Zope process can be
debugged, by dumping a traceback of all running python processes. The
dump is sent to the event log (at the DEBUG level) and returned to the
browser (even though the Zope is deadlocked and doesn't answer any
other requests!).

DeadlockDebugger can of course also be used in non-deadlock situations,
when a Zope process is taking a long time and you wish to know what code
is being executed.


This product requires the 'threadframe' python module
When DeadlockDebugger starts, it verifies that threadframe is available,
please check the event.log for ERROR message.


You must edit the file for your needs. You have to change
ACTIVATED to True, and change SECRET. You may change the URL that's
intercepted by the hook to do the dump.


The standard way to call it is to go to the URL::


This will return a dump, and also send this dump to the event log.

A secret is needed because Zope doesn't do any access control on the URL
(it is intercepted too early), and the thread traceback dump may return
sensitive information about the requests being executed. If you know
your Zope will only be accessed by authorized persons anyway, you can
set SECRET to the empty string, and just call::


In any case you should filter out 'manage_debug_threads' in your
front-end proxy.


This product is sponsored by Nuxeo

Please contact Florent Guillaume ( for problems.
You can use the mailing-list to discuss this product.