Description of problem: The ForceReturnValuesTest.testDifferentInstancesForDifferentForceReturnValues test is failing when checking the previous retunr value when ForceReturnValue is true for the cache. Here is code: public void testDifferentInstancesForDifferentForceReturnValues() { RemoteCache<String, String> rcDontForceReturn = remoteCacheManager.getCache(false); RemoteCache<String, String> rcForceReturn = remoteCacheManager.getCache(true); assertNotSame("RemoteCache instances should not be the same", rcDontForceReturn, rcForceReturn); String rv = rcDontForceReturn.put("Key", "Value"); assertNull(rv); rv = rcDontForceReturn.put("Key", "Value2"); assertNull(rv); rv = rcForceReturn.put("Key2", "Value"); assertNull(rv); rv = rcForceReturn.put("Key2", "Value2"); assertNotNull(rv); <-- THIS ASSERT FAILS, rv IS NULL assertEquals("Previous value should be 'Value'", "Value", rv); } Version-Release number of selected component (if applicable): JDG 6.6 DR3 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I was unable to reproduce this in straight C++ code, so the issue is somewhere in the SWIG layer. Investigating now.
Now I can't reproduce this in SWIG either. Closing...
Re-opening, because this has reappeared in the JDG 6.6 DR4 build
This failure occurs when requesting a cache with force return values equal to true from RemoteCacheManager.getCache(), but not when requesting the same cache with RemoteCache.withFlags(Flag.FORCE_RETURN_VALUE)
Created attachment 1087661 [details] Memtestv logs memtestv logs that show uninitialized variable warnings
Verified in JDG 6.6.0 ER1