3 Replies Latest reply on Feb 27, 2003 10:05 AM by prpatel

Clustering - Nodes don't pick each other up

cessner Feb 20, 2003 3:44 PM

I have two boxes, both the same setup (rayden,subzero):

Redhat 8.0
jdk1.4.1_01
jboss-3.0.6_tomcat-4.1.18.zip

Deployed the same cluster-service.xml to both JBOSS_HOME/server/default/deploy dirs

Rayden:
2003-02-20 12:40:07,947 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/usr/local/jboss-3.0.6_tomcat-4.1.18/server/default/deploy/cluster-service.xml
2003-02-20 12:40:08,148 INFO [org.jboss.ha.framework.server.ClusterPartition] Creating
2003-02-20 12:40:09,021 INFO [org.jboss.ha.framework.server.ClusterPartition] Set the JavaGroups logging to log4j with category:org.apache.log4j.Logger@b3cac9, priority: DEBUG, JavaGroupsLevel: 4
2003-02-20 12:40:09,208 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Initializing
2003-02-20 12:40:09,323 INFO [org.jboss.ha.framework.server.ClusterPartition] Created
2003-02-20 12:40:09,489 INFO [org.jboss.ha.httpsession.server.ClusteredHTTPSessionService] Creating
2003-02-20 12:40:09,489 INFO [org.jboss.ha.httpsession.server.ClusteredHTTPSessionService] Created
2003-02-20 12:40:09,490 INFO [org.jboss.ha.framework.server.FarmMemberService] Creating
2003-02-20 12:40:09,491 INFO [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Running
2003-02-20 12:40:09,493 INFO [org.jboss.ha.framework.server.FarmMemberService] Created
2003-02-20 12:40:09,496 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Creating
2003-02-20 12:40:09,550 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Created
2003-02-20 12:40:09,551 INFO [org.jboss.ha.jndi.HANamingService] Creating
2003-02-20 12:40:09,839 INFO [org.jboss.ha.jndi.HANamingService] Created
2003-02-20 12:40:09,841 INFO [org.jboss.invocation.jrmp.server.JRMPInvokerHA] created
2003-02-20 12:40:09,842 INFO [org.jboss.ha.framework.server.ClusterPartition] Starting
2003-02-20 12:40:09,843 INFO [org.jboss.ha.framework.server.ClusterPartition] Connecting to channel
2003-02-20 12:40:09,891 INFO [STDOUT]
-------------------------------------------------------
GMS: address is rayden:33089
-------------------------------------------------------
2003-02-20 12:40:11,992 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] New cluster view: 0 ([rayden:33089])
2003-02-20 12:40:11,995 INFO [org.jboss.ha.framework.server.ClusterPartition] Starting channel
2003-02-20 12:40:11,996 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Number of cluster members: 1
2003-02-20 12:40:11,996 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Other members: 0
2003-02-20 12:40:12,007 INFO [org.jboss.ha.framework.server.ClusterPartition] Started ClusterPartition: DefaultPartition
2003-02-20 12:40:12,008 INFO [org.jboss.ha.framework.server.ClusterPartition] Started
2003-02-20 12:40:12,258 INFO [org.jboss.ha.httpsession.server.ClusteredHTTPSessionService] Starting
2003-02-20 12:40:12,311 INFO [org.jboss.ha.httpsession.server.ClusteredHTTPSessionService] Started
2003-02-20 12:40:12,312 INFO [org.jboss.ha.framework.server.FarmMemberService] Starting
2003-02-20 12:40:12,357 INFO [org.jboss.ha.framework.server.FarmMemberService] Started
2003-02-20 12:40:12,358 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Starting
2003-02-20 12:40:12,358 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Started
2003-02-20 12:40:12,359 INFO [org.jboss.ha.jndi.HANamingService] Starting
2003-02-20 12:40:12,506 INFO [org.jboss.ha.jndi.HANamingService] Listening on 0.0.0.0/0.0.0.0:1100
2003-02-20 12:40:12,532 INFO [org.jboss.ha.jndi.HANamingService$AutomaticDiscovery] Listening on /0.0.0.0:1102, group=230.0.0.4
2003-02-20 12:40:12,534 INFO [org.jboss.ha.jndi.HANamingService] Started
2003-02-20 12:40:12,535 INFO [org.jboss.invocation.jrmp.server.JRMPInvokerHA] Starting
2003-02-20 12:40:12,547 INFO [org.jboss.invocation.jrmp.server.JRMPInvokerHA] Started
2003-02-20 12:40:12,548 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/usr/local/jboss-3.0.6_tomcat-4.1.18/server/default/deploy/cluster-service.xml

Subzero:
2003-02-20 12:33:46,671 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/usr/local/jboss-3.0.6_tomcat-4.1.18/server/default/deploy/cluster-service.xml
2003-02-20 12:33:46,789 INFO [org.jboss.ha.framework.server.ClusterPartition] Creating
2003-02-20 12:33:47,355 INFO [org.jboss.ha.framework.server.ClusterPartition] Set the JavaGroups logging to log4j with category:org.apache.log4j.Logger@37d490, priority: DEBUG, JavaGroupsLevel: 4
2003-02-20 12:33:47,480 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Initializing
2003-02-20 12:33:47,557 INFO [org.jboss.ha.framework.server.ClusterPartition] Created
2003-02-20 12:33:47,558 INFO [org.jboss.ha.framework.server.FarmMemberService] Creating
2003-02-20 12:33:47,559 INFO [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Running
2003-02-20 12:33:47,560 INFO [org.jboss.ha.framework.server.FarmMemberService] Created
2003-02-20 12:33:47,561 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Creating
2003-02-20 12:33:47,591 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Created
2003-02-20 12:33:47,592 INFO [org.jboss.ha.jndi.HANamingService] Creating
2003-02-20 12:33:47,786 INFO [org.jboss.ha.jndi.HANamingService] Created
2003-02-20 12:33:47,790 INFO [org.jboss.invocation.jrmp.server.JRMPInvokerHA] created
2003-02-20 12:33:47,790 INFO [org.jboss.ha.framework.server.ClusterPartition] Starting
2003-02-20 12:33:47,791 INFO [org.jboss.ha.framework.server.ClusterPartition] Connecting to channel
2003-02-20 12:33:47,822 INFO [STDOUT]
-------------------------------------------------------
GMS: address is subzero:33295
-------------------------------------------------------
2003-02-20 12:33:49,891 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] New cluster view: 0 ([subzero:33295])
2003-02-20 12:33:49,907 INFO [org.jboss.ha.framework.server.ClusterPartition] Starting channel
2003-02-20 12:33:49,908 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Number of cluster members: 1
2003-02-20 12:33:49,908 INFO [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Other members: 0
2003-02-20 12:33:49,914 INFO [org.jboss.ha.framework.server.ClusterPartition] Started ClusterPartition: DefaultPartition
2003-02-20 12:33:49,915 INFO [org.jboss.ha.framework.server.ClusterPartition] Started
2003-02-20 12:33:49,915 INFO [org.jboss.ha.framework.server.FarmMemberService] Starting
2003-02-20 12:33:49,958 INFO [org.jboss.ha.framework.server.FarmMemberService] Started
2003-02-20 12:33:49,959 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Starting
2003-02-20 12:33:49,959 INFO [org.jboss.ha.hasessionstate.server.HASessionStateService] Started
2003-02-20 12:33:49,960 INFO [org.jboss.ha.jndi.HANamingService] Starting
2003-02-20 12:33:50,077 INFO [org.jboss.ha.jndi.HANamingService] Listening on 0.0.0.0/0.0.0.0:1100
2003-02-20 12:33:50,087 INFO [org.jboss.ha.jndi.HANamingService$AutomaticDiscovery] Listening on /0.0.0.0:1102, group=230.0.0.4
2003-02-20 12:33:50,088 INFO [org.jboss.ha.jndi.HANamingService] Started
2003-02-20 12:33:50,089 INFO [org.jboss.invocation.jrmp.server.JRMPInvokerHA] Starting
2003-02-20 12:33:50,097 INFO [org.jboss.invocation.jrmp.server.JRMPInvokerHA] Started
2003-02-20 12:33:50,097 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/usr/local/jboss-3.0.6_tomcat-4.1.18/server/default/deploy/cluster-service.xml

I have tested that multicast works with the tool from javagroups so I am stuck. I have copied the javagroups-2.0.jar from the "all" lib to the "default" lib as well but still no go. Any idea?

Thanks,

Christian

1. Re: Clustering - Nodes don't pick each other up

belaban Feb 26, 2003 2:28 AM (in response to cessner)

1. How does your cluster-service.xml look like ?

2. Try to run org.javagroups.demos.Draw -props where is default.xml from the JavaGroups distribution. Run 2 instances. Both should show "2" in the title bar.

3. If #2 works, copy and modify the default.xml to cluster-service.xml

4. Else turn on full JavaGroups tracing (explained in the SourceForge docs section for JavaGroups).
Bela
Actions
2. Re: Clustering - Nodes don't pick each other up

belaban Feb 26, 2003 2:29 AM (in response to cessner)

and check whether your firewall is turned off (RH 8 includes a FW by default).
Bela
Actions
3. Re: Clustering - Nodes don't pick each other up

prpatel Feb 27, 2003 10:05 AM (in response to cessner)

Try running in the 'all' configuration first to see if the cluster nodes can find themselves.

./run.sh -c all

I suspect that you have forgotten to copy over some other needed JARs to the default config. Here are the JAR's I have in my default/lib directory. I am using JBoss 3.2.0RC2, BTW!

activation.jar
ant.jar
autonumber-plugin.jar
bcel.jar
bsh-core-1.2b7.jar
bsh-deployer.jar
counter-plugin.jar
hsqldb-plugin.jar
hsqldb.jar
javagroups-2.0.jar
javax.servlet.jar
jboss-common-jdbc-wrapper.jar
jboss-j2ee.jar
jboss-jaas.jar
jboss-jsr77.jar
jboss-management.jar
jboss-transaction.jar
jboss.jar
jbossha.jar
jbossmq.jar
jbossmx.jar
jbosssx.jar
jcert.jar
jmxri.jar
jmxtools.jar
jnet.jar
jnpserver.jar
jpl-pattern.jar
jpl-util.jar
jsse.jar
jts.jar
log4j.jar
mail-plugin.jar
mail.jar
properties-plugin.jar
scheduler-plugin-example.jar
scheduler-plugin.jar
tyrex.jar
xalan.jar
xml-apis.jar
Actions

Go to original post