-
-
2. Re: setsockopt IP_ADD_MEMBERSHIP failed
i found out that the 2 box run on diffrennt version of linux. I formatted one of our dev server and load same os as the other dev server using redhat9. I also upgraded j2sdk1.4.0 to j2sdk1.4.2_05. When i started the two box it seems that they can find each other usign the default cluster-service.xml.
2004-09-10 13:46:20,230 INFO [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Initializing 2004-09-10 13:46:20,278 DEBUG [DefaultPartition:ReplicantManager] registerRPCHandler 2004-09-10 13:46:20,279 DEBUG [DefaultPartition:ReplicantManager] subscribeToStateTransferEvents 2004-09-10 13:46:20,279 DEBUG [DefaultPartition:ReplicantManager] registerMembershipListener 2004-09-10 13:46:24,016 INFO [org.jboss.ha.framework.server.ClusterPartition] Starting channel 2004-09-10 13:46:24,017 INFO [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Number of cluster members: 1 2004-09-10 13:46:24,017 INFO [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Other members: 0 2004-09-10 13:46:32,033 INFO [org.jboss.ha.framework.server.ClusterPartition] Started ClusterPartition: DefaultPartition
I also disable iptables on both box, and addedroute add -net 224.0.0.0 netmask 240.0.0.0 dev eth0
but same thing happend. I modifed the cluster-service.xml usng TCPPING but same thing too.. did i miss something here<?xml version="1.0" encoding="UTF-8"?> <server> <classpath codebase="lib" archives="jbossha.jar"/> <!-- ==================================================================== --> <!-- Cluster Partition: defines cluster --> <!-- ==================================================================== --> <mbean code="org.jboss.ha.framework.server.ClusterPartition" name="jboss:service=DefaultPartition"> <!-- Name of the partition being built --> <attribute name="PartitionName">DefaultPartition</attribute> <!-- Determine if deadlock detection is enabled --> <attribute name="DeadlockDetection">False</attribute> <!-- The JGroups protocol configuration --> <attribute name="PartitionConfig"> <Config> <TCP start_port="7800"/> <TCPPING initial_hosts="192.168.40.55[7800],192.168.40.54[7800]" up_thread="true" down_thread="true" num_initial_members="2" port_range="5" timeout="3000"/> <VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false"/> <pbcast.NAKACK gc_lag="100" retransmit_timeout="3000" up_thread="true" down_thread="true"/> <pbcast.STABLE desired_avg_gossip="20000" up_thread="false" down_thread="false"/> <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="false" print_local_addr="false" up_thread="true" down_thread="true"/> </Config> </attribute> </mbean> <!-- ==================================================================== --> <!-- HA Session State Service for SFSB --> <!-- ==================================================================== --> <mbean code="org.jboss.ha.hasessionstate.server.HASessionStateService" name="jboss:service=HASessionState"> <depends>jboss:service=DefaultPartition</depends> <!-- Name of the partition to which the service is linked --> <attribute name="PartitionName">DefaultPartition</attribute> <!-- JNDI name under which the service is bound --> <attribute name="JndiName">/HASessionState/Default</attribute> <!-- Max delay before cleaning unreclaimed state. Defaults to 30*60*1000 => 30 minutes --> <attribute name="BeanCleaningDelay">0</attribute> </mbean> <!-- ==================================================================== --> <!-- HA JNDI --> <!-- ==================================================================== --> <mbean code="org.jboss.ha.jndi.HANamingService" name="jboss:service=HAJNDI"> <depends>jboss:service=DefaultPartition</depends> <!-- Name of the partition to which the service is linked --> <attribute name="PartitionName">DefaultPartition</attribute> <!-- bind address of HA JNDI RMI endpoint --> <attribute name="BindAddress">${jboss.bind.address}</attribute> <!-- RmiPort to be used by the HA-JNDI service once bound. 0 => auto. --> <attribute name="RmiPort">0</attribute> <!-- Port on which the HA-JNDI stub is made available --> <attribute name="Port">1100</attribute> <!-- Backlog to be used for client-server RMI invocations during JNDI queries --> <attribute name="Backlog">50</attribute> <!-- Multicast Address and Group used for auto-discovery --> <!-- Uncomment AutoDiscovery attributes for auto-discovery --> <attribute name="AutoDiscoveryAddress">230.0.0.4</attribute> <attribute name="AutoDiscoveryGroup">1102</attribute> <!-- IP Address to which should be bound: the Port, the RmiPort and the AutoDiscovery multicast socket. --> <!-- Client socket factory to be used for client-server RMI invocations during JNDI queries --> <!--attribute name="ClientSocketFactory">custom</attribute--> <!-- Server socket factory to be used for client-server RMI invocations during JNDI queries --> <!--attribute name="ServerSocketFactory">custom</attribute--> </mbean> <mbean code="org.jboss.invocation.jrmp.server.JRMPInvokerHA" name="jboss:service=invoker,type=jrmpha"> <attribute name="ServerAddress">${jboss.bind.address}</attribute> <!-- <attribute name="RMIObjectPort">0</attribute> <attribute name="RMIClientSocketFactory">custom</attribute> <attribute name="RMIServerSocketFactory">custom</attribute> --> </mbean> <!-- ==================================================================== --> <!-- Distributed cache invalidation --> <!-- ==================================================================== --> <mbean code="org.jboss.cache.invalidation.bridges.JGCacheInvalidationBridge" name="jboss.cache:service=InvalidationBridge,type=JavaGroups"> <depends>jboss:service=DefaultPartition</depends> <depends>jboss.cache:service=InvalidationManager</depends> <attribute name="InvalidationManager">jboss.cache:service=InvalidationManager</attribute> <attribute name="PartitionName">DefaultPartition</attribute> <attribute name="BridgeName">DefaultJGBridge</attribute> </mbean> </server> -
3. Re: setsockopt IP_ADD_MEMBERSHIP failed
If you run a *TCP* based configuration, you will *not* see this problem. At least not in JChannel, but HAJNDI uses multicast as well.
Bela -
4. Re: setsockopt IP_ADD_MEMBERSHIP failed
okay. i switch over to the default cluster-service.xml and restarted node1 and node2 after node1 finishes booting up. But sitll they cant see each other. and also added bind_addr=<IP of node2>
node1[root@U1 deploy]# netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.40.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 224.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 eth0 0.0.0.0 192.168.40.1 0.0.0.0 UG 0 0 0 eth0 eth0 Link encap:Ethernet HWaddr 00:06:5B:6D:19:A1 inet addr:192.168.40.55 Bcast:192.168.40.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3753 errors:0 dropped:0 overruns:1 frame:0 TX packets:674 errors:0 dropped:0 overruns:0 carrier:0 collisions:1 txqueuelen:100 RX bytes:324079 (316.4 Kb) TX bytes:122475 (119.6 Kb) Interrupt:11 Base address:0xec80 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:137 errors:0 dropped:0 overruns:0 frame:0 TX packets:137 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:21136 (20.6 Kb) TX bytes:21136 (20.6 Kb)
node2Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.40.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 224.0.0.0 0.0.0.0 224.0.0.0 U 0 0 0 eth0 0.0.0.0 192.168.40.1 0.0.0.0 UG 0 0 0 eth0 [root@U1 deploy]# /sbin/ifconfig -a eth0 Link encap:Ethernet HWaddr 00:B0:D0:B0:5C:32 inet addr:192.168.40.54 Bcast:192.168.40.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2891 errors:0 dropped:0 overruns:0 frame:0 TX packets:1582 errors:0 dropped:0 overruns:0 carrier:0 collisions:26 txqueuelen:100 RX bytes:228352 (223.0 Kb) TX bytes:294965 (288.0 Kb) Interrupt:11 Base address:0xecc0 Memory:fe2ff000-fe2ff038 eth1 Link encap:Ethernet HWaddr 00:B0:D0:B0:5C:33 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Base address:0xec80 Memory:fe2fe000-fe2fe038 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:203 errors:0 dropped:0 overruns:0 frame:0 TX packets:203 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:33599 (32.8 Kb) TX bytes:33599 (32.8 Kb)