- The jvmRoute is set via an environment variable jboss.jvmRoute, which is set in our startscript to be the hostename of the server. Since these are different, the appserver1 entry in jvmRoute is a typo (I had to edit company stuff out). In our production test case, the jvmRoutes are different
- We are indeed using ports-default and ports-01 (ports-02, ports-03, etc) settings when starting up the JBoss-AS instances, so that you have http://appserver1:8080 and http://appserver2:8180 available
The resaon we cannot use virtual nics is that we don't have that many IP's available (the 192.68.x.y is of course an example here, in real life we have to use routable IP-addresses). Questions are thus:
- Have you tried to make the configuration work (or not work) with the ports-?? options from JBoss, or just with each cluster it's own IP-address ?
- Is it possible to make a configuration we are using to work ? I find it strange if it's not, bacause the whole mod_cluster / JBoss ports mechanism is designed in the first place to make this easier.
- Is there any other documentation available (other than getting the minimal-configuratiun to work) ?