[
https://issues.apache.org/jira/browse/SSHD-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318751#comment-16318751
]
Goldstein Lyor commented on SSHD-793:
-------------------------------------
The client code does not seem to really test SSH client - closing a socket
abruptly without any SSH traffic may cause some memory to be allocated which
takes some time to release. If the client keeps creating and dropping
connections at a very high rate, the GC and other code that eventually
de-allocates the original memory allocated when connection was established
cannot release it at a sufficient rate. This is not something specific to SSHD
but rather to all servers - they are all subject to memory "leaks" if a high
enough sustained connection rate is applied to them. This is why there are
routers and firewalls in the middle. To really declare that SSHD server leaks
you need to run a more realistic scenario over a (much) longer time. There may
be a leak, but this very simple code does not indicate it... closing the issue
- please feel free to re-open if a more realistic scenario can be used to
reproduce this.
> Continuously connecting to sshd server lead to memory leaks
> -----------------------------------------------------------
>
> Key: SSHD-793
> URL: https://issues.apache.org/jira/browse/SSHD-793
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 1.7.0
> Environment: Linux
> Reporter: Li Fangning
> Attachments: SshClientTest.java, SshdServerTest.java
>
>
> Run the attachments [^SshdServerTest.java] and [^SshClientTest.java],
> [^SshdServerTest.java]'s memory will continue to rise and lead to
> {{OutOfMemory}} error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
