[JBoss-user] [Clustering/JBoss] - Re: clustering problems - nodes fail to cluster
Turns out the problem was a switch issue. What made this especially hard to figure out is that org.jgroups.demos.ViewDemo shows the machines clustering correctly. Fortunately, org.jgroups.tests.McastReceiverTest and org.jgroups.tests.McastSenderTest failed, which led me to investigate the switch settings. I can now get the machines to cluster successfully in jboss 3.2.5, but they fail to cluster in 3.2.7. We'll launch with 3.2.5 for now.Perhaps removing "-b 0.0.0.0" will fix it for 3.2.7? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887818#3887818 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887818 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: clustering problems - nodes fail to cluster
// I start jboss with "run.sh -b 0.0.0.0 -c all". Lose the -b 0.0.0.0 option View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887206#3887206 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887206 --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: clustering problems - nodes fail to cluster
I've tried starting jboss separately, and that doesn't help. I did just discover the following: the org.jgroups.tests.McastReceiverTest fails, even though the ViewDemo app succeeds: bs-desktop% java -cp ".:../server/all/lib/jgroups.jar:../server/all/lib/commons-logging.jar" org.jgroups.tests.McastReceiverTest -mcast_addr 224.1.2.3 -port -bind_addr bs-desktop Socket=0.0.0.0/0.0.0.0:, bind interface=/192.168.253.47 bs-laptop% java -cp ".:../server/all/lib/jgroups.jar:../server/all/lib/commons-logging.jar" org.jgroups.tests.McastSenderTest -mcast_addr 224.1.2.3 -port -ttl 32 -bind_addr bs-laptop Socket=0.0.0.0/0.0.0.0:, ttl=32, bind interface=/192.168.253.46 > asdasd > sadasdlk However, ViewDemo still connects! bs-desktop% java -cp ".:../server/all/lib/jgroups.jar:../server/all/lib/commons-logging.jar" org.jgroups.demos.ViewDemo --- GMS: address is bs:34936 --- ** New view: [bs:34936|0] [bs:34936] ** New view: [bs:34936|1] [bs:34936, bs-laptop:32807] bs-laptop% java -cp ".:../server/all/lib/jgroups.jar:../server/all/lib/commons-logging.jar" org.jgroups.demos.ViewDemo --- GMS: address is bs:32807 --- ** New view: [bs-desktop:34936|1] [bs-desktop:34936, bs:32807] Could this be a kernel or interface configuration issue? The interfaces read: bs-desktop% ifconfig eth1 Link encap:Ethernet HWaddr 00:11:D8:43:FB:F6 inet addr:192.168.253.47 Bcast:192.168.253.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:817279 errors:0 dropped:0 overruns:0 frame:0 TX packets:590413 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:702380963 (669.8 Mb) TX bytes:90165930 (85.9 Mb) Interrupt:17 Memory:fba0-0 bs-laptop% ifconfig eth0 Link encap:Ethernet HWaddr 00:0F:1F:16:26:6E inet addr:192.168.253.46 Bcast:192.168.253.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:504162 errors:0 dropped:0 overruns:0 frame:0 TX packets:192885 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:442423866 (421.9 Mb) TX bytes:20610308 (19.6 Mb) Interrupt:11 Both machines are running gentoo, with 2.6.11 kernels. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886916#3886916 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886916 --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: clustering problems - nodes fail to cluster
Are you starting JBoss on both boxes at close to the same time? Previous versions of JGroups could sometimes run into problems if this is the case. Try shutting down both JBoss instances, then start one, wait until it starts completely, then start the other. See if this makes any difference. Depending on which version of JGroups you downloaded to attempt to use the ViewDemo, that version may contain the resolution to this issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886911#3886911 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886911 --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
