WebSphere Management Connector Subsystem messages |
ADMC0001E: Unable to serialize object: {0}
Explanation:
The object needs to implement the java.io.Serializable class to be marshalled.
User Response:
Check your class definition and verify that all classes being passed implement the Serializable class.
ADMC0002E: The system failed to initialize the SOAP connector with the exception: {0}
Explanation:
The administrative run time cannot bring up the SOAP (Simple Object Access Protocol) connector. Generally this error occurs because of a port conflict.
User Response:
Verify that you do not have two configurations specifying the same port.
ADMC0005E: A SOAP URI violation occurred. The correct URI is uri:AdminService.
Explanation:
The SOAP (Simple Object Access Protocol) connector defines its own URI (Uniform Resource Identifier) for SOAP calls, uri:AdminService. This error occurs only when the SOAP call is not made through the SOAP administrative client provided by IBM.
User Response:
Connect through the AdminClient, the only supported mechanism for connecting to the AdminService from a separate process.
ADMC0006E: No port is specified for the SOAP connector.
Explanation:
The SOAP (Simple Object Access Protocol) connector must listen to one specific port.
User Response:
Edit the serverindex.xml file and add a named endpoint for the SOAP connector.
ADMC0007E: An unknown error occurs while invoking the AdminService methods.
Explanation:
The MBean methods are either not defined or are not accessible because of security issues.
User Response:
Check the MBean definition and the Java 2 security permission granted to the MBean class.
ADMC0008E: The system failed to marshall the object of type {0}: {1}
Explanation:
The SOAP (Simple Object Access Protocol) connector fails to marshall some Java object, which probably does not implement the java.io.Serializable interface.
User Response:
Check the definition of the problem Java class.
ADMC0009E: The system failed to make the SOAP RPC call: {0}
Explanation:
This generic exception indicates that the SOAP (Simple Object Access Protocol) RPC (remote procedure call) failed. Either the remote process is not reachable, or there is a marshalling problem.
User Response:
Verify that the remote process is reachable and that the SOAP connector is running on the remote process.
ADMC0011E: The SOAP remote procedure call (RPC) cannot be unmarshalled.
Explanation:
The SOAP (Simple Object Access Protocol) connector fails to extract the SOAP Call object from a received SOAP message; some other general exceptions have occurred.
User Response:
Check the SystemOut.log file and the First Failure Data Capture (FFDC) log to find the most relevant root cause.
ADMC0013I: The SOAP connector is available at port {0}
Explanation:
This informational message indicates the availability of the SOAP (Simple Object Access Protocol) connector.
User Response:
No action is required.
ADMC0014E: A failure occurred starting connector {0}.
Explanation:
The AdminService cannot start the JMX (Java Management Extensions) connector with the specified type.
User Response:
Check the SystemOut.log file and the First Failure Data Capture (FFDC) log to find the most relevant root cause for this connector error.
ADMC0015W: The SOAP connector failed to start with exception: {0}.
Explanation:
The AdminService cannot start the SOAP connector because of the stated exception.
User Response:
Examine the exception in this message for problem determination.
ADMC0016E: The system cannot create a SOAP connector to connect to host {0} at port {1}.
Explanation:
In most cases, the wrong host and port have been provided. If the remote process runs in secure mode, an appropriate userID and password are required.
User Response:
Verify that the correct data is provided to create a SOAP connector.
ADMC0017E: Could not create an RMI connector to connect to host {0} at port {1}
Explanation:
In most cases, the wrong host and port have been provided. If the remote process runs in secure mode, an appropriate userID and password are required.
User Response:
Verify that the correct data is provided to create an RMI connector.
ADMC0018E: the system is unable to get the valid bootstrap port.
Explanation:
The RMI connector needs to obtain the bootstrap port as part of its initialization properties.
User Response:
Check the serverindex.xml file for the current node and verify that the BOOTSTRAP_ADDRESS endpoint is specified for this server.
ADMC0019E: No Secure Sockets Layer (SSL) configuration is specified for the secure SOAP connector.
Explanation:
When security is enabled, the SOAP connector needs to obtain the SSL configuration to intialize the SSL server socket.
User Response:
Check the server.xml file and verify that a property named sslConfig exists, which points to an entry in the security.xml file.
ADMC0020E: The system failed to initialize the Java Remote Method Invocation (RMI) connector with the exception: {0}
Explanation:
The administration run time cannot bring up the RMI (Java Remote Method Invocation) connector because of the displayed exception; the naming service must be running to use the RMI connector.
User Response:
Examine the displayed exception and check whether the naming service is up and running.
ADMC0021W: The RMI connector failed to start with NamingException: {0}
Explanation:
The RMI (Java Remote Method Invocation) connector failed to create an InitialContext and bind itself to the name space.
User Response:
Verify that the naming service is running.
ADMC0022W: The RMI connector start failed with RemoteException: {0}
Explanation:
A problem occurred attempting to start the RMI (Java Remote Method Invocation) connector.
User Response:
Examine the displayed exception for more details.
ADMC0023W: The RMI connector stop failed with NamingException: {0}
Explanation:
A problem occurred attempting to stop the RMI (Java Remote Method Invocation) connector.
User Response:
Examine the displayed exception for more details.
ADMC0026I: The RMI Connector is available at port {0}
Explanation:
This informational message indicates the availability of the RMI (Java Remote Method Invocation) connector.
User Response:
No action is required.
ADMC0027I: The Tivoli HTTPAdapter is available on port {0}
Explanation:
This informational message indicates the availability of the Tivoli HTTPAdapter.
User Response:
No action is required.
ADMC0028W: Error starting the Tivoli HTTPAdapter: {0}
Explanation:
A problem occurred attempting to start the HTTP adapter.
User Response:
Examine the displayed exception for more details.
ADMC0029E: Unable to initialize the discovery adapter for the deployment manager: {0}
Explanation:
The deployment manager process failed to initialize the discovery service.
User Response:
Examine the serverindex.xml file to check the port number defined for deployment manager discovery. Verify that there is no port conflict.
ADMC0030E: Unable to initialize the discovery adapter for the node agent: {0}
Explanation:
The NodeAgent process failed to initialize the discovery service.
User Response:
Open the serverindex.xml file to check the CELL_DISCOVERY_ADDRESS port number; make sure there is no port conflict.
ADMC0031E: The system is unable to initialize the discovery adapter for the managed process: {0}
Explanation:
The ManagedProcess failed to initialize the discovery service.
User Response:
Open the serverindex.xml file to check the CELL_DISCOVERY_ADDRESS port number; make sure there is no port conflict.
ADMC0032W: The incoming request does not have valid credentials.
Explanation:
The credential cannot be found in the SOAP (Simple Object Access Protocol) header.
User Response:
Provide a userID and password or set the thread credential before creating a SOAP client.
ADMC0034W: The system cannot obtain WSSecurityContext.
Explanation:
Generally, this problem is caused by a SOAP (Simple Object Access Protocol) connector and SWAM (Simple WebSphere Authentication Mechanism) combination that is not supported in the ND environment.
User Response:
Do not use SWAM with the SOAP connector.
ADMC0035E: No user name has been specified to create a secure SOAP administrative client.
Explanation:
The user name is a required attribute for the secure administrative client.
User Response:
Specify the username either in the properties file or through parameters passed to the AdminClientFactory.
ADMC0036E: No password has been specified to create a secure SOAP administrative client.
Explanation:
The password is a required attribute for the secure administrative client.
User Response:
Specify the password either in the properties file or through parameters passed to the AdminClientFactory.
ADMC0037W: No truststore file has been specified to create a secure SOAP administrative client.
Explanation:
In most cases, the truststore file is a required attribute for the secure administrative client.
User Response:
Specify the truststore file either in the properties file or through parameters passed to the AdminClientFactory.
ADMC0038W: No keystore file has been specified to create a secure SOAP administrative client.
Explanation:
The keystore file might be a required attribute for client certificate authentication.
User Response:
Specify the keystore file either in the properties file or through parameters passed to the AdminClientFactory.
ADMC0040I: Tivoli HTTPAdapter is disabled in the secure mode.
Explanation:
As a simple JMX (Java Management Extensions) adapter, the Tivoli HTTP adapter is not protected by WebSphere security. To avoid a security exposure, the JMX adapter is intentionally disabled if security is enabled.
User Response:
No action is required.
ADMC0041E: The SOAP connector host name is not specified.
Explanation:
The host name is a required property for creating the SOAP (Simple Object Access Protocol) connector.
User Response:
Verify that a host name is provided. The property key for the host name is AdminClient.CONNECTOR_HOST.
ADMC0042E: A SOAP connector port number is not specified.
Explanation:
The port is a required property for creating a SOAP (Simple Object Access Protocol) connector.
User Response:
Verify that a port number is provided. The property key for port is AdminClient.CONNECTOR_PORT.
ADMC0043E: An error occurred while deserializing the received exception.
Explanation:
The SOAP (Simple Object Access Protocol) administrative client failed to restore the exception object from the received SOAP response message.
User Response:
Verify that the exception class is in the client side class path.
ADMC0044E: The system encountered an unsupported AdminClient operation: {0}
Explanation:
This exception can occur if an unsupported AdminClient operation called the SOAP connector.
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/.
ADMC0045E: The system is unable to create a SOAP header to carry the security attributes.
Explanation:
A SOAP (Simple Object Access Protocol) connector calls the DOM (Document Object Model) API to create a SOAP header.
User Response:
Verify that the XML parsing engine is functioning.
ADMC0046W: The system failed to load properties from com.ibm.SOAP.configURL: {0}
Explanation:
The AdminClientFactory loads the file as specified by com.ibm.SOAP.configURL to get some security related data.
User Response:
If com.ibm.SOAP.configURL is specified through the Java system property (-Dcom.ibm.SOAP.configURL), make sure the file to which it points exists in the file system.
ADMC0047W: Lost connection to the node agent at node "{0}". The routing table is updated to remove the entry for this node.
Explanation:
The deployment manager contacts each discovered node agent at fixed intervals. The lost connection can result from a network connectivity failure or a stopped node agent.
User Response:
If the node agent is not intentionally stopped, make sure the network is up; for instance, try performing a ping
ADMC0048I: The system established the connection to a previously disconnected node agent at node {0}.
Explanation:
The deployment manager keeps pinging each previously disconnected node agent at fixed intervals. Normally the connection can be reestablished if the network failure is recovered.
User Response:
No action is required.
ADMC0049E: The deployment manager failed to ping the node agent at node "{0}" because of a null administrative client. The ping thread is terminated.
Explanation:
The deployment manager failed to obtain a valid administrative client from the node agent when the node was discovered. There is no way to ping the node agent.
User Response:
Verify that all the JMX connectors are running inside the targeted node agent when the node agent starts. Check the SystemOut.log file for this node agent process.
ADMC0050E: Exception occurred while reading the node discovery protocol.
Explanation:
The administrative run time failed to obtain the node discovery protocol.
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/.
ADMC0051W: Failed to do a multicast-based process discovery; trying MBean discovery instead...
Explanation:
This error occurs either because the environment consists of a stand-alone machine, or because multicast is malfuctioning or not supported in the local network.
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/.
ADMC0052W: 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/.
ADMC0053E: The system cannot create a SOAP connector to connect to host {0} at port {1} with SOAP connector security enabled.
Explanation:
In most cases, the wrong host and port have been provided. If the remote process runs in secure mode, appropriate userID and password are required.
User Response:
Verify that the correct data is provided to create a SOAP connector. Supply a username and password in a soap.client.props file or at the command line.
ADMC0054E: You have set the security policy to use only FIPS approved cryptographic algorithms; however, the JSSE provider in this SSL configuration may not be FIPS approved. Make any necessary modifications.
Explanation:
The JSSE (Java Secure Socket Extension) provider must support FIPS (the Federal Information Processing Standard) on both the client and server.
User Response:
Verify that the server is configured for FIPS support. Verify that the JSSE provider on the client supports FIPS.