WebSphere Management Process Discovery messages

ADMD0001E: The discovery MBean cannot be activated.
Explanation: Every ND process requires one discovery MBean.
User Response: 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/.

ADMD0002E: Only a multicast address is allowed to open the multicast socket
Explanation: Multicast group addresses are in the range of 224.0.0.0 through 239.255.255.255
User Response: 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.

ADMD0003E: The multicast socket cannot be opened to join multicast group: {0}
Explanation: Opening the multicast socket requires that the router has multicasting capability.
User Response: Consult the network administrator to make sure that the router supports multicasting.

ADMD0004E: The TCP socket: {0} cannot be opened.
Explanation: The TCP-based discovery needs to open a TCP socket before sending out discovery message.
User Response: Either the (remote) socket is not listening, or a network failure has occurred.

ADMD0005E: The User Datagram Protocol (UDP) socket: {0} cannot be opened.
Explanation: The UDP-based discovery needs to open a UDP socket before sending out discovery message.
User Response: Either the (remote) socket is not listening, or a network failure has occurred.

ADMD0006E: The destination endpoint is not specified
Explanation: The discovery needs to know the destination endpoint before sending out the discovery message.
User Response: Record and save the exception information in this message for further problem determination.

ADMD0007W: Unable to construct the discovery query message with exception: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0008W: Unable to construct the discovery response message with exception: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0009W: Unable to send out the discovery response message with exception: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0010E: Incorrect discovery endpoint address
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0011E: Unsupported transport protocol
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0012E: The transport of type: {0} cannot be initialized.
Explanation: The discovery service is built on top of a specific transport, i.e. UDP, TCP or Multicasting.
User Response: 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.

ADMD0013W: Invalid discovery message: No Source End Tag
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0014W: The multicast server cannot be initialized at port: {0}
Explanation: A failure occurred while initializing the transport that receives the multicast requests.
User Response: Verify that multicasting is supported in your local area network and that no port conflict exists.

ADMD0015W: The multicast group: {0} cannot be joined.
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.
User Response: Make sure that multicasting is supported in your local area network and that the right multicast group is specified for discovery

ADMD0016W: Unable to close the server socket with exception: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0017W: Datagram socket failure in receiving package: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0018E: The TCP transport cannot be initialized; exception: {0}
Explanation: The discovery fails to initialize the TCP transport to receive the incoming discovery message.
User Response: Check whether this is a port conflict

ADMD0019E: The UDP Transport cannot be initialized; exception: {0}
Explanation: The discovery fails to initialize the UDP transport to receive the incoming discovery message.
User Response: Check to see if a port conflict exists.

ADMD0020W: Tcp socket failure in receiving package: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0021W: Unalbe to handle discovery connection with exception: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0022W: Host "{0}" cannot be resolved while sending discovery messages.
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.
User Response: 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.

ADMD0023I: The system discovered process (name: {0}, type: {1}, pid: {2})
Explanation: This informational message indicates the system status.
User Response: No user action is required.

ADMD0024W: Failed to send out the discovery message to the process: {0}
Explanation: This exception is unexpected. The cause is not immediately known.
User Response: 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/.

ADMD0025W: In process discovery, the 127.0.0.1 IP address is used to advertise an endpoint. This usage might cause problems in a network environment.
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.
User Response: 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.

ADMD0026W: The version of the deployment manager ({0}) is earlier than that of this node ({1}).
Explanation: A deployment manager version that is earlier than that of a node is an unsupported configuration.
User Response: Upgrade the deployment manager to the same or later version as that of the node.