...
To avoid an input/output operation getting hung for an indefinite time waiting for a request to return due to reasons like network fluctuations of the mounted directory, it is recommended to configure Connection Timeout in the runtime arguments. To configure Connection Timeout, add the following value in This is done by adding a property "-DCONNECTIO_TIMEOUT" with the value (in milliseconds) as per requirement in Runtime Arguments in the Properties pane, which represents the maximum time that component waits for execution of each file.
To configure Connection Timeout,
- Click the FTPGet microservice present on the orchestrator editor.
In the Properties pane, click the Runtime Arguments tab and append the following values in the JVM_PARAMS text area:
Code Block title Append to the JVM_PARAMS values language actionscript3 -DCONNECTION_TIMEOUT=3000
...
Figure 12: Configuring the runtime arguments by editing the JVM_PARAMS value to manage memory- Press Enter to save the configuration and click the option "No" or "Yes" to update this configuration only to the current service instance alone or for all event process respectively.
| Info |
|---|
After configuring Connection Timeout as above, the maximum time that the component waits for execution of each file will be 3000 milliseconds (3 seconds). If a CONNECTION_ERROR is thrown while the request is expecting to read N number of files, then the execution of all the remaining files for that request will be discarded. Once the CONNECTION_ERROR has occurred, the next request from the input port is processed |
...
in sequential order. |
...
| Note |
|---|
The default value, in case the -DCONNECTION_TIMEOUT is not configured in runtime arguments, is 180000 milliseconds (3 minutes). |
Input and Output
Input
When FileReader is not in scheduling mode, messages can be sent onto the input port of the component specifying the file to be read and the location of the file. The schema of the input XML message is shown in Figure 10.
...