Thread hangs up on SocketRead0 about ganymed-ssh-2

[GoogleCodeExporter]

we also need this fixed...

Original comment by [email protected] on 24 May 2012 at 1:46

[GoogleCodeExporter]

I am also seeing the same issue. Any plan to fix this?

Original comment by [email protected] on 29 Jun 2012 at 10:44

[GoogleCodeExporter]

I also encountered this issue. How can I fix this? Will this be fixed? With 
this bug ganymed-ssh-2 is unusable.

Original comment by [email protected] on 12 Jun 2013 at 9:17

[GoogleCodeExporter]

Does anyone know if there has been any progress on this topic?  

I have noticed some similar behavior while using the GanyMed Library.  When 
executing similar tests to those described by the original poster: open 
connection on an unstable IP link, perform SFTP transactions, drop IP link to 
sshd on remote target, and at 
ch.ethz.ssh2.crypto.cipher.CipherInputStream.fill_buffer(CipherInputStream.java:
41)
I will intermittently receive a blocking read.  I can see this in the debugger 
as our software "hangs" and the NETSTAT command shows the connection as 
"ESTABLISHED" until manually terminated.  Ideally an exception or error of some 
sort would be thrown or returned. 

I am unsure if this is the exact same issue that is explained by the original 
poster, but I feel that it is similar enough that opening another issue isn't 
warranted.

Any insight into the status of this ticket is greatly appreciated!

Original comment by [email protected] on 23 Sep 2013 at 7:29

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This has been fixed long ago in r10.

Original comment by [email protected] on 9 Apr 2014 at 7:44

• Changed state: Fixed

[GoogleCodeExporter]

Hi.

dkocher:
I agree that r10 fixed the issue, but as far as I see this bug was 
re-introduced in r47 by the following code in TransportManager.java:

private static Socket establishConnection(...) {
Socket s = new Socket(); // (1) Creating new socket here, and thus earlier 
.setSoTimeout will not have effect.
// missing setSoTimeout here.
s.connect(new InetSocketAddress(addr, port), connectTimeout);
return s;
...
}

public void setSoTimeout(int timeout) throws IOException
    {
        sock.setSoTimeout(timeout);
    }
but sock.connect() is never called. Instead a new Socket is created in (1).

https://code.google.com/p/ganymed-ssh-2/source/diff?spec=svn47&r=47&format=side&
path=/trunk/src/main/java/ch/ethz/ssh2/transport/TransportManager.java

It would be great to see this issue re-opened and fixed.

Thanks
Regards

Original comment by [email protected] on 10 Apr 2014 at 7:00

[GoogleCodeExporter]

Original comment by [email protected] on 10 Apr 2014 at 12:02

• Changed state: Accepted

[GoogleCodeExporter]

In r102.

Original comment by [email protected] on 10 Apr 2014 at 1:42

• Changed state: Fixed