Edward Sutter created JGRP-1535:
-----------------------------------
Summary: SocketException WARN messages at startup
Key: JGRP-1535
URL:
https://issues.jboss.org/browse/JGRP-1535
Project: JGroups
Issue Type: Enhancement
Affects Versions: 3.2, 3.0.14
Reporter: Edward Sutter
Assignee: Bela Ban
Priority: Minor
We are seeing the following messages when starting our server nodes. From what I can tell
from the source, JGroups is attempting to attach to every detected network interface and
logs warning messages when an IP address is not found.
I'm not seeing any negative behavior from JGroups but the messages cause some alarm to
our administrators. Ideally JGroups would *not* log a message in the case where the
interface does not have an IP address associated with it. Alternatively, lowering the log
level to DEBUG could also work.
WARN [org.jgroups.protocols.TCP] failed to join /224.0.75.75:7500 on net3:
java.net.SocketException: Unrecognized Windows Sockets error: 0: no Inet4Address
associated with interface
WARN [org.jgroups.protocols.TCP] failed to join /224.0.75.75:7500 on net4:
java.net.SocketException: Unrecognized Windows Sockets error: 0: no Inet4Address
associated with interface
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira