[ https://issues.jboss.org/browse/ISPN-4132?page=com.atlassian.jira.plugin.... ] Paul Ferraro edited comment on ISPN-4132 at 4/4/14 10:36 AM: ------------------------------------------------------------- I disagree. The likelihood that a given session attribute will be accessed is not independent of, but is correlated with, the access recency of the session with which it is associated. If a session was not accessed for a given period then we know for certain that its attributes were not accessed for at least as long. The greater point I was trying to make is: it's not always meaningful to base eviction off of a maximum number of entries. WildFly can be configured to store sessions as either 2 entries per session (the default), or N+1 entries per session, where N is the number of attributes in the session. In both cases, all cache entries associated with a session make up a single group. As a user/administrator, I am more interested in specifying the maximum number of sessions (i.e. groups) to keep in memory - irrespective of the cache entry mapping implementation details, since the desired value of max-entries would differ widely based on the session mapping strategy. was (Author: pferraro): I disagree. The likelihood that a given session attribute will be accessed is not independent of, but is correlated with, the access recency of the session with which it is associated. If a session was not accessed for a given period then we know for certain that its attributes were not accessed for at least as long. The greater point I was trying to make is: it's not always meaningful to base eviction off of a maximum number of entries. WildFly can be configured to store sessions as either 2 entries per session (the default), or N+1 entries per session, where N is the number of attributes in the session. In both cases, all cache entries associated with a session make up a single group. As a user/administrator, I am more interested in specifying the maximum number of sessions (i.e. groups) to keep in memory - irrespective of the cache entry mapping implementation details, since the effective value of max-entries would differ based on the session mapping strategy. -- 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