If you deploy a copy of the whole cluster-service.xml file, you're going to deploy more than just a partition; i.e. another HA-JNDI, etc. To get the farming to work, just deploy the cluster partition MBean. Whether you want a separate instance of things like HASessionStateService, cache invalidation bridge, etc. really depends on the architecture of your app and is probably too complex for a forum discussion.
Do you just want to deploy certain beans on certain nodes, but have them visible via JNDI from all nodes? If so, just do the farming part, and leave the <partition-name> element in each bean's jboss.xml set to DefaultPartition. This has the same effect as if you'd deployed Group1EJB1 to node1 and 2 without using farming. In the partition config for your group1 & 2 partitions, don't just change the partition name. Also change the multicast address and port in the UDP section of the config. Otherwise the low-level JGroups protocols will have to process and discard packets meant for the other partitions. Re: farming, if you use the general farming service to deploy your group1 & 2 farm services, JBoss will try to deploy the group1-farm-service.xml on a machine with no group1 partition, and the deploy will fail. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3902678#3902678 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3902678 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
