Hi, Dmitry,
There isn't the best way for all scenarios, IMO. For example, if the
exception is critical and the application can not afford to ignore the
failure, throw the exception uncaught is proper, which would fail the
container and allows the application to restart from the previous
Suppose my task's process method fails for some reason. Say the problem is
not in the message but is attributable to some external condition: a
service is down, a network partition.
What is the best way to handle such failures? Currently I am just what
seems natural and writing the failures to a
