[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
This is from the wiki (http://www.jboss.org/wiki/Wiki.jsp?page=IPv6): Another source of problems might be the use of IPv6, and/or misconfiguration of /etc/hosts. If you communicate between an IPv4 and an IPv6 host, and they are not able to find each other, try the java.net.preferIP4Stack=true property. Change your /bin/run.sh from # Setup JBoss sepecific properties | JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME" to # Setup JBoss sepecific properties | JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true -Dprogram.name=$PROGNAME" JDK 1.4.1 uses IPv6 by default, although is has a dual stack, that is, it also supports IPv4. I tried this with JBoss 4.0.1sp1 on SuSE 9.1 prof. and the cluster configuration is starting without errors. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877303#3877303 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877303 --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
This is from the wiki (http://www.jboss.org/wiki/Wiki.jsp?page=IPv6): Another source of problems might be the use of IPv6, and/or misconfiguration of /etc/hosts. If you communicate between an IPv4 and an IPv6 host, and they are not able to find each other, try the java.net.preferIP4Stack=true property. Change your /bin/run.sh from # Setup JBoss sepecific properties | JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME" to # Setup JBoss sepecific properties | JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true -Dprogram.name=$PROGNAME" JDK 1.4.1 uses IPv6 by default, although is has a dual stack, that is, it also supports IPv4. I tried this with JBoss 4.0.1sp1 on SuSE 9.1 prof. and the cluster configuration is starting without errors. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877302#3877302 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877302 --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
I have updated the wiki, thanks: http://www.jboss.org/wiki/Wiki.jsp?page=IPv6 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874779#3874779 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874779 --- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
Thanks thebadpete, it worked! the error disappeared.. yea! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874742#3874742 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874742 --- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
Hi folks, There was an earlier post mentioning the same symtoms. Assuming that you are running JBoss on Linux, if your Linux kernel has IPv6 support, you will have this problem. If you don't need IPv6 support, you can disable it from the kernel and the problem will go away. For me, I disable it by adding the following in /etc/modprobe.conf: alias net-pf-10 off and reboot the Linux box. Don't ask me why, I just follow some websites. Works for me. Hope this helps! Pete View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874704#3874704 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874704 --- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
Okay, you can either - not set BindAddress in the XML file for HANamingService or - use jnp.disableMulticastDiscovery. BTW: using a 0.0.0.0 bind address seems to be fixed in CVS head: socket = new MulticastSocket (adGroupPort); if (bindAddress != null && bindAddress.isAnyLocalAddress() == false) socket.setInterface(bindAddress); socket.setTimeToLive(autoDiscoveryTTL); group = InetAddress.getByName (adGroupAddress); socket.joinGroup (group); View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874058#3874058 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874058 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
Thanks for the tip on disabling HAJNDI autodiscovery. Ok, I ran my server through the debugger watching both the JGroups multicast socket creation and the DetatchedHANamingService.AutoDiscovery multicast socket creation. The main difference is that in org.jgroups.protocols.UDP.createSockets(), mcast_recv_sock.setInterface(bind_addr) is passing in an real address on my machine. In DetatchedHANamingService.AutoDiscovery.start(), socket.setInterface(bindAddress) is passing 0.0.0.0. That call is throwing an exception thus logging the warning as seen above. I noticed these comments in org.jgroups.protocols.UDP: | // changed by bela Feb 12 2003: by default multicast sockets will be bound to all network interfaces | | // CHANGED *BACK* by bela March 13 2003: binding to all interfaces did not result in a correct | // local_addr. As a matter of fact, comparison between e.g. 0.0.0.0:1234 (on hostA) and | // 0.0.0.0:1.2.3.4 (on hostB) would fail ! | If I set a valid bind address for HAJNDI in cluster-service.xml, the warning disappears! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874028#3874028 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874028 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
Can you debug this ? Should be simple to find out. BTW: the JGroups code should do almost the same, so maybe you compare the 2 beasts. Note that you can turn multicast HA-JNDI discovery off by setting a system prop, afair jnp.multicastDiscovery=false. But hit the manual for the exact name. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873928#3873928 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873928 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
FWIW, I get the same error when starting the all configuration on Mac OS X 10.3.8, JBoss 3.2.7. I even tried changing the HAJNDI autodiscovery mcast address to the same address used in the JGroup config (different port of course), and still get the same error. I've pretty much ignored it, since I don't necessarily need HAJNDI autodiscovery. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873918#3873918 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873918 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
Odd, seems that JGroups is working, but the HA-JNDI service doesn't work (uses its own mcast socket). Can you try to run 2 instances of JGroups first to see whether this is a JGroups problem ? You'll need jgroups.jar, commons-logging.jar and concurrent.jar in your CLASSPATH. java org.jgroups.demos.Draw View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873858#3873858 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873858 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Clustering/JBoss] - Re: error on jboss start: b ad argument for IP_MULTICAST_IF:
I also get this error on a Suse 9.1 enterprise linux box running jboss 4.0 with tomcat 5.0 my routing table is the same as above (well, at least the multicast address). Do I need to recompile the kernel to add multicast? Which address needs to be bound the interface?... I noticed that the default was 230.0.0.4 in the code. Anybody have any ideas? I would LOVE to get clustering working. Thanks in advance! --Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873815#3873815 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873815 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
