[jira] [Commented] (KARAF-1823) Memory leak on windows in SSHD ServerSession

["Henryk Konsek (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499302#comment-14499302 ] 

Henryk Konsek commented on KARAF-1823:
--------------------------------------

Hi [~gnt],

Can this affect Karaf 2.3 i.e. Fuse 6.1?

Cheers.

> Memory leak on windows in SSHD ServerSession
> --------------------------------------------
>
>                 Key: KARAF-1823
>                 URL: https://issues.apache.org/jira/browse/KARAF-1823
>             Project: Karaf
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>
> We use apache-karaf-2.2.9 in windows 2008 server R2.
> I've run a lot of Ssh "Echo" in a short time. And the karaf memory peaked,
> and we receive out of memory as exception.(see the attached picture
> http://karaf.922171.n3.nabble.com/file/n4026025/Jconsole_Karaf.png )
> Running jhat shows some classes that should consume such memory:
> class org.apache.activemq.command.ProducerId 21706 955064
> class org.apache.felix.gogo.runtime.Token 46536 930720
> class org.apache.felix.gogo.runtime.Closure 9972 717984
> *class org.apache.sshd.server.session.ServerSession 1662 563418
> class org.apache.mina.transport.socket.nio.NioSocketSession 1662 511896 *
> class [Lorg.apache.activemq.command.DataStructure; 48 393984
> The memory leak seems to lie around unclosed ssh server session.
> To reproduce the problem, you have just to run this script "loopsshecho.bat"
> that will allow to reproduce rapidly the bug
> http://karaf.922171.n3.nabble.com/file/n4026025/probes.zip probes.zip :
> {code}
> @echo ON
> :again
> CALL launch-javaprobe.bat com.eurofins.nagios.probe.ssh.SSHEcho --hostname
> Localhost --login karaf --password karaf --sshport 8101
> ECHO .
> goto again
> {code}
> You have to change the parametrs of :
> --hostname
> --login
> --password
> --sshport



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)