Bugs item #583139, was opened at 2002-07-17 16:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=583139&group_id=22866
Category: Clustering Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Ulrich Romahn (diggermaus) Assigned to: Nobody/Anonymous (nobody) Summary: clustering issue with Linux and Windows Initial Comment: When starting an instance of JBoss 3.0.0 on either Linux or Win2k, it does not joind the default cluster partition of another JBoss 3.0.0 instance that has already been started on another Linux server. It works, however, between two JBoss instances started on two Windows boxes (Win2k and/or WinME). My test configuration was: SuSE Linux 7.3 (with latest patches) Windows 2000 Server SP2 Windows ME (with latest patches) LAN with multicast enabled (verified!) Sun JDK1.3.1_03 on Linux Sun JDK1.4.0 and 1.3.1_02 on Windows (both tested) How to reproduce: Start one JBoss instance on a SuSE 7.3 Start a second JBoss instance on either Win2k or another SuSE 7.3 Identified issue: 1. There must be an issue with the javagroups-2.0.jar that is bundeled with the current JBoss3.0.0 download package from May 31st. If I get the latest javagroups source from CVS, compile it and replace the 'old' jar with the newly compiled, everything seems to be OK and working in any configuration/combination ... except, 2. when running on Linux, a paramter "bind_addr" should be used to use 'eth0' instead of 'lo' in my case. When I initially installed Linux, I didn't have an active network connection. In this case, only 'lo' got activated on Linux and this will be the first network interface. Now, javagroups seems to always try to bind to this 'first' interface, 'lo' in my case. As a result, no multicast were send to the network :(. So, I added the following parameters to my 'cluster-service.xml' to make it work: <mbean code="org.jboss.ha.framework.server.ClusterPartition" name="jboss:service=DefaultPartition"> <attribute name="PartitionProperties"> UDP(mcast_addr=228.8.8.8;mcast_port=45566;bind_addr=<ip-addr-of-your-if>;ip_ttl=32;mcast_send_buf_size=32000;mcast_recv_buf_size=64000):PING(timeout=2000;num_initial_members=3):MERGE2(min_interval=5000;max_interval=10000):FD:VERIFY_SUSPECT(timeout=1500):pbcast.STABLE(desired_avg_gossip=20000):pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800):UNICAST(timeout=1200):FRAG(down_thread=false;up_thread=false):pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;shun=false;print_local_addr=true) </attribute> </mbean> Please note that these are the exact default protocol parameters as given in JBoss' "ClusterPartition.java", except for the additional paramter 'bind_addr='. After making these changes, everything works, i.e. two JBoss instances on the same LAN join the cluster, regardless of OS and JDK version. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=583139&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
