2009/7/10 Mike McGrath <[email protected]>: > > On Fri, Jul 10, 2009 at 5:17 AM, Graham > Dumpleton<[email protected]> wrote: >> >> >> A final thought though, if you are seeing 500 error responses, that >> would indicate that a request is still in the process of being handled >> when this problem occurs. This would mean that process shutdown or >> inactivity-timeout can't really be triggering, unless you actually had >> a single request that blocked for the timeout period and no other >> requests arrived in that time. If this did occur, then would also >> expect to see a 'Premature end of script headers' error message in >> logs and you have said anything about that. >> > > One other thing I thought I'd ask about is how shutdown-timeout > behaves. If a shutdown gets triggered, will apache stop sending > requests to that process immediately or will it wait until after it > actually dies?
It isn't that Apache stops sending the requests, but that the process stops accepting any new ones. Thus, if using such a long shutdown timeout, is wise to run more than one process in the daemon process group so that have chance there is another process in the daemon process group still running that can accept requests while the first in shutting down and restarting. > Also, what happens to a process if it's been told to > shut down, but takes longer then the shutdown-timeout, is there > anything that would show up in the logs? It will be killed off at end of shutdown timeout period. In the logs you will see a message containing 'Aborting process'. Graham > -Mike > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
