[JBoss JIRA] (ISPN-1822) Cache entry not evicted from memory on IBM JDK when another entry was loaded from a cache loader and maxEntries had been reached
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-1822?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-1822:
-----------------------------------
Fix Version/s: 6.0.0.Beta1
(was: 6.0.0.Alpha4)
> Cache entry not evicted from memory on IBM JDK when another entry was loaded from a cache loader and maxEntries had been reached
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-1822
> URL: https://issues.jboss.org/browse/ISPN-1822
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.1.0.FINAL
> Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pxi3260sr9fp1-20110208_03(SR9 FP1))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110203_74623 (JIT enabled, AOT enabled) ;
> java version "1.7.0"
> Java(TM) SE Runtime Environment (build pxi3270-20110827_01)
> IBM J9 VM (build 2.6, JRE 1.7.0 Linux x86-32 20110810_88604 (JIT enabled, AOT enabled)
> Reporter: Martin Gencur
> Assignee: Tristan Tarrant
> Fix For: 6.0.0.Beta1
>
>
> This behavior is specific to IBM JDK (I tried JDK6 and 7), it works fine with Java HotSpot.
> Steps to reproduce the problem:
> 1) set maxEntries for eviction to 2 and algorithm e.g. to LRU
> 2) store 3 entries key1, key2, key3 to the cache (after that you can see that the cache contains only 2 entries - key2 and key3, the first one was evicted from memory)
> 3) call cache.get("key1")
> 4) PROBLEM - cache contains all key1, key2, key3 even though it should contain only 2 entries - only happens with IBM JDK (6 or 7 ..no matter)
> I'll shortly issue a pull request with a test to ispn-core
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (ISPN-2463) Clean up Configuration API in test suites
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2463?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2463:
-----------------------------------
Fix Version/s: 6.0.0.Beta1
(was: 6.0.0.Alpha4)
> Clean up Configuration API in test suites
> -----------------------------------------
>
> Key: ISPN-2463
> URL: https://issues.jboss.org/browse/ISPN-2463
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite
> Affects Versions: 6.0.0.Alpha1, 6.0.0.Alpha4
> Reporter: Navin Surtani
> Assignee: Navin Surtani
> Labels: configuration, testsuite
> Fix For: 6.0.0.Beta1
>
>
> For ISPN 6.x, the package org.infinispan.config needs to be deleted. We need to go through each individual module and clean out every usage of this package (specifically the testsuite) and migrate all usages of the org.infinispan.config API to the org.infinispan.configuration.cache API.
> A sub-task for each module should be created so that it would make easier tracking of individual pull-requests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months