[infinispan-issues] [JBoss JIRA] (ISPN-1915) Memory leak in L1 manager

[Bela Ban (JIRA)]

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

Bela Ban commented on ISPN-1915:
--------------------------------

OK, the memory leak is still present in the 3 node case (2 passives, 1 active): the 2 passives run out of memory. Same culprit as in the (fixed) 2 node case: L1CacheManagerImpl.
                
> Memory leak in L1 manager
> -------------------------
>
>                 Key: ISPN-1915
>                 URL: https://issues.jboss.org/browse/ISPN-1915
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Distributed Cache
>    Affects Versions: 5.1.2.FINAL
>            Reporter: Manik Surtani
>            Assignee: Manik Surtani
>            Priority: Blocker
>              Labels: memory_leak
>             Fix For: 5.1.3.CR1, 5.1.3.FINAL
>
>
> From an email from Bela:
> {quote}
> OK, when running async DIST with 2 nodes and numOwners == 2, I found a huge memory leak in the L1ManagerImpl !
> With L1 enabled, my test with 1 passive and 1 active node wouldn't complete with 10 threads each putting 100'000 elements in the cache; instead the passive node would always OOME !
> With L1 disabled, it would complete, with 23'000 TXs / sec !
> Profiling the passive node (the one which would receive the modifications via RPCs), I can see that L1ManageImpl.addRequestor() leaks entries in the 'requestors' hashmap.
> ******
> The weird thing is that L1 shouldn't even matter in the 2 node case !
> ******
> {quote}

--
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