[jbosscache-issues] [JBoss JIRA] Updated: (JBCACHE-1582) ExpirationAlgorithm doesn't evict nodes that have been created in a long Tx
[
https://jira.jboss.org/browse/JBCACHE-1582?page=com.atlassian.jira.plugin...
]
Nicolas Filotto updated JBCACHE-1582:
-------------------------------------
Description:
I noticed that I had a memory leak in my application when I use the ExpirationAlgorithm
(maybe this bug happens with other algorithms) due to some nodes that were never evicted.
After a deeper investigation, I noticed that no EvictionEntry was created for those nodes
since the method getExpiration returns null (which also means that cache.peek(fqn, false)
returns null). I finally found the problem, that is because if the Expiration Thread wakes
up before that the related Tx is committed, it doesn't find the node into the cache so
it considers it as removed but in fact it is just because the Tx has not yet been
committed. This has for consequence that the node will never be evicted and thus create a
memory leak.
Please find the related unit test as attached file.
was:
I noticed that I had a memory leak in my application when I use the ExpirationAlgorithm
(maybe this bug happens with other algorithms) some nodes were never evicted. After a
deeper investigation, I noticed that the no EvictionEntry was created for those nodes
since the method getExpiration returns null (which also means that cache.peek(fqn, false)
returns null). I finally found the problem, that is because if the Expiration Thread wakes
up before that the related Tx is committed, it won't find the node into the cache so
it will considered it as removed but in fact it is just because the Tx has not yet been
committed. This has for consequence that the node will never be evicted and thus create a
memory leak.
Please find the related unit test as attached file.
ExpirationAlgorithm doesn't evict nodes that have been created in
a long Tx
----------------------------------------------------------------------------
Key: JBCACHE-1582
URL: https://jira.jboss.org/browse/JBCACHE-1582
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Eviction
Affects Versions: 3.2.5.GA
Reporter: Nicolas Filotto
Assignee: Manik Surtani
Attachments: TestExpirationAlgorithm.java, TestExpirationAlgorithm.java
I noticed that I had a memory leak in my application when I use the ExpirationAlgorithm
(maybe this bug happens with other algorithms) due to some nodes that were never evicted.
After a deeper investigation, I noticed that no EvictionEntry was created for those nodes
since the method getExpiration returns null (which also means that cache.peek(fqn, false)
returns null). I finally found the problem, that is because if the Expiration Thread wakes
up before that the related Tx is committed, it doesn't find the node into the cache so
it considers it as removed but in fact it is just because the Tx has not yet been
committed. This has for consequence that the node will never be evicted and thus create a
memory leak.
Please find the related unit test as attached file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira