I use JBoss AS7 in domain-mode on two physical nodes. We run an application for several customers and each customer has it's own server-group (with it's own two server-processes - one per physical-node). We startet a cluster for our first customer and it works. Now we wanted to start the next server-group but those server-processes do not form a cluster - each works only on it own.

First of all UDP seems to work. I run several jgroups-test-applications (and they all worked fine). Example:

I separate customers cluster-traffic by using different UDP- and TCP-ports. I also separate business-traffic from cluster-traffic by using two physical network-interfaces per node. This is the relevant section of the file domain.xml:

After the three-seconds-timeout MPING gives up and asumes that the process is the first in the cluster.

During my experiments I experienced that also the first server-group does not work sometimes: If I shutdown the server on the second node and start it again the cluster doesn't form again. After restarting the server on the first node the cluster is available again. This is the log of the first customer during this

I do not understand what's the reason for this. I tried to find a solution in the web, but no one seems to expirience the same problem. I don't know if this is a network-issue but I don't think so because the jgroups-tests work. Is there any reason why there could be only one cluster at the time? Or what else could bring the problem I see?

You'll need to separate your clusters cleanly; for instance jgroups-tcp uses the same port (9007) for both clusters. I suggest make this and jgroups-tcp-fd use a system property (which is different per cluster), too.

the port 9007 will be increased for each cluster by the jboss domain-controller. In my example cluster A uses port-offset "50" and this results in "9057" and cluster B uses port-offset "250" which results in "9257". This works - I verified this by using "lsof":

>If this doesn't work, I suggest come up with a JGroups-only test and - once you get it working - translate it back to JBoss 7.

I can try this, but I do not know the current JGroups-settings because JBoss AS7 is a zero-config-system - I cannot see the default configuration! So I have to start from scratch what is a problem because I don't know much about those details :-(. But I will do my very best - results will be posted.

and my configuration wasn't applied! The syntax of my adaptions seems to be correct because JBoss starts without any error. Also the spelling of the property-names is correct. Is there something wrong with my configuration? I' afraid of even if I find a working configuration and will not be able to apply it in JBoss because of this problem.

Never the less jgroups does not work - with and without my adaptions. So I will proceed...

I assume this is the sort of configuration you are trying to set up: two isolated server-groups. Is that correct? I'll attach the domain.xml and host.xml in any case.

There is a problem in checking the JGroups configuration using the operation Rado mentioned above - it doesn't seem to be available for me in domain mode and i'm looking into why this is the case. But from what I can tell, JGroups protocol properties are getting processed correctly - certainly in standalone where we verify with the export operation.

This was done with the community AS version 7.1.3.Final-SNAPSHOT; I haven't yet had a chance to try it with the version of AS7 that you were using.

thank you for your response. Meanwhile I know what the problem is (see next post) - thank you for testing!

There is a problem in checking the JGroups configuration using the operation Rado mentioned above - it doesn't seem to be available for me in domain mode and i'm looking into why this is the case. But from what I can tell, JGroups protocol properties are getting processed correctly - certainly in standalone where we verify with the export operation.

This was done with the community AS version 7.1.3.Final-SNAPSHOT; I haven't yet had a chance to try it with the version of AS7 that you were using.

In 7.1.2.Final I get the config in cluster-mode. But as I mentioned it does reflect the properties I set. Is there another possibility to check whether my properties has been applied?

It works if I set the bind_addr to the main-address of the machine. The 10.9.0.x-address is bound on a second network-card to separate cluster- and business-traffic. It seems my colleagues managing the operating system (I only implement Java-software and manage the JBoss-servers) did not configure the multicast-address to use this second network-card either. I will check this...

Firstly, we have found out why the export-native-configuration operation was not working in domain mode in AS 7.1.2, and this will be fixed for AS 7.1.3. So, calling this command can be done as follows:

Secondly, concerning the application of JGroups subsystem protocol properties to the actual JGroups protocdol instances created, the visibility of these properties needs to be improved and will be (https://issues.jboss.org/browse/AS7-4083) . However, I did verify that any protocol properties specified in the JGroups subsystem do get correctly applied, using a debugger. The exception to this are properties which try to override socket binding values, and these properties are ignored - the values specified in the socket binding take precedence. So, for example, trying to override the value of mcast_port in MPING as an MPING property will have no effect. We plan to issue a warning message in such cases for AS 7.1.3.

In other words, a property of a protocol layer is an addressable resource with the last component of the address being property=<property_name> which needs to be first added to the management api. This resource has an attribute named "value" which can be read and written as above. It can also be removed.