Attempt to start up management daemon may throw an error.
Article ID: KB0091966
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Service Grid | - |
| Not Applicable | - |
Description
Resolution:
The error may be similar to the messages posted below:
- The discovery channel on udp://239.100.104.102:1965 could not join the multicast group on network interface "eth2" (Intel(R) PRO/Wireless 3945ABG Network Connection - Packet Scheduler Miniport).
java.net.SocketException: bad argument for IP_MULTICAST_IF2: No IP addresses bound to interface
- The discovery channel on udp:// 239.100.104.102:1965 joined all network interfaces; there were failures on network interfaces "eth2" (Intel(R) PRO/Wireless
3945ABG Network Connection - Packet Scheduler Miniport), "eth4" (Juniper Network Connect Virtual Adapter); you may want to change your discovery configuration from a wildcard to one or more configuration URI.
Above message is an indication that the default configuration tries to do discovery on all network interfaces, but for hardware it fails on the given network interface.
Changing the discovery host name in <tibco_home>\managementdaemon\2.0\config\configuration.xml
from default hostname to multicast on the default network interface
<list name="discoverySocketAddresses">
<string>udp://239.100.106.107:1965#*</string>
helps to avoid this error on the Management Daemon startup.
The error may be similar to the messages posted below:
- The discovery channel on udp://239.100.104.102:1965 could not join the multicast group on network interface "eth2" (Intel(R) PRO/Wireless 3945ABG Network Connection - Packet Scheduler Miniport).
java.net.SocketException: bad argument for IP_MULTICAST_IF2: No IP addresses bound to interface
- The discovery channel on udp:// 239.100.104.102:1965 joined all network interfaces; there were failures on network interfaces "eth2" (Intel(R) PRO/Wireless
3945ABG Network Connection - Packet Scheduler Miniport), "eth4" (Juniper Network Connect Virtual Adapter); you may want to change your discovery configuration from a wildcard to one or more configuration URI.
Above message is an indication that the default configuration tries to do discovery on all network interfaces, but for hardware it fails on the given network interface.
Changing the discovery host name in <tibco_home>\managementdaemon\2.0\config\configuration.xml
from default hostname to multicast on the default network interface
<list name="discoverySocketAddresses">
<string>udp://239.100.106.107:1965#*</string>
helps to avoid this error on the Management Daemon startup.
Issue/Introduction
Attempt to start up management daemon may throw an error.
Feedback
Yes
No
Powered by
