[jira] [Commented] (SSHD-779) Deadlock in ChannelOutputStream

[ https://issues.apache.org/jira/browse/SSHD-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291184#comment-16291184 ] Goldstein Lyor commented on SSHD-779: - BTW, see also SSHD-786 - not exactly this issue, but sometimes

[jira] [Commented] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor

[ https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291181#comment-16291181 ] Goldstein Lyor commented on SSHD-786: - A very good idea - you can find the branch in

[jira] [Commented] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor

[ https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290657#comment-16290657 ] masc commented on SSHD-786: --- delegating such errors to a listener would be beneficial in general, yes. I don't see

[jira] [Commented] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor

[ https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290599#comment-16290599 ] Goldstein Lyor commented on SSHD-786: - How about this - if the (re-)accept call fails when invoked by