Hi! 16.09.2015 19:37, Karl Lehenbauer пишет:
I want to affirm your comments from the 11th that there needs to be a way to to terminate the child process or thread if code detects that things have gotten wonky. We do this, for instance, on failure to obtain a database connection during page processing startup and on any uncaught traceback within the guts of our top level traceback-handling code.
And we don't do exit in above situations. Application reports HTTP 500 result code with standard message like "error processing request".
At some request later database is reconnected. It doesn't require worker to restart.
Uncaught error in this one request may not repeat with next request. The worker doesn't exit.
There are situations where worker exit doesn't help to recover from detected problem. Say request to external service returns unexpected result repeatedly.
But maybe to terminate worker is simpler and/or safer .. -- Best regards, Anton. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
