Hello,
the cache policy (i.e. the algorithm used to decide when a cache entry
should age out of the cache, and hence passivate a bean) and the cache size
should be something manageable in jBoss, or it is not the case ?
For example, should a sys-admin be able to manage through JMX the jBoss
server and change its cache sizes or policies at runtime or this is a
feature not requested / important ?
I remember a post of Rickard saying that could be an option for the cache
size, what about the policies ?
BS
