Runtime - File Event Issues

Issue

Cause

Diagnosis

Resolution

Mail source activity sometimes aborts with the error:
"Unable to connect host [mailserver]: Server is down or Server/UserId/Password/Port is wrong."

This error occurs when multiple instances of the process flow, which include Mail Source/Target activities, are executed concurrently. The mail server limits the number of concurrent connections, leading to the mail source aborting due to unavailable connections.

Check the logs:
"Unable to connect host [mailserver]: Server is down or Server/UserId/Password/Port is wrong."

This log suggests connection attempts exceed the mail server's allowed concurrent connections when multiple process flows try to connect simultaneously.

1. De-activate the Mail Events.

2. Limit Concurrent Mail Processing:

Change the following properties:
abpm.mailEvent.mailProcessConcurrency = 15
abpm.mailEvent.retry = 1000
abpm.mailEvent.sleepTime = 1000
Adjust these values based on your mail server's capacity. Restart the server after changing these properties.

3. Enable Activity Retry Feature in the process designer:

Double click the mail source activity.
Update the properties:
Activity maximum retries on failure = 50
Activity wait time between retries = 60 sec
Save the process flow. This ensures the mail source activity retries connection attempts without aborting the process flow.

4. Activate the Mail Events.

A process flow triggered by an FTP trigger, exported from a 5.3 server and imported into a 6.2 server, gets triggered and then aborts. The diagnostics show an error related to initializing the FTP source activity.

The FTP connector type used while creating the connection to the FTP server needs to be corrected. In Adeptia Suite 6.2, a new API "Secured Inet Factory" was introduced, which provides better connectivity and enhanced logging.

Check the logs:
Error initializing activity FtpSource:FTPSource_PROD:19216800503000000003[Unable to access file location "test4.txt", Please check either provided file location is invalid or it doesn't have required permission.]
This logs suggests a disconnect between the trigger and the FTP source, likely due to an outdated or incorrect FTP connector.

1. Edit the FTP Source:

Navigate to the FTP source configuration.

2. Update Connector:

Go to Advanced Properties > Connector.
Select "Secured Inet Factory".

3. Save the FTP Source:

Save the changes to apply the new connector settings.

When a large file is sent to an FTP folder, it throws errors each time. After logging Verbose, it seems that the connection closes before the file transfer it complete.

The connector type of the FTP Target may not be compatible with the FTP Server

Check the logs:
SshFxpStatus {id=4, code=4, message='seek 0 not supported with cursor 65536.', languageTag=''}

Try changing the connector type of the FTP Target from "Secured Inet Factory" to "J2SSH" (Advanced Properties).