WebSphere Management Process DiscoveryADMD0001E: Failed to activate the discovery mbean
Explanation
Every ND process should have one discovery mbean.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0002E: Only 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 in the serverindex.xml file to make sure the IP provided falls into the above range. Note there might be some multicast ip conflict in your local area network. Consult your LAN administrator
ADMD0003E: Can not open the multicast socket to join multicast group: {0}
Explanation
To open the multicast socket requires the router which has the multicasting capability
User Response:
Consult the network administrator to make sure the router supports mutlicasting.
ADMD0004E: Can not open the TCP socket: {0}
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 there is a network failure.
ADMD0005E: Can not open the UDP socket: {0}
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 there is a network failure.
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 is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0008W: Unable to construct the discovery response message with exception: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0009W: Unable to send out the discovery response message with exception: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0010E: Incorrect discovery endpoint address
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0011E: Unsupported transport protocol
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0012E: Unable to initialize the transport of type: {0}
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 is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0014W: Unable to initialize the multicast server at port: {0}
Explanation
Failure occurred while initializing the transport which receives the multicast requests
User Response:
Make sure that the multicasting is supported in your local area network and that there is no port conflict
ADMD0015W: Unable to join the multicast group: {0}
Explanation
Certain type of discovery requires the multicasting support. Either no multicasting is supported with local area network or the target multicast group rejects join request
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 is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0017W: Datagram socket failure in receiving package: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0018E: Unable to initialize TcpTransport with exception: {0}
Explanation
The discovery fails to initialize the TCP transport in order to receive the incoming discovery message
User Response:
Check whether this is a port conflict
ADMD0019E: Unable to initialize UdpTransport with exception: {0}
Explanation
The discovery fails to initialize the UDP transport in order to receive the incoming discovery message
User Response:
Check whether this is a port conflict
ADMD0020W: Tcp socket failure in receiving package: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0021W: Unalbe to handle discovery connection with exception: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0022W: Unable to resolve host "{0}" while sending discovery messages
Explanation
The host in question can not be resolved from DNS server. There are a few possibilities: the host to be resolved may not exist, or runs on DHCP machine, or it has a short hostname which can not be resolved without appending an appropriate DNS suffix, or some other causes.
User Response:
Check whether the host to be resolved does exist in the network or runs on DHCP machine. Also if it is a short host name, check the default DNS suffix in the local machine where discovery occurs.
ADMD0023I: Process discovered (name: {0}, type: {1}, pid: {2})
Explanation
None
User Response:
None
ADMD0024W: Failed to send out the discovery message to the process: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMD0025W: In process discovery, the IP address 127.0.0.1 is used to advertize an endpoint. This may cause problems in a networked environment.
Explanation
IP address 127.0.0.1, or "localhost", is known as the "loopback" IP address which is only valid in a standalone environment. Over the network no hosts can be recognized by others through this IP address.
User Response:
Verify that the host address and DNS configurations are set correctly. For Linux configurations, configure the /etc/nsswitch.conf file to search DNS before the /etc/hosts file.