• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • hhuynh
  • Reporter: teck
  • January 23, 2008
  • 0
  • Watchers: 0
  • March 27, 2008
  • February 21, 2008

Attachments

Description

I ran this test on revision 6811of the 2.5 branch

Replace this file dso-tests-jdk15/tests.system.resources/com/tc/properties/tests.properties with the attached version. These settings might be slightly ridiculous, but I don’t think they should cause an AssertionError.

After replacing that file, just run this test :

tcbuild check_one ConcurrentHashMapSwapingTest

After a while, you should get this error: 2008-01-23 20:19:59,829 [TC Memory Monitor] ERROR com.tc.runtime.TCMemoryManagerImpl - Exception thrown java.lang.AssertionError: Computed Object to evict is out of range : toEvict = 2263 currentCount = 1842 CacheStats[ type = MemoryEventType.ABOVE_THRESHOLD, usage = Jdk15MemoryUsage ( max = 477233152, used = 48104360, free = 429128792, used % = 10, collectionCount = 2 ), countBefore = 1842, toEvict = 2263, evicted = 0, countAfter = 0, objectsGCed = false, state = State[ INIT ]] at com.tc.object.cache.CacheManager$CacheStatistics.getObjectCountToEvict(CacheManager.java:91) at com.tc.object.ClientObjectManagerImpl.evictCache(ClientObjectManagerImpl.java:1141) at com.tc.object.cache.CacheManager.memoryUsed(CacheManager.java:50) at com.tc.runtime.TCMemoryManagerImpl.fireMemoryEvent(TCMemoryManagerImpl.java:102) at com.tc.runtime.TCMemoryManagerImpl.access$500(TCMemoryManagerImpl.java:17) at com.tc.runtime.TCMemoryManagerImpl$MemoryMonitor.fire(TCMemoryManagerImpl.java:196) at com.tc.runtime.TCMemoryManagerImpl$MemoryMonitor.reportUsage(TCMemoryManagerImpl.java:183) at com.tc.runtime.TCMemoryManagerImpl$MemoryMonitor.run(TCMemoryManagerImpl.java:137) at java.lang.Thread.run(Thread.java:595)

Comments

Saravanan Subbiah 2008-02-20

Take a look at this and lets discuss a fix for it.