-
Notifications
You must be signed in to change notification settings - Fork 599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"The handle is invalid." error when opening the 128th RemoteFile when using WinSSHD #119
Comments
@vpartington I assume you mean that it doesn't happen if you move the opening outside of the loop, it is now in the loop. |
@vpartington Does this also happen with other SSH daemons? (OpenSSH?) |
@hierynomus: This only occurs with WinSSHD and the problem does indeed disappear when I move the opening of the file to outside of the loop But I can't do the generically because the mode (read/write/append, etc.) is also set when opening a file. And you'd think that closing the file ( |
It seems like a bug in WinSSHD if this only occurs with that SSH server. The error message / stacktrace also seems to indicate this comes from the other side of the connection? |
True, but the error could also be caused by some resource not being closed properly by the client, i.e. SSHJ or the code invoking SSHJ. I'd like to rule out those two possibilities first. |
This is now fixed in master with #150. |
While running the integration tests for Overthere, which uses SSH/J for its SSH connections, the following exception is thrown when the 128th
RemoteFile
is opened for reading or writing when connecting to WinSSH version 5 or version 6:I've been able to reproduce the error using this standalone program:
I'm trying to figure out whether this is due to:
I've noticed that the problem does not appear when I move the opening of the
RemoteFile
into the loop so that would hint at a resource leak in theRemoteFile.close()
method.I hope I've provided enough informaton. If not, please let me know!
Regards, Vincent Partington.
The text was updated successfully, but these errors were encountered: