tomaswolf commented on issue #312:
URL: https://github.com/apache/mina-sshd/issues/312#issuecomment-1385419758
The error message appears to indicate that this is Windows error 10038 ("An
operation was attempted on something that is not a socket."). Searching the
Internet for "OS 10038" or related things (like the Chinese error message
text!) gets quite a few hits. Some include the Apache HTTP server; compare the
[mod_winnt configuration of Apache httpd
2.2](https://httpd.apache.org/docs/2.2/mod/mpm_winnt.html#win32disableacceptex).
(In newer releases, that config was removed; compare the [httpd 2.4
documentation](https://httpd.apache.org/docs/current/mod/mpm_winnt.html): it
appears the problem is still there, but httpd falls back to another API if
there are too many failures.)
The cause appears to be unclear. Most hits report this occurring suddenly
from time to time in otherwise working applications. It's being mentioned for
many different applications. Some mention it was some corruption in the Windows
TCP/IP stack, and some people claim running "netsh winsock reset" would resolve
this problem.
It is possible that the AsynchronousSocketChannel used by the Apache MINA
sshd NIO2 transport back-end exercises some Windows code that triggers a bug in
Windows. The Java native code does use the Windows ConnectEx function... maybe
that can have the same problem as AcceptEx mentioned on other sites. JSch
definitely doesn't use AsynchronousSocketChannel.
You could try using the sshd-mina or sshd-netty transport back-ends with
Apache MINA sshd; those also do not use AsynchronousSocketChannel.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
