tomaswolf commented on issue #578: URL: https://github.com/apache/mina-sshd/issues/578#issuecomment-2275432488
As I understand it the exception means the O/S thinks it lost the connection. Hence closing all channels and the session is the right thing to do. Apparently Windows has some timeout somewhere, and if no message arrives within that time, it produces this error. (At least that is how I read that error messsage.) Evidently this might be a problem for high-latency connections. I don't know if that timeout value can be tweaked at O/S level somehow. At application level you may perhaps be able to do something by using heartbeats that require the server to reply, and running them in an interval shorter than that timeout (in fact, interval + time until you get the reply < that O/S timeout.) Set properties `CoreModuleProperties.HEARTBEAT_INTERVAL` and `CoreModuleProperties.HEARTBEAT_NO_REPLY_MAX` on the SshClient, the latter > 0. This sends SSH global requests and requests a reply from the server. If your commands produce output on stdout or stderr, make sure you read it. Otherwise the channel window may drop to zero, and the server won't send data anymore. -- 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
