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

[JBoss JIRA] Created:...

Nicolas Filotto (JIRA)

Wednesday, 21 April 2010 Wed, 21 Apr '10

7:12 p.m.

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

Show replies by date

Nicolas Filotto (JIRA)

Wednesday, 21 April Wed, 21 Apr

7:12 p.m.

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

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] 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

Nicolas Filotto (JIRA)

7:14 p.m.

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

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] Nicolas Filotto updated JBCACHE-1578: ------------------------------------- Description: 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 some OutOffMemoryErrors. I attached a UnitTest. was: 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.

...

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 some OutOffMemoryErrors. I attached a UnitTest.

Nicolas Filotto (JIRA)

7:14 p.m.

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

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] Nicolas Filotto updated JBCACHE-1578: ------------------------------------- Summary: ExpirationAlgorithm doesn't seem to work properly when same fqns are modified and removed in parallel (was: ExpirationAlgorithm doesn't seem to work properly when same fqn are modified and removed in parallel)

...

ExpirationAlgorithm doesn't seem to work properly when same fqns 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 some OutOffMemoryErrors. I attached a UnitTest.

Dennis Reed (JIRA)

Thursday, 22 April Thu, 22 Apr

8:02 a.m.

New subject: [JBoss JIRA] Commented: (JBCACHE-1578) ExpirationAlgorithm doesn't seem to work properly when same fqns are modified and removed in parallel

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] Dennis Reed commented on JBCACHE-1578: -------------------------------------- Appears to be a regression caused by the JBCACHE-1575 patch. A NullPointerException is killing the expiration thread.

...

Dennis Reed (JIRA)

8:12 a.m.

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

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] Dennis Reed updated JBCACHE-1578: --------------------------------- Attachment: JBCACHE-1578.patch

...

ExpirationAlgorithm doesn't seem to work properly when same fqns 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: JBCACHE-1578.patch, 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 some OutOffMemoryErrors. I attached a UnitTest.

Nicolas Filotto (JIRA)

9:14 a.m.

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

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] Nicolas Filotto updated JBCACHE-1578: ------------------------------------- Affects Version/s: (was: 3.2.3.CR1)

...

ExpirationAlgorithm doesn't seem to work properly when same fqns 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.GA Reporter: Nicolas Filotto Assignee: Manik Surtani Fix For: 3.2.3.CR1 Attachments: JBCACHE-1578.patch, 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 some OutOffMemoryErrors. I attached a UnitTest.

Galder Zamarreno (JIRA)

12:37 p.m.

New subject: [JBoss JIRA] Assigned: (JBCACHE-1578) ExpirationAlgorithm doesn't seem to work properly when same fqns are modified and removed in parallel

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] Galder Zamarreno reassigned JBCACHE-1578: ----------------------------------------- Assignee: Galder Zamarreno (was: Manik Surtani)

...

ExpirationAlgorithm doesn't seem to work properly when same fqns 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.GA Reporter: Nicolas Filotto Assignee: Galder Zamarreno Fix For: 3.2.3.CR1 Attachments: JBCACHE-1578.patch, 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 some OutOffMemoryErrors. I attached a UnitTest.

Nicolas Filotto (JIRA)

1:21 p.m.

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

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] Nicolas Filotto updated JBCACHE-1578: ------------------------------------- Fix Version/s: (was: 3.2.3.CR1)

...

ExpirationAlgorithm doesn't seem to work properly when same fqns 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.GA Reporter: Nicolas Filotto Assignee: Galder Zamarreno Attachments: JBCACHE-1578.patch, 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 some OutOffMemoryErrors. I attached a UnitTest.

Galder Zamarreno (JIRA)

4:57 p.m.

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

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] Galder Zamarreno updated JBCACHE-1578: -------------------------------------- Fix Version/s: 3.2.4.GA

...

ExpirationAlgorithm doesn't seem to work properly when same fqns 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.GA Reporter: Nicolas Filotto Assignee: Galder Zamarreno Fix For: 3.2.4.GA Attachments: JBCACHE-1578.patch, 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 some OutOffMemoryErrors. I attached a UnitTest.

Galder Zamarreno (JIRA)

Monday, 3 May Mon, 3 May

6:46 p.m.

New subject: [JBoss JIRA] Closed: (JBCACHE-1578) ExpirationAlgorithm doesn't seem to work properly when same fqns are modified and removed in parallel

[ https://jira.jboss.org/jira/browse/JBCACHE-1578?page=com.atlassian.jira.p... ] Galder Zamarreno closed JBCACHE-1578. ------------------------------------- Resolution: Done

...

ExpirationAlgorithm doesn't seem to work properly when same fqns 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.GA Reporter: Nicolas Filotto Assignee: Galder Zamarreno Fix For: 3.2.4.GA Attachments: JBCACHE-1578.patch, 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 some OutOffMemoryErrors. I attached a UnitTest.

5108

days inactive

5120

days old

jbosscache-issues@lists.jboss.org

Manage subscription

10 comments

3 participants

tags (0)

participants (3)

Dennis Reed (JIRA)
Galder Zamarreno (JIRA)
Nicolas Filotto (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

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