Controlling the Exiting and Restarting of a Worker to Minimize the Impact of Publishing Issues
The exiting and restarting of the worker is controlled by the Error Handling settings on the > tab. All adapter errors have a unique error code you can see in the worker log, such as proe2pv Error:56127: Failure to retrieve…. There are three settings that control the worker’s response to specific adapter error codes:
• Fail Current Job On Following Errors
(adapter/failErrorList=<error_list>)
This is a space-separated list of adapter error codes. The Publish Job in which the errors occur is marked with the publishing status of FAILED. The FAILED status occurs even if the error does not normally prevent the publish job from completing, such as a failure to create a simplified representation.
• Batch Exits After Job on the Following Errors
(adapter/batchAbortErrorList=<error_list>)
This is a space-separated list of adapter error codes. This setting is only relevant in the context of a batch mode conversion, such as using the proebatch command line publisher. It configures the adapter to exit after the generation of any error code specified in the space-separated list. For example, if you use the batch command to process multiple objects from the file-system and an error code in the list occurs, the batch processing ends without processing any of the remaining objects. The processing ends even if the error is not normally fatal.
• Worker Exits After Job on the Following Errors
(adapter/abortErrorList=<error_list>)
This is a space-separated list of adapter error codes. When an error from the list occurs, the worker exits and the message The adapter has been configured to restart after the current job when this error occurs appears in the worker log. The adapter sends a message indicating helper restart of the worker, and then reprocesses the same job after successfully restarting.