I'm also having this problem at the moment. The server I'm working from is the 'standard' server config.
I also see the same behaviour under JBoss 4.0.0. HOWEVER - if I start up the 'all' configuration, which has another cluster already configured, then I don't get the error on the cache already configured - but when I copy in mine, same thing :( My configuration was first copied straight from the online docs, then I compared it to the one which seems to work in the 'all' server configuration. Apart from the names and the multicast info, no difference. Cheers, C View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886568#3886568 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886568 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
