No doubt about it. A number of users have reported serious stability problems - me included. Apache/FCGI or direct to medusa seems to make no difference. One way of stopping the problem is to run with -t 1 but frankly, it's not a viable option for many situations - single threading zope is painful under any kind of load, but at least it doesn't appear to core dump regularly. I've experienced it on a 2.1.6 binary install on a linux (stock RH6.1) box but I understand it's been reported on a solaris x86 box also. I have a lightly loaded sunos 5.6 binary install which seems stable. The stability with single threading seems to point to a thread problem and the possibility of a libc bug has been rumored. --- In zope@egroups.com, Marcus Collins <mcollins@s...> wrote:

Apologies for the imposing subject line...

Briefly, since increasing the NUMBER_OF_THREADS that Zope uses from the default (4) to 20, Zope has been hanging randomly. A request will be sent off to Zope (whether through apache with mod_pcgi, or directly through ZServer), but the request is never served up, and Z2.log shows no record of it. No additional CPU is taken by the python process.

Environment: Zope 2.1.3 (source release) python 1.5.2 GCC 2.7.2.3 FreeBSD 3.3-RELEASE

-- Dr Ross Lazarus Associate Professor and Sub-Dean for Information Technology Faculty of Medicine, Room 126A, A27, University of Sydney, Camperdown, NSW 2006, Australia Tel: (+61 2) 93514429 Mobile: +61414872482 Fax: (+61 2) 93516646 Email: rossl@med.usyd.edu.au