[Zope] ZServer Must Be Continually Re-Started: my Method to stop zope dead:

Chris McDonough chrism@digicool.com
Fri, 11 May 2001 08:04:52 -0400


Chris Withers wrote:
> 
> Gilles Lavaux wrote:
> >
> > I am personally thinking that ONE of the problem is that there is no
> >   time-out on the Zserver socket, I think that if for some reason a request
> >   get stuck, the thread is never released. If you use all the thread pool,
> >   your server doesn't reply anymore.
> 
> I'd second that...

There evidently already is a timeout (according to Jim).  I think it's
set to 30 minutes.  I'm not sure where it is.  It's possible it needs to
be lowered.

> ChrisM: I cc'ed you on this because I have a hunch that it's something along
> these lines that's causing the hangs I mentioned on zope-dev.
> That said, would the python process usage drop down to nothing in the above
> scenario?

No... at least I don't think so...  if you have a long-running method,
and some joker reloads that method 5 times (because they think it'll
speed things up), it will chew up five threads, and whatever processing
is happening will be happening five times.  It's likely that the Python
process would be working hard in this scenario... unless of course the
method was long-running because it was IO-bound instead of CPU-bound...
did requestprofiler turn anything up for you?