mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oliver Stöneberg (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SSHD-635) potential hang in AuthFuture.verify(Long.MAX_VALUE) on error
Date Wed, 29 Jun 2016 12:43:37 GMT

    [ https://issues.apache.org/jira/browse/SSHD-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355155#comment-15355155

Oliver Stöneberg commented on SSHD-635:

I am no longer able to reproduce this issue. As a matter of fact I was able to enable all
of my the unit tests now and they are running without any issues now. I assume this was a
network issue since even when using putty the server was sometimes forcefully close the connection
and that also hasn't happen in a while.
I reckon the hang is still potentially happening when the connection is somehow terminated
by the server or something else in the network. But without any reproducible case I see nothing
we can do now. So feel free to close this issue and thanks for looking into this.

> potential hang in AuthFuture.verify(Long.MAX_VALUE) on error
> ------------------------------------------------------------
>                 Key: SSHD-635
>                 URL: https://issues.apache.org/jira/browse/SSHD-635
>             Project: MINA SSHD
>          Issue Type: Bug
>            Reporter: Oliver Stöneberg
>         Attachments: ssh.log
> It appears that after the SshClient.connect().verify() call was successful the ClientSession.auth().verify()
call might hang if the connection was closed in-between those calls. If AuthFuture.verify()
is called with a timeout it correctly times out, but I would expect it to detect that the
connection is closed/closing and throw a proper error even without the timeout.
> The errors I see in the log are these (more completel log attached):
> DEBUG [sshd-SshClient[329a1f8d]-nio2-thread-5] (Nio2Session.java:137) Caught IOException[An
established connection was aborted by the software in your host machine] - calling handler
> DEBUG [sshd-SshClient[329a1f8d]-nio2-thread-5] (Nio2Session.java:142) Exception handler
threw IllegalStateException, closing the session: No session available
> It's hard to debug for me since it only happens in a multi-threaded scenario and I haven't
been able to generate separate logs per session (is this even possible?)

This message was sent by Atlassian JIRA

View raw message