On 10/25/2009 03:16 PM, Adam GROSZER wrote:
> Hello,
> I have the bad feeling (still need to investigate further) that when
> running zope3 with WSGI and paster the shutdown is not a proper
> shutdown but a real hard kill/terminate process. On win32 and *nix
> too. I remember vaguely that with zserver it wasn't like this.

Right, there's some more or less delicate dance going on.

> That means e.g. the FileStorage index is not written -- that means it
> has to be redone on each startup, what costs time.

Checking that is easy: stop the process and look whether the index file
was written or not.

> Or transactions killed in the middle of doing something.

I think ZServer didn't do anything special about that. If you happen to
have a request running it probably just ended anyway ... but I'm just

> Anyone out there noticed the same? Even better question: how to nicely
> stop a WSGI/paster Z3 server (without ZMI ServerControl)

Signal handling (on Unix) comes to mind.


Christian Theune · c...@gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
Zope and Plone consulting and development

Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to