Concurrent access and removal of an AtomicMap should result in an IllegalStateException --------------------------------------------------------------------------------------- Key: ISPN-1121 URL: https://issues.jboss.org/browse/ISPN-1121 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 4.2.1.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.CR3, 5.0.0.FINAL Currently, we see: {code} tx.begin(); Map<?,?> map = AtomicMapLookup.getAtomicMap(cache, key); assert map.size() == 3; AtomicMapLookup.removeAtomicMap(cache, key); assert map.size() == 0; tx.commit(); {code} Access to the map after its removal is invalid, since even storing data here would be lost. An {{IllegalStateException}} should be thrown if one attempts to access or manipulate an {{AtomicMap}} after the {{AtomicMap}} has been removed from the cache, since this represents a stale handle. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira