[infinispan-issues] [JBoss JIRA] (ISPN-1611) Hotrod server memory leak after enable idle timeout

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675107#comment-12675107 ] 

RH Bugzilla Integration commented on ISPN-1611:
-----------------------------------------------

Tristan Tarrant <ttarrant at redhat.com> changed the Status of [bug 768411|https://bugzilla.redhat.com/show_bug.cgi?id=768411] from VERIFIED to CLOSED
                
> Hotrod server memory leak after enable idle timeout
> ---------------------------------------------------
>
>                 Key: ISPN-1611
>                 URL: https://issues.jboss.org/browse/ISPN-1611
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Cache Server
>    Affects Versions: 5.1.0.CR1
>            Reporter: hs z
>            Assignee: Galder Zamarreño
>            Priority: Blocker
>             Fix For: 5.1.0.CR2
>
>
> i set --idle_timeout=15 as param, threads count and memory usage always grow, i got a heap dump and found many netty HashedWheelTimer instances cost much memory.
> in HashedWheelTimer javadoc, it says: "Do not create many instances. HashedWheelTimer creates a new thread whenever it is instantiated and started. Therefore, you should make sure to create only one instance and share it across your application. One of the common mistakes, that makes your application unresponsive, is to create a new instance in ChannelPipelineFactory, which results in the creation of a new thread for every connection.". but in infinispan NettyChannelPipelineFactory.scala, there is "timer = new HashedWheelTimer", it's misused.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira