Error Policies

The LoaderManager uses a configurable error handling policy, defined by the Repository Loader’s ErrorPolicy component. Each job processed by the LoaderManager might contain files that cause exceptions to be thrown. The LoaderManager consults the ErrorPolicy component to determine how to handle exceptions. All exceptions are logged. The Repository Loader sets a success state for each job and each batch. In addition, the following ErrorPolicy methods are used to determine how to proceed after encountering a problem while processing a job:

checkIsExceptionFatal

Returns true if the provided exception should terminate processing of a job. If false, then we proceed to the checkRequiresNewTransaction method.

checkRequiresNewTransaction

Returns true if the provided exception requires a new transaction in order to reasonably continue.

checkEndTransactionWithBatchState

Returns true if transaction demarcations should be ended using the value of the Job’s batchFailed property. In this case, if a batch has failed, then all subsequent batches in the job will be rolled back, whether or not they contained any errors.

 
loading table of contents...