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

masc commented on SSHD-786:
---------------------------

thanks.. we could only see this on productive systems with specific clients and 
currently is not a good time for experimental changes, so please don't wait for 
me. when 1.8.0 is released I will put it live at some appropriate time and 
report back.

> 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
>            Assignee: Goldstein Lyor
>            Priority: Major
>             Fix For: 1.7.0, 1.8.0
>
>
> {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
(v7.6.3#76005)

Reply via email to