Which means that after halting and save current process then system switches to the exception handler
and comes back again once an exception handling is done.
If any exception occurred, then the Reasoner will call the Exception Handler
to handle the exception.
For now, we throw ConnectionFailureException and handle it in a bubbled exception handler
in the UI.
When an exception is unexpected, the exception handler
typically resorts to halting the process and invoking a human intervention.
Instead, we must guarantee that all preceding instructions complete successfully before invoking the exception handler
An exception handler
is the code attached to (or associated with) an entity for one or several exceptions and is executed when any of these exceptions occur within the entity.
Jobs are run by an execution Controller software module that interfaces with a graphics monitor and an exception handler
(one of the first implementations of a shop-floor expert system).
Regardless of whether the exception is detected and raised by the hardware or the software, its effect is to abandon the execution of the instruction responsible for the exception, and to continue instead with the execution of an exception handler
, if one has been provided for the specific exception.