I don't think that will help. First, I think that cache.getServiceName() will return null if my cache instance isn't defined as a jboss service. Maybe I can set the service name after registration for later use but the problem remains that each interceptor's registration name is modified by WebSphere such that I can't easily derive it from a service name. For example, jboss.cache:service=TreeCache-Cluster,treecache-interceptor=TxInterceptor, the registration name in WebSphere becomes jboss.cache:service=TreeCache-Cluster,cell=citgoNode01Cell,treecache-interceptor=TxInterceptor,node=citgoNode01,process=server1 I suppose I could parse the bits that WebSphere adds, figure out which should be used as a prefix, which as a postfix, etc. but that seems cumbersome and probably susceptible to other implementation quirks. It seems like it would be safer to just store the actual object names and use them when needed. This could probably be optimized by determining whether we need to do this (e.g., only when an mbean server mangles names) but this code only executes when the cache is started or destroyed so it might not be worthwhile to optimize it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038547#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...