EldoS | Feel safer!

Software components for data protection, secure storage and transfer

simulation of "Connection Lost" error

Posted: 05/27/2010 12:38:34
by Dmitry K (Basic support level)
Joined: 09/03/2009
Posts: 5


there were plenty of talks here on what to do with "Connection Lost" error as well there is a long FAQ on why this may happen.

I have a slightly different case here - there is no problem connecting to sFTP server in 999 cases out of 1000 but sometimes we do get this Connection Lost error.

We are trying to find a way around this issue, but to do so, we need to be able to generate error in dev/prod env more consistently - any attempts to interrupt network services result only in "Connection Failure" message but not "Connection Lost".

currently, we doing retry of Open() command with a delay between retries, however, after initial exception: "SBSimpleSftp.EElSimpleSFTPClientError: Connection lost (error code is 10054)", on retry this generates a different error: "SBSocket.EElSocketError: Wrong socket state 4 in Init (error code is 96258)"

so here is the question:
1) are there any ways for use to Simulate "Connection Lost" error?

2) why errors are different on retry?
we are doing:
sftpClient initialization
sftpClient Open()
if no error then
exit loop and continue with operations
try closing connection if active
retry Open()
end if
end loop
Posted: 05/27/2010 13:16:10
by Eugene Mayevski (Team)

If you have a license, please assign the license ticket to your user account before we continue. The ticket itself and the procedure of it's use are specified in the registration e-mail that was sent to you upon license purchase.

Sincerely yours
Eugene Mayevski



Topic viewed 2185 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!