Our Products:   CompleteFTP  edtFTPnet/Free  edtFTPnet/PRO  edtFTPj/Free  edtFTPj/PRO

SecureFTPConnection.Connect() method hangs and does not throw time out exception

0 votes
50 views
asked Jul 25 in .NET FTP by winkert (120 points)

One of our clients did not include our IP address in their white list for their FTP server (SFTP) so our attempts to deliver daily files to them were rejected for about a month. During this time, many of our attempts to send the file did not throw an exception when we attempted to connect to their server. Some attempts did throw the following exception: EnterpriseDT.Net.Ftp.Ssh.SFTPException: Protocol negotiation timeout

The exception is, of course, the expected behavior and we have a process that handles any exception and marks the delivery attempt as failed. However, when no exception was thrown and the connection process hung, the task was "running" for days until killed.

System Information:

  1. We are using version 9.1.1.20 (edtFTPnetPro dll)
  2. We do not currently enable logging (is there a way to log to a Db or object?)
  3. We are using .NET 4.6
  4. All FTP transactions are called from static routines which create the connection and then call the SecureFTPConnection methods (upload, delete, download, etc).

 

Why wouldn't the Connect() method throw an exception? I know it is failing there because we log our steps to a communication log in the Db which ends when we call Connect() and does not have the next entry (Connection success or connection failed).

Is there anything we can do to catch when this is failing to throw an exception when connecting?

commented Jul 26 by support2 (143,750 points)
Probably best to post a snippet of the debug log file of when this occurs.  Is it possible you have the timeout set to 0?
commented Jul 26 by winkert (120 points)
The only place I can see where we change the TimeOut value for the connection is when we set it to 60s instead of whatever the default value is for a particular client. Am I correct that the default timeout is 120s? I will probably propose changes to set the timeout initially to something reasonable (and probably drop that hard code for a single FTP server).

I'm also going to ask about setting up logging. That might take some time to get approved and set up. Thanks.

Please log in or register to answer this question.

...