-
1. Re: Can't configure cluster in jboss 5.1
wdfink Feb 16, 2012 2:35 AM (in response to ksermas)1 of 1 people found this helpfulHow do you start your JBoss?
If I understand correct you don't want to have a cluster right?
Or do you want be able to have a cluster but a unwanted member join?
Is a JBoss running at IP *213?
-
2. Re: Can't configure cluster in jboss 5.1
ksermas Feb 16, 2012 5:57 PM (in response to wdfink)Yes it should be a cluster of one. don't ask me why. Thanks for all your help in answereing my question but somehow the jboss came up on the server
after I rebooted it.
-
3. Re: Can't configure cluster in jboss 5.1
ksermas Feb 17, 2012 12:53 PM (in response to ksermas)Found out that the nodename set in the /etc/sysconfig/network-scripts directory was not the same as the nodename in ther /etc/hosts.
It was also the incorrect nodename when I ran the 'hostname' command. Once I corrected both with the correct nodename, the jboss
ran fine.
-
4. Re: Can't configure cluster in jboss 5.1
wdfink Feb 17, 2012 2:00 PM (in response to ksermas)Just for interest ...
do you start or configure JBoss with the hostname or with the IP?
-
5. Re: Can't configure cluster in jboss 5.1
ksermas Feb 17, 2012 2:02 PM (in response to wdfink)ip address but some java components read the nodename.
-
6. Re: Can't configure cluster in jboss 5.1
ksermas Feb 21, 2012 10:36 AM (in response to wdfink)What I really need to know is how to clear the cluster cache. A development server is showing up as part of a cluster on the production side. The production jboss servers see the development server as part of the development cluster and we don't know how do clear the development server's ip from the cluster configuration or the cluster cache.
-
7. Re: Can't configure cluster in jboss 5.1
wdfink Feb 21, 2012 12:40 PM (in response to ksermas)Looks like you did not use the correct start options. See this wiki.
You should use the -g <a name : default is DefaulPartition> -u <multicast address : 230.0.0.4 is default> -m <multicast port> for run.sh.
These three values should separate your cluster. I would recommend to change the parameter in production, this avoid clustering a default instance with the production one