Slow memory leak in StatefulTreeCache if removal timeout is not configured. --------------------------------------------------------------------------- Key: EJBTHREE-1692 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1692 Project: EJB 3.0 Issue Type: Bug Components: cache, Clustering Affects Versions: 1.0.0-CR1 Reporter: Brian Stansberry Fix For: 1.0.0-CR2 StatefulTreeCache maintains a Map<GUID, Long> of all beans that is used 1) to drive removal of expired beans, and 2) to provide the answer to the Cache.getTotalSize() management method. Problem is entries will never be removed from this map if @CacheConfig.removalTimeoutSeconds is left at the default value of 0. Solution is to not use the Map if removalTimeoutSeconds is 0. Implement a different mechanism to answer Cache.getTotalSize(). -- 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