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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
