Explanation | Every ND process requires one discovery MBean. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Multicast group addresses are in the range of 224.0.0.0 through 239.255.255.255 |
Action | Check the multicast IP address in the serverindex.xml file to verify that the IP address provided is in the valid range. Some multicast IP conflicts might exist in your network. Consult your network administrator. |
Explanation | Opening the multicast socket requires that the router has multicasting capability. |
Action | Consult the network administrator to make sure that the router supports multicasting. |
Explanation | The TCP-based discovery needs to open a TCP socket before sending out discovery message. |
Action | Either the (remote) socket is not listening, or a network failure has occurred. |
Explanation | The UDP-based discovery needs to open a UDP socket before sending out discovery message. |
Action | Either the (remote) socket is not listening, or a network failure has occurred. |
Explanation | The discovery needs to know the destination endpoint before sending out the discovery message. |
Action | Record and save the exception information in this message for further problem determination. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The discovery service is built on top of a specific transport, i.e. UDP, TCP or Multicasting. |
Action | Check the serverindex.xml file to make sure there is no port conflict with the discovery port in your local system. For multicasting discovery, make sure your LAN router supports the multicasting. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A failure occurred while initializing the transport that receives the multicast requests. |
Action | Verify that multicasting is supported in your local area network and that no port conflict exists. |
Explanation | A certain type of discovery requires multicasting support. Either multicasting is not supported within the local area network, or the target multicast group rejects join requests. |
Action | Make sure that multicasting is supported in your local area network and that the right multicast group is specified for discovery |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The discovery fails to initialize the TCP transport to receive the incoming discovery message. |
Action | Check whether this is a port conflict |
Explanation | The discovery fails to initialize the UDP transport to receive the incoming discovery message. |
Action | Check to see if a port conflict exists. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The host in question cannot be resolved from the domain name server (DNS). Several causes are possible: the host to resolve might not exist, or runs on a Dynamic Host Configuration Protocol (DHCP) machine, or has a short host name that cannot be resolved without appending an appropriate DNS suffix. |
Action | Check whether the host to resolve does exist in the network or runs on a DHCP machine. If it has a short host name, check the default DNS suffix in the local machine where discovery occurs. |
Explanation | This informational message indicates the system status. |
Action | No user action is required. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The 127.0.0.1 IP address, or local host, is known as the loopback IP address, which is only valid in a stand-alone environment. Hosts cannot be recognized by others through this IP address over the network. |
Action | Verify that the host address and the domain name server configurations are set correctly. For Linux configurations, configure the /etc/nsswitch.conf file to search the DNS before the /etc/hosts file. |
Explanation | A deployment manager version that is earlier than that of a node is an unsupported configuration. |
Action | Upgrade the deployment manager to the same or later version as that of the node. |