Job log from IG_FTP shows Caught an exception, leaving main loop due to Socket closed
Article ID: 382603
Updated On:
Products
Issue/Introduction
After upgrading the Integration FTP agent (IG_FTP) from 21.1.0 to 21.2.0 you observe a peculiar message (Caught an exception, leaving main loop due to Socket closed) at the end of a succesful transfer in the report of the FTP Job randomly:
Agent 21.1.0:
SFTPHelperDelegate: disconnect channel.
Agent 21.2.0:
SFTPHelperDelegate: disconnect channel.
Disconnecting from sftp_hostname port
Caught an exception, leaving main loop due to Socket closed
No impact is observed in the FTP Jobs, they all work fine, same as before.
This error cannot replicated and occurs randomly, seems somehow related to the disconnection from the target SFTP server.
Environment
Agent Integration FTP 21.2.0 and superior and Agent Integration FTP 24.1.0 and superior.
Cause
Not a problem: this is an INFORMATION level message from the jsch fork third-party that we use in the Integration FTP Agent.
Resolution
On the latest versions of the Integration FTP Agent we upgraded the jsch fork to the latest available version to include some vulnerability fixes on the third-party included and the solution, along with bug fixes and enhancements, this is most likely the reason why the messages are only visible now in the reports.
For now, please ignore the message as it's just informative and there's no impact in the execution of the FTP Jobs.
Additional Information
Broadcom does not modify the source code of the third-party solutions such as jsch, so the level of this message or a fix to avoid it cannot be provided by Broadcom but only by the developper that maintains the jsch library.
You can follow the following issue at jsch with the explanation from the developpers of the third-party library and request a fix / procedure to avoid the message if needed.
Feedback
