This content has been marked as final. Show 2 replies
But I suggest to ship jbossweb-tomcat5.sar/META-INF/jboss-service.xml with its own TreeCache configuration (e.g. for session repl), and have SSO refer to it via ObjectName.
If you and Scott decide to have the config in jbossweb-tomcat5.sar/META-INF/jboss-service.xml, we need to give the service a less generic name. I suggest, jboss.cache:service=TreeCache,type=jboss.web
BTW, from painful experience I learned the more obvious "jboss.web:service=TreeCache" is no good. The Tomcat5 service's stop() method unregisters all MBeans under the jboss.web space (it assumes they are all Tomcat objects). So, when the ServiceController goes to stop the TreeCache service, it is no longer registered in the JMX server and an exception is thrown.
I add the context in: