Oliver Stöneberg created SSHD-635:
-------------------------------------

             Summary: 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


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
(v6.3.4#6332)

Reply via email to