Hi there
My app uses both SftpClient and SshClient on threadpool threads, to interact with a remote server (specifically OpenSSH running on Amazon AWS EC2 servers running Windows).
Because these AWS servers go down more than I'd like, I've had to build in retry-logic into my code. This retry logic looks for certain exceptions from SftpClient and SshClient, and if one occurs, waits for a timeout period, and tries again.
The problem I'm running into is that once one of these servers terminates (and thus there is no remote SSH server that can be connected to), occasionally both the SftpClient.Connect and the SshClient.Connect calls will hang (never return).
Sometimes they don't hang, though, they do the expected thing which is to throw an exception.
I can't figure out why sometimes they hang and never return.
Any insights, or suggestions for how to debug this, would be greatly appreciated
Michael
Comments: No response, assume it is fixed
My app uses both SftpClient and SshClient on threadpool threads, to interact with a remote server (specifically OpenSSH running on Amazon AWS EC2 servers running Windows).
Because these AWS servers go down more than I'd like, I've had to build in retry-logic into my code. This retry logic looks for certain exceptions from SftpClient and SshClient, and if one occurs, waits for a timeout period, and tries again.
The problem I'm running into is that once one of these servers terminates (and thus there is no remote SSH server that can be connected to), occasionally both the SftpClient.Connect and the SshClient.Connect calls will hang (never return).
Sometimes they don't hang, though, they do the expected thing which is to throw an exception.
I can't figure out why sometimes they hang and never return.
Any insights, or suggestions for how to debug this, would be greatly appreciated
Michael
Comments: No response, assume it is fixed