3 Sep
2004
3 Sep
'04
8:49 a.m.
Paul Winkler wrote:
But, I haven't been able to reproduce this behavior today with Zope 2.7.2, even with socket.setdefaulttimeout(None). I've currently got 16 pending requests for the never-finishing external method, and I can still browse zope just fine.
...but this doesn't. Have you upped the number to work threads to > 16?
Nope. This was a 2.7.2 server with the default 4 threads.
Hmmm, then I'd hypothesise that only 4 of those threads were connected to Zope, with the other other 12 waiting to connect to Zope. Do you have any evidence which could back this up, or prove it wrong? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk