Oliver, I'm a bit confused. What version of things are you running? I remember that this thread changed quickly to specify Solaris with the problem. I tested this problem on my linux box (note, dual processor) without any problems at all.... Mind you of course it slowed the response down a bit, but it was stable... And what is the significance of 2 methods and 'not 4'? Paul Zwarts -----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org] On Behalf Of Oliver Bleutgen Sent: Tuesday, October 30, 2001 5:13 PM To: zope@zope.org Subject: Re: [Zope] Re: Threading, dtml and performance?! Thomas B. Passin wrote:
[Paul Zwarts]
AFAIK, such a beast does not exist where you can stop a transaction from pressing a browsers stop button. Web is stateless, so a stop button on a browser cannot be connected to the servers understanding of finish the request or don't.
Yes and no. When you stop the browser, the socket connection closes. The next time the server tries to use that socket it gets an exception. Ideally in handling the exception the server should stop the thread in question, but who is to say that really happens?
As I wrote before, it happens in mod_perl, it doesn't happen in zope2.3.3 on linux 2.2.13. And I would still be interested in an explanation why two long running methods (not four) seem to be able to stall zopes http server on linux. cheers, oliver _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )