You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Lyor Goldstein (Jira)" <ji...@apache.org> on 2021/08/02 17:12:00 UTC
[jira] [Comment Edited] (SSHD-1180) Limiting the number of active
sessions
[ https://issues.apache.org/jira/browse/SSHD-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391708#comment-17391708 ]
Lyor Goldstein edited comment on SSHD-1180 at 8/2/21, 5:11 PM:
---------------------------------------------------------------
Looks like some bug in the client code that does not close its session (in this case some JSCH client). Does not seem to be the server's fault - there are simply more clients who for some reason do not disconnect. In any case, there is a limit on the number of concurrent sessions a server is allowing - see {{CoreModuleProperties.MAX_CONCURRENT_SESSIONS}}.
was (Author: lgoldstein):
Looks like some bug in the client code that does not close its session (in this case some JSCH client). Does not seem to be the server's fault.
> Limiting the number of active sessions
> --------------------------------------
>
> Key: SSHD-1180
> URL: https://issues.apache.org/jira/browse/SSHD-1180
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Subramaniajeeva
> Priority: Major
>
> I upgraded mina version from 2.3.0 to 2.6.0 two months back. Since then I could see that the number of sessions being held keep on increasing for a particular client. I found this using {color:#9876aa}sshd{color}.getActiveSessions().
> On analysing further,I could see the below messages from debug logs:
> {code:java}
> 2021-06-05 00:00:00.222 [DEBUG] [sshd-SshServer[18a79bc1](port=2000)-nio2-thread-5] ServerConnectionService - globalRequest(ServerConnectionService[ServerSessionImpl[<username>@/10.125.247.40:46011]]) received SSH_MSG_GLOBAL_REQUEST keepalive@jcraft.com want-reply=true{code}
> Looks like the client keep on sending keep alive packets even after the file transfer is done keeping the session active. I didn't see this behaviour in earlier version.
> Can I get some help on resolving this issue? Is there a systemic way to figure out the last activity based on which cancel the session?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@mina.apache.org
For additional commands, e-mail: dev-help@mina.apache.org