[Zope] ZServer lockups

[Brian Hooper]

Just to add to my last message -

I tried running z2.py with a single thread (-t 1), however I was still
able to produce a similar lockup.  (I guess this makes sense, since
we're talking about something with reading documents, not concurrent
writes, probably this doesn't involve anything with transactions or the
ZODB?  I'm just inferring this here, it seems to make sense...!)

--Brian

Brian Hooper <brian@garage.co.jp> wrote:

> Hi there -
> 
> I've reproduced the same problem here on my setup, also on Win NT.
> Here's what I did, and what happened:
> 
> 1. I set up a Zope installation (Zope 2.0.0b4 w/ patches from the
> latest CVS), with an index_html
> 2. I used Socrates (postcard-shareware testing program) to pound Zope
> with a pretty reasonably low request rate.
> 3. I tried accessing index_html through Netscape while Socrates was
> still testing index_html.
> 4. Both Netscape and Socrates got no response; the Zope machine had a
> pop-up dialog on it saying that 'An application error occurred,
> Exception: Access violation (0xc0000005), Address 0x00f7a88f)' with
> python.exe (I ran z2.py from the command line with -D, hoping to get
> a traceback or something)... effectively it looks like the procedure
> above can kill Zope/ZServer on Win32.
> 
> One thing that I noticed was it seemed like it was fine if I accessed
> pages other than the one that was being checked by Socrates - I was able
> to click around the management screens a bit before having it lock up -
> when I clicked on the top level folder in the management screen
> (<pure speculation>probably requiring an access of the same object or
> objects which were also being accessed by another thread???</pure
> speculation>) that was when I got no response.
> 
> Have you found any more clues about this?
> 
> --Brian
> 
> Robin Becker <robin@jessikat.demon.co.uk> wrote:
> 
> > In article <613145F79272D211914B0020AFF64019262879@gandalf.digicool.com>
> > , Paul Everitt <Paul@digicool.com> writes
> > >
> > >
> > >And one other debugging thing to look for: when it's hung, check to see
> > >if the process is consuming much CPU.
> > >
> > ...
> > ok I don't know what's causing my lockups. I have the 1.9 HTTPResponse
> > etc and I can reliably after around 2000 hits from my torture tester get
> > the win32 ZServer to lock as far as HTTP is concerned. I can use the
> > monitor to see that things are alive in the medusa loop.
> > 
> > My cpu hog thread is responsive (the job queue is empty) and I'm able to
> > add a job and have the server thread go. And the system monitor reports
> > no serious work going on unless I start it. I am unable to get in via
> > netscape.
> > 
> > The interesting thing is that the torture script is also hung so it may
> > be a strangeness related to win9x ie too many requests hanging on the
> > port or somesuch. Killing the torturer doesn't help though.
> > 
> > I suspect that HTTP publication is locked somehow. When it happens again
> > is there anything I can look at to test various/threads etc?
> > -- 
> > Robin Becker
> > 
> > _______________________________________________
> > Zope maillist  -  Zope@zope.org
> > http://www.zope.org/mailman/listinfo/zope
> > 
> > (To receive general Zope announcements, see:
> > http://www.zope.org/mailman/listinfo/zope-announce
> > 
> > For developer-specific issues, zope-dev@zope.org -
> > http://www.zope.org/mailman/listinfo/zope-dev )
> > 
>