bela wrote:anonymous wrote : 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. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836991#3836991 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3836991 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
