Turning on detailed logging at startup might help too... read about the -M argument in the z2.py script and read my Howto regarding "How To Track Down Hangs" at http://www.zope.org/Members/mcdonc/HowTos/DEBUG-LOG "Cees de Groot" <cg@cdegroot.com> wrote in message news:92ghr3$jf3$1@gaia.intranet.cdegroot.com...

Dieter Maurer <dieter@handshake.de> said:

...

Cees de Groot writes:

...

... excessive CPU/memory consumption ... If you use Zope 2.2.x, you can try to access the debug tools in the "Control Panel". They will show you, which request is active (to more easily reproduce and analyse the problem) and how the reference counts are changed.

The problem is, apparently the thing gets in a really tight loop - one threads blocks the rest of Zope, so it is quite hard to use these tools (especially not when the whole thing is not - yet - reproducable, sometimes it happens in an hour, sometimes after 12 hours; a bit hard to keep staring at the screen for 12 hours :-)).

As a bit of an act of despair, I'm currently logging Zope's CPU usage every 5 seconds in a log file, hopefully I can match a rise in CPU time with some request in the server logs.

-- Cees de Groot http://www.cdegroot.com <cg@cdegroot.com> GnuPG 1024D/E0989E8B 0016 F679 F38D 5946 4ECD 1986 F303 937F E098 9E8B

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )