File Watcher - Error Handling (Magic xpi 4.14)
The Magic xpi Server Flow Manager checks for errors during the execution of a step. If there is an error in a File Watcher component step, the Error Handler is invoked and handles the error.
The first error in the step causes the termination of the step execution. If the step has multiple methods, and an error occurs in one of these methods, all subsequent methods are not executed.
For File Watcher triggers: The File Watcher connects to the FTP server to Get the directory listing. If the connection is successful, it processes each file in the list one after the other. If there is a connection error (Socket Exception) while Getting the Directory Listing, the Reconnection Policy is applied:
-
If the reconnection is successful, then a message is shown in the Monitor and the process is continued.
-
If the reconnection fails, then a message is shown in the Monitor and the File Watcher trigger is delayed for the Polling Interval (as specified in the configuration) and continues for the next processing cycle.
The error codes for the File Watcher component are listed below. You can also use Magic xpi's General Component Errors with the File Watcher component. The codes are returned to the Magic xpi Server in the Invocation program’s Error Code parameter.
|
|
|
|
8888
|
.Net Exception
|
|
250
|
Java Exception
|
|
251
|
FTP server errors
|
|
252
|
Data validity errors
Error code 252 in the File Watcher indicates a permission problem. This means you need to check if Magic xpi can delete, write, or rename files in the relevant locations.
This error also appears when there is a file that is locked by another system while Magic xpi tries to process it.
|
|
253
|
FTP(SSL) connection has failed
|
|
254
|
Failed to load Server Certification
|
|
255
|
Failed to load Client Certification
|
|
256
|
Failed to load Client Password
|
|
257
|
FTP connection has failed
|
|
1601
|
Step invocation error
|
|
1602
|
ACM: No available AC found
|
|
1603
|
AC: Step incorrectly configured
|
|
1604
|
Input/output error
|
|
1605
|
Communication: Data Transfer error
|
|
1606
|
.NET Launcher: failed to call .NET connector
|
|
1607
|
.NET launcher: More than one IStep.NET-assembly found
|
|
1608
|
.NET launcher: No IStep.NET-assembly found
|
|
1609
|
Communication: Message processing error
|
|
1610
|
RemoteStepinvoker: Invocation timeout error
|
|
1611
|
.NET launcher: Java-.NET interop failure
|
|
1612
|
AC: Unknown connector name
|
|
1613
|
AC: Unsupported runtime technology
|
|
1614
|
AC: Metadata file for the connector not found
|
|
1615
|
AC: Wrong data in metadata.xml file
|
|
1621
|
Trigger Load Timeout
|
|
1622
|
ACM: No available AC found for the trigger
|
Error Handling in Magic xpi
