[Zope] ftp server deadlocking zope with DeadlockDebugger

Dieter Maurer dieter at handshake.de
Fri May 5 16:25:17 EDT 2006


Michael Kaplan wrote at 2006-5-5 16:09 +0200:
> ...
>  File "/home/www/Zope-2.8.5-0/Products/Archetypes/ReferenceEngine.py", line 583, in getReferences
>    return self._resolveBrains(brains)
>  File "/home/www/Zope-2.8.5-0/Products/Archetypes/ReferenceEngine.py", line 716, in _uidFor
>    return uuid, obj
>  File "/home/www/Zope-2.8.5-0/Products/Archetypes/ReferenceEngine.py", line 634, in isReferenceable
>    return (IReferenceable.isImplementedBy(object) or
>  File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/_InterfaceClass.py", line 111, in isImplementedBy
>    return visitImplements(
>  File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/Implements.py", line 86, in visitImplements
>    return r
>  File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/Implements.py", line 86, in visitImplements
>    return r
>  File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/Implements.py", line 86, in visitImplements
>    return r
>  File "/usr/local/mypackages/Zope-2.8.5-final/lib/python/Interface/Implements.py", line 81, in visitImplements
>    elif implements_class == TupleType or type(implements) is TupleType:
>
>Could anybody explain what's wrong here and how to repair it?

Stays the part above (maybe partially) accross several
"DeadlockDebugger" invocations (or changes the tail of your
traceback continously)?

In this case, there would seem to be some infinite loop caused
by the AT "ReferenceEngine" (I like it).

-- 
Dieter


More information about the Zope mailing list