On 11/25/10 4:55 AM, Heiko W.Rupp wrote: I'm not sure what you mean. In AS 6 the most relevant things are the mbean interfaces exposed by the JBoss Web StandardManager class (non-clustered) versus the AS's JBossCacheManager class (clustered). There the latter's mbean interface is a superset of the former's. That's to account for some configuration options that jboss-web.xml exposes for clustered webapps (IMHO valid to expose) and the fact that a distributed session cache inherently has a different set of capabilities from a non-distributed one -- primarily that it can store (and thus use resources for) backup copies of sessions that are being handled on other servers in the cluster. If a tool doesn't want to expose that extra information it doesn't have to. -- Brian Stansberry Principal Software Engineer JBoss by Red Hat