First of all, thanks for all the replies I received in the last days! * 2007-07-02 21:39, Jim Fulton wrote: > >See also http://www.upfrontsystems.co.za/Members/jean/zope-notes/ > >debug-spinning-zope and http://svn.python.org/view/python/trunk/ > >Misc/gdbinit?view=markup. > > Another option, if you are using zserver, is to (carefully) use the > Medusa monitor server and client. This lets you telnet to the server > and get a limited Python prompt that lets you poke around at the > Python level. Of course, this is a potential security hole if not > done carefully. I used to find it very useful for looking at hung > Zope 2 applications before it was disabled in Zope 3 for security > reasons.
I tried the suggestions from Benji, but using gdb and the commands from "debug-spining-zope" results in a segfault of the zope3 instance I'm debugging. The threads in the sleeping zope3 instance are in either select, poll, or semaphore waiting (2 or 3 of them) but I can't get more information about it. I'm thinking about switching to zserver, but considering that my deployment is in production and I can't have long down-times, I'd like to know if zserver is a good choice for high loads or if it deprecated and I should stay with twisted. Was zserver disabled only for security reasons? What's your opinion about it? Thanks, -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _____________________________________________________________________ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com