Error Handling in Simple File Transfer Mode
Error Handling provides a convenient way of analyzing the parsing errors in Simple File Transfer mode.
Publication Service
For every Subscription Service that is marked unavailable, or if an available Subscription Service returns a checksum error for a given file transfer, Publication Service maintains a specific log file (_.txt) for Subscription Service in the error directory specified during configuration. This file contains information that points to the file that Subscription Service had an issue with.
- If the postprocessing option is set to Leave as is or Delete, and Publication Service has detected an issue with Subscription Service, the file is moved to the error directory with the date and timestamp appended to it.
- If the postprocessing option is set to Move to, and Publication Service has detected an issue with Subscription Service, the file is moved to the completion directory. Depending on the option to add date and time, the date and timestamp are appended to the file.
Subscription Service
If an error occurs when processing a file transfer, Subscription Service prints an error log and exits by default. When you set the adfiles.io.sub.exit4issue property to OFF, Subscription Service prints an error log and does not exit.
When IO errors occur in Subscription Service, Subscription Service exits by default. If Publication Service continues to send messages using the Durable EMS transport or the Certified RV transport, Subscription Service resubscribes the remaining messages from the transport when restarted.