[ https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
masc updated SSHD-786: ---------------------- Comment: was deleted (was: I see the real stack trace is swallowed when this error is logged. {code} protected Nio2Session createSession(Nio2Acceptor acceptor, SocketAddress address, AsynchronousSocketChannel channel, IoHandler handler) throws Throwable { if (log.isTraceEnabled()) { log.trace("createNio2Session({}) address={}", acceptor, address); {code} I will change this in the next build and report back with more details.) > Clients can't authenticate after unexpected exception in Nio2Acceptor > --------------------------------------------------------------------- > > Key: SSHD-786 > URL: https://issues.apache.org/jira/browse/SSHD-786 > Project: MINA SSHD > Issue Type: Bug > Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.6.0 > Environment: Windows > Reporter: masc > > {code} > 2017-11-28 15:26:54,808 11566202 sshd-SshServer[434a2a10]-nio2-thread-4 > org.apache.sshd.common.io.nio2.Nio2Acceptor WARN - Caught IOException while > accepting incoming connection from /0:0:0:0:0:0:0:0:13003: The specified > network name is no longer available. > java.io.IOException: The specified network name is no longer available. > at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309) > at sun.nio.ch.Iocp.access$700(Iocp.java:46) > at sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:399) > at java.lang.Thread.run(Thread.java:748) > {code} > As soon as this exception occurs once, clients can still connect but will > fail to authenticate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)