Managed File Transfer Internet Server version 8.4.x introduced an issue where downloads from some SSH servers can be affected by slow and/or failed transfers
Article ID: KB0071913
Updated On:
| Products | Versions |
|---|---|
| TIBCO Managed File Transfer Internet Server | 8.4.x |
Description
Managed File Transfer Internet Server version 8.4.x introduced an issue where transfers to some SSH servers can be affected by slow and/or failed transfers. The issue is for downloads and does not affect uploads. The root cause of the problem has been identified and was introduced with the updated SSH maverick-legacy jar files in MFT v8.4.x.
Transfers may fail with different exceptions including any of the following:
"Exception: Failed to close proxy"
"Exception: Connection has been dropped as it reached the max idle time of xxx seconds."
"Error happened from back-end. Proxy: Transfer failed"
"Exception: Server responded with an unknown failure: There are insufficient resources to complete the request"
"Exception:Null."
Exception: Corrupt Mac on input."
Transfers may fail with different exceptions including any of the following:
"Exception: Failed to close proxy"
"Exception: Connection has been dropped as it reached the max idle time of xxx seconds."
"Error happened from back-end. Proxy: Transfer failed"
"Exception: Server responded with an unknown failure: There are insufficient resources to complete the request"
"Exception:Null."
Exception: Corrupt Mac on input."
Issue/Introduction
Managed File Transfer Internet Server version 8.4.x introduced an issue where downloads from some SSH servers can be affected by slow and/or failed transfers
Environment
All supported environments
Resolution
The issue can be resolved by replacing the maverick-legacy jar files in MFT IS v8.4.x with the maverick-legacy jar files from MFT IS v8.3.x. The MFT IS v8.3.x maverick-legacy jar files are attached to this article. Use the following procedure to resolve the issue:
1) Create a backup folder "<MFT install>/backup-lib-maverick" on the server where MFT IS is installed.
Note, the backup folder can be any name, but must not be under the "<MFT install>/server" folder.
2) Move the following 3 maverick-legacy jar files from the "<MFT install>/server/webapps/cfcc/WEB-INF/lib/" folder to the "<MFT install>/backup-lib-maverick" folder:
maverick-legacy-client-1.7.39-no-common.jar
maverick-legacy-common-1.4.12.jar
maverick-legacy-server-1.7.39-no-common.jar
Note, these files must be moved out of the "<MFT install>/server/webapps/cfcc/WEB-INF/lib/" folder.
3) Download the maverick-legacy.zip attached to this article. Unzip maverick-legacy.zip and copy the following 3 maverick-legacy jar files to the "<MFT install>/server/webapps/cfcc/WEB-INF/lib/" folder on the server
maverick-legacy-server-1.7.35-no-common.jar
maverick-legacy-common-1.4.8.jar
maverick-legacy-client-1.7.35-no-common.jar
4) Restart the MFT Internet Server
1) Create a backup folder "<MFT install>/backup-lib-maverick" on the server where MFT IS is installed.
Note, the backup folder can be any name, but must not be under the "<MFT install>/server" folder.
2) Move the following 3 maverick-legacy jar files from the "<MFT install>/server/webapps/cfcc/WEB-INF/lib/" folder to the "<MFT install>/backup-lib-maverick" folder:
maverick-legacy-client-1.7.39-no-common.jar
maverick-legacy-common-1.4.12.jar
maverick-legacy-server-1.7.39-no-common.jar
Note, these files must be moved out of the "<MFT install>/server/webapps/cfcc/WEB-INF/lib/" folder.
3) Download the maverick-legacy.zip attached to this article. Unzip maverick-legacy.zip and copy the following 3 maverick-legacy jar files to the "<MFT install>/server/webapps/cfcc/WEB-INF/lib/" folder on the server
maverick-legacy-server-1.7.35-no-common.jar
maverick-legacy-common-1.4.8.jar
maverick-legacy-client-1.7.35-no-common.jar
4) Restart the MFT Internet Server
Attachments
Feedback
Yes
No
Powered by
