> Hi uWSGI,
>
> Are --reload-on-exception-{type,value,repr} preferable to
> --reload-on-exception? The list said --reload-on-exception is
> something to use if you want to "go berserk", so that's the impression
> I got, but I think it's the right choice for our app. Our app (using
> Flask) has error handling that ought to be catching just about
> anything so it can serve a custom error response, without raising to
> uWSGI.
>
> So anything that makes it to uWSGI has to be pretty friggin' severe:
> the last time it happened, the thread that raised it turned out to be
> in some kind of permanent error state and wouldn't respond with
> anything but 500 for the rest of its life. That incident's actually
> why we're looking into this option in the first place!
>
> Thoughts?
> Matt PhippsIf i understand correctly your app passes only "extreme" exceptions to uWSGI. So any exception of this kind would mean something bad has happened. if so, --reload-on-exception seems the best approach to me. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
