did a search for mcast_port through Jboss deploy folder and came up with following :
also came up with :
don't think this last one needs to be isolated?
The first four are the standard ones. The last only comes into play if you go out of your way to use an obscure feature in the jmx-console.
Unfortunately there's no simple way to verify isolation. A good approach is to give each cluster a different partition name (via the -g swtich at startup) and then include the partition name as an element in the group name passed to JGroups. This is controlled via the "PartitionName" attribute in cluster-service.xml and the "ClusterName" attribute in the other files. If you do this and mistakenly mix the clusters, they will complain in the logs about receiving messages for another group, alterting you to the problem.