coderZoe commented on issue #482: URL: https://github.com/apache/mina-sshd/issues/482#issuecomment-2081290796
> Setting a "global request" handler for keep-alives has only an effect on global requests. It has no effect on channel requests. OpenSSH prefers to send keep-alive messages a channel requests if a channel is open, and then expects a failure reply. > > Apache MINA SSHD actually behaves like OpenSSH expects; the only problem is that it logs this warning. That's issue [SSHD-1237](https://issues.apache.org/jira/browse/SSHD-1237). > > I don't think your problem is related to this warning. But I don't know what might cause your problem; it looks like your code is reading from a `ChannelAsyncInputStream` when that stream is being closed. Why it is being closed I cannot tell. I think I understand why the connection was actively disconnected because the server's sshd_config is configured with ClientAliveInterval 600. Regarding your second issue, to resolve the warning logs like `o.a.sshd.client.channel.ChannelShell - handleUnknownChannelRequest(ChannelShell[id=0, recipient=0]-ClientSessionImpl[admin@/10.252.146.106:61122]) Unknown channel request: keepal...@openssh.com[want-reply=true]`, I looked at the Jira link you provided. This means the KeepAliveHandler.INSTANCE I set in globalRequestHandlers did not affect individual channels. If I want it to work and avoid these warnings, do I need to add a request handler for each channel and implement logic similar to KeepAliveHandler.INSTANCE within them? -- 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
