Error Handling
This topic only applies to self-managed Intelligent Advisor edition
There are two types of errors that can occur when Intelligent Advisor Java Batch Processor is running: fatal and non-fatal. Java Batch Processor manages these errors differently.
Fatal errors
Fatal errors are unexpected errors that apply to a processor as a whole. For example, if the database the processor is reading from or writing to becomes unexpectedly unavailable. Fatal errors may affect one or more of the parallel processors, but do not necessarily affect all parallel processors.
When a fatal error is encountered, the error details are logged according to the log configuration, and the affected processor stopped. If using multiple parallel processors, any unaffected processors will continue working to ensure that as many cases as possible are processed. The final summary message provided by Java Batch Processor will indicate that an error occurred during processing, and identify the total number of cases that were successfully processed.
Once the cause of the fatal error has been identified and resolved, Java Batch Processor can be run again to reprocess all cases, including those missed previously due to the fatal error.
Non-fatal errors
Non-fatal errors are predictable errors that apply to a single case only. For example, data validation errors (such as trying to read the value 'abc' into a numeric attribute) and errors returned by a specific rule in a policy model.
When a non-fatal error is encountered, the error details are logged according to the log configuration, the affected case ignored, and the processor continues on to the next case. The final summary message provided by Java Batch Processor will identify the total number of cases that were successfully processed and the total number of cases that were ignored due to non-fatal errors.