mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Goldstein Lyor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor
Date Mon, 11 Dec 2017 17:22:00 GMT

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

Goldstein Lyor commented on SSHD-786:
-------------------------------------

{quote}
I don't see how a single retry would be a feasible solution to this problem.
{quote}
I don't think it is a single retry - remember: this is an *asynchronous* API so the {{socket.accept(addr,
this)}} simply tells the network layer to resume listening - same as {{onSuccess}}.

> 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
>
> {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)

Mime
View raw message