[jbosscache-issues] [JBoss JIRA] Updated: (JBCACHE-1578) ExpirationAlgorithm doesn't seem to work properly when same fqn are modified and removed in parallel

[Nicolas Filotto (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Filotto updated JBCACHE-1578:
-------------------------------------

    Attachment: TestExpirationAlgorithm.java


> ExpirationAlgorithm doesn't seem to work properly when same fqn are modified and removed in parallel
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1578
>                 URL: https://jira.jboss.org/jira/browse/JBCACHE-1578
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.3.CR1, 3.2.3.GA
>            Reporter: Nicolas Filotto
>            Assignee: Manik Surtani
>             Fix For: 3.2.3.CR1
>
>         Attachments: TestExpirationAlgorithm.java
>
>
> I have a memory leak in my application that uses the ExpirationAlgorithm, after a deeper investigation it seems that some nodes are never evicted so after a certain period of time I get OutOffMemoryError.
> I attached a UnitTest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira