I have a requirement to send a 10 GB file to a client SFTP server through an automated process. We are using BMC Control-M to automate the whole process.
However, the client SFTP Server disconnects the session after 300 seconds due to inactivity. And since the file size is quite big, file transfer fails due to SFTP Server disconnect.
During testing, I was sending the file manually, through WinSCP. In WinSCP, we have an option called Keepalives, that will keep a FTP connection alive.
Is there any similar option we can set in Control-M AFT settings?
This can be changed by right clicking on the "Control-M for Advanced File Transfer" (or "Control-M for Managed File Transfer", depending on which version you have) in Control-M Configuration Manager (CCM).
From there, open "Configuration Management" then update "Connection timeout (seconds)" to your required value.
Related
I have a simple Flow that write on SFTP folder. When it finish to write it keep on connection.
Is possible to close the connection with the SFTP server when the file has been written?
Thanks.
Our BizTalk 2016 environment consists of 2 application server running in a group with CU5 and FP3.
We have 24 applications deployed. Across this applications we have 27 receive locations with the new sFTP WinSCP adapter configured. For all sFTP receive applications we have the "Connection Limit" configured to 5. We have 6 different sFTP Server we are connecting to.
After approximate 2 hours, we have the following event log warnings and the receive locations stop working:
"The adapter "SFTP" raised an error message. Details "The WCF service
host at address "sftp://..." has faulted and as a result no more
messages can be received on the corresponding receive location. To fix
the issue, BizTalk Server will automatically attempt to restart the
service host."
Against the event log message the service host is not restarting automatically.
Has someone any idea how to fix this issue?
Try out CU7 as it includes a couple of SFTP fixes.
The latest version of BizTalk Health Monitor comes up with the following Important Warning
The host instances of 'hostinstancename' need more worker threads per cpu to run correctly SFTP Receive Locations. Increase so the "Maximum Worker Threads" property to 500 for these host instances and be sure they are dedicated for this SFTP Receive Locations
So things to look at are
Have a dedicated host for receive locations using SFTP
Increase the Maximum Worker threads setting to 500
Check how frequently you poll (the default is 5 seconds)
Put a schedule on to only poll during the periods you need.
Disable message body tracking if it is not needed.
My Mirth Connect v3.4 channel's File Reader source connector is configured as the SFTP reader to poll files from a remote server every 20 minutes and it works as expected.
But when the channel goes idle it starts sending keepalive#jcraft.com messages to the remote server every 10 seconds regardless of the Timeout setting of that source connector.
Is there anything else to configure to stop these messages from being sent to keep connection alive or is there any workarounds other than restarting the channel after each poll by some other channel?
From the JSch changelog:
change: at TCP socket reading timeout, keep-alive message will be sent
to the remote sshd. To disable this functionality, invoke
explicitly Session.setServerAliveCountMax(0)
Unfortunately JSch does not provide any way to set this value from its own configuration file. So you'll have to use JavaScript and create a Session manually.
I'm using the ssh.net library to communicate with another server as part of a ASP.NET application.
I noticed using TCPView there is ever only one connection via SSH to the outgoing server at a time, the IIS server doesn't open one SSH connection per web request like I would expect. This is causing huge performance issues as only one request can be handled at a time - and must complete before a new one starts. Meanwhile, the other requests wait.
How can I allow the ssh.net library or the IIS server to open as many connections as required?
I use cyberduck for SFTP my website files to the server. Dreamhost is the server.
In setting up a new bookmark in cyberduck I received this error "Connection failed - EOF while reading packet." [end of file]
The website is up and working fine, http://ce-t.org
Initially I thought this error had to do with the connection opening with cyberduck. So I setup a different bookmark to test and was able to do without a problem.
I have also deleted my first attempt to setup and reset up. This did not alter anything.
Now after doing more reading, may be in one of the website files?
As you can see i am a novice.
Help appreciated.
Usually when I run into this issue, its because my pw has expired.
Try SSHing into the server and change/update your pw. After I change it, I can FTP in.
This is 3 years too late for the OP. But I had this error when trying to make an SFTP connection to hosting on a Plesk server and the solution was to:
Enable the 'Access to the server over SSH' setting for the ftp user via the Plesk Control panel.
Of course you might need to contact your hosting service to get this done if you are not managing your own server.
In my case the same error occurred due to a syntax error in the .bashrc file on the remote server.
Also note that the default account setting for an FTP user at Dreamhost might specify an FTP connection. If so, trying to use Cyberduck to connect via SFTP will generate this error message. You can use the Dreamhost control panel to edit the user's record to specify SFTP.
In my case I have used dropbear ssh server.
I replace this server with openssh server, and now i can open the sftp connection without any issues.