How To Keep The Job From Aborting Because Of Too Many Errors

The job is aborting because of too many errors. How can I get as much as I can, without regard to errors?

Generally if there are too many errors, you will want to stop the job and see if there is a connection issue.  However, if it is just a lot of old messages with issues and you just want to archive as many as you can, especially if it's the first run against your message source, you can change the attachment.properties file to accommodate that.

File location:
Linux: /opt/beginfinite/retain/RetainWorker/WEB-INF/classes/config Windows: C:\Program Files\Beginfinite\Retain\RetainWorker\WEB-INF\classes\config

Stop tomcat
For each worker installed:

1. Open attachment.properties in a text editor
2. Find the line: max.errors.total= (default is 10)
3. Change the number to -1
4. Save the file

Restart tomcat and you can run the job which will continue even if errors are thrown.

Note: This will not automatically advance the timestamp (Retention/SmartPurge/Internal) on a mailbox. The next job will start at the first error if you're using the Duplicate Check option in your profile.

If using GroupWise see also: How to Configure Error Handling in the ERRORS.PROPERTIES File

This article was originally published in the GWAVA knowledgebase as article ID 2753.