I think there was a problem with how TreeCacheSSOClusterManager was finding the JMX server -- I'm expecting your command line switch caused another JMX server to start and TreeCacheSSOClusterManager was finding that (sorry -- at work now and can't confirm).
Last night I committed a patch to Branch_4_0 CVS that should fix this. Earlier today I replied to the e-mail you sent me with the config files. Email included a zip with the latest version and compiled classes, which if you want you can integrate to see if it solves your problem. Tonight I'll try using the -Dcom.sun.management.jmxremote switch and see if my patch resolves the problem. BTW, thanks for the very clear report. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887754#3887754 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887754 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
