WebSphere Management Connector SubsystemADMC0001E: Unable to serialize object: {0}
Explanation
The object needs to implement java.io.Serializable in order to be marshalled.
User Response:
Check your class definition and insure that all classes being passed implement Serializable
ADMC0002E: Failed to initialize SOAP connector with the exception: {0}
Explanation
The admin runtime cannot bring up the SOAP connector, generally because of a port conflict
User Response:
Verify that you do not have 2 configurations specifying the same port
ADMC0005E: SOAP URI violation, the correct URI should should be uri:AdminService
Explanation
The SOAP connector defines its own URI for SOAP calls which is uri:AdminService. This occurs only when the SOAP call is not made through the SOAP admin client provided by IBM
User Response:
The AdminClient is the only supported mechanism for connecting to the AdminService from a separate process.
ADMC0006E: No port specified for SOAP connector
Explanation
SOAP connector must listen to one specific port
User Response:
Edit serverindex.xml file and add a named Endpoint for SOAP connector
ADMC0007E: Unknown error occurs while invoking AdminService methods
Explanation
MBean methods are either not defined or not accessiable due to security
User Response:
Check the MBean definition and Java 2 security permission granted to the MBean class.
ADMC0008E: Failed to marshall the object of type {0}: {1}
Explanation
SOAP connector fails to marshall some Java object which probabaly doesn't implement java.io.Serializable interface
User Response:
Check the definition of the problem Java class.
ADMC0009E: Failed to make the SOAP RPC call: {0}
Explanation
A generic exception showing the SOAP RPC failed. Either the remote process is not reachable or there is a marshalling problem.
User Response:
Make sure the remote process is reachable and the SOAP connector is running on the remote process.
ADMC0011E: SOAP RPC call can not be unmarshalled
Explanation
The SOAP connector fails to extract the SOAP Call object from received SOAP message; generally some other exceptions have occurred
User Response:
Check the SystemOut.log and/or FFDC log to find the most relevant root cause.
ADMC0013I: SOAP connector available at port {0}
Explanation
None
User Response:
None
ADMC0014E: Failure starting connector {0}
Explanation
The AdminService can not start the JMX connector of type as specified.
User Response:
Check the SystemOut.log and/or FFDC log to find the most relevant root cause for the specified connector
ADMC0015W: SOAP connector failed to start with exception: {0}
Explanation
The AdminService cannot start the SOAP connector due to given exception
User Response:
Examine the exception in this message for further problem determination.
ADMC0016E: Could not create SOAP Connector to connect to host {0} at port {1}
Explanation
In most cases, the wrong host and port are provided. If the remote process runs in secure mode, appropriate user and password are required
User Response:
Make sure the correct data is provided to create a SOAP connector.
ADMC0017E: Could not create RMI Connector to connect to host {0} at port {1}
Explanation
In most cases, the wrong host and port are provided. If the remote process runs in secure mode, appropriate user and password are required
User Response:
Make sure the correct data is provided to create a RMI connector.
ADMC0018E: Unable to get the valid bootstrap port
Explanation
The RMI connector needs to obtain the bootstrap port as part of its initialization properites
User Response:
Check the serverindex.xml file for the current node and ensure the BOOTSTRAP_ADDRESS endpoint is specified for this server
ADMC0019E: No SSL config specified for the secure SOAP connector
Explanation
With security enabled, the SOAP connector needs to obtain the SSL config in order to intialize the SSL server socket
User Response:
Check the server.xml file and ensure there is a property named sslConfig which points to an entry in the security.xml
ADMC0020E: Failed to initialize the RMI Connector with the exception: {0}
Explanation
The admin runtime can not bring up the RMI 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 connector failed to start with NamingException: {0}
Explanation
The RMI connector failed to create an InitialContext and bind itself to the name space
User Response:
Make sure the naming service is running
ADMC0022W: RMI connector start failed with RemoteException: {0}
Explanation
A problem occurred attempting to start the RMI connector.
User Response:
Examine the displayed exception for more details.
ADMC0023W: RMI connector stop failed with NamingException: {0}
Explanation
A problem occurred attempting to stop the RMI connector.
User Response:
Examine the displayed exception for more details.
ADMC0026I: RMI Connector available at port {0}
Explanation
None
User Response:
None
ADMC0027I: Tivoli HTTPAdapter available on port {0}
Explanation
None
User Response:
None
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. Make sure 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 serverindex.xml file to check the CELL_DISCOVERY_ADDRESS port number; make sure there is no port conflict.
ADMC0031E: Unable to initialize the discovery adapter for the managed process: {0}
Explanation
The ManagedProcess failed to initialize the discovery service.
User Response:
Open 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 can not be found in the SOAP header.
User Response:
Provide user/password or set the thread credential before creating a SOAP client. Depending on the nature of the admin calls, this may not be required.
ADMC0034W: Cannot obtain WSSecurityContext.
Explanation
Generally this is caused by a SOAP Connector and SWAM combination which is not supported in ND environment.
User Response:
Do not use SWAM with the SOAP connector.
ADMC0035E: No username specified to create a secure SOAP admin client
Explanation
The username is a required attribute for the secure admin client
User Response:
Specify the username either in the properties file or through parameters passed to AdminClientFactory
ADMC0036E: No password specified to create a secure SOAP admin client
Explanation
The password is a required attribute for the secure admin client
User Response:
Specify the password either in the properties file or through parameters passed to AdminClientFactory
ADMC0037W: No trustStore specified to create a secure SOAP admin client
Explanation
In most cases, the trustStore is a required attribute for the secure admin client
User Response:
Specify the trustStore either in the properties file or through parameters passed to AdminClientFactory
ADMC0038W: No keyStore specified to create a secure SOAP admin client
Explanation
The keyStore may be required attribute in case of client certificate authentication.
User Response:
Specify the keyStore either in the properties file or through parameters passed to AdminClientFactory
ADMC0040I: Tivoli HTTPAdapter is disabled in the secure mode
Explanation
As a simple JMX Adapter, Tivoli HTTP Adapter is not protected by Websphere security. Hence, the JMX Adapter is intentionally disabled if security is enabled in order to avoid a security exposure.
User Response:
None
ADMC0041E: SOAP connector hostname not specified
Explanation
The hostname is a required property to create the SOAP connector
User Response:
Make sure hostname is provided. The property key for hostname is AdminClient.CONNECTOR_HOST.
ADMC0042E: SOAP connector port number not specified
Explanation
The port is a required property to create SOAP connector
User Response:
Make sure port is provided. The property key for port is AdminClient.CONNECTOR_PORT.
ADMC0043E: Error occurred while deserializing the received exception
Explanation
The SOAP admin client failed to restore the exception object from the received SOAP response message
User Response:
Make sure the exception class is in the client side classpath.
ADMC0044E: Unsupported AdminClient operation: {0}
Explanation
The exception could be thrown if an unsupported AdminClient operation is called upon SOAP connector
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMC0045E: Unable to create SOAP header to carry the security attributes
Explanation
SOAP connector calls the DOM API to create SOAP header
User Response:
Make sure XML parsing engine is functioning
ADMC0046W: Failed to load properties from com.ibm.SOAP.configURL: {0}
Explanation
AdminClientFactory loads the file as specified by com.ibm.SOAP.configURL in order 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 it points to does exist in 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 dmgr contacts each discovered nodeagent at fixed interval. The lost connection could be caused by the network connectivity failure or the node agent has been stopped
User Response:
If the node agent is not intentionlly stopped, make sure the network is not down, for instance, try to make a 'ping
'. ADMC0048I: Established the connection to previously disconnected nodeagent at node {0}
Explanation
The dmgr keeps pinging each previously disconnected node agent at fixed interval. Normally the connection can be reestablished if the network failure is recovered.
User Response:
None
ADMC0049E: Failed to ping the node agent at node "{0}" due to a null admin client; The ping thread is terminated.
Explanation
The dmgr failed to obtain a valid admin client to the node agent when the node was discovered; because of this, there is no way to ping the node agent.
User Response:
Make sure all the JMX connectors are running inside the targeted node agent when the node agent is started. Check the SystemOut.log file for this node agent process
ADMC0050E: Exception occurred while reading the node discovery protocol
Explanation
The admin runtime fails to obtain the node discovery protocol
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMC0051W: Failed to do a multicast-based process discovery, trying discovery mbean instead...
Explanation
Either because it's a standalone machine or because multicast is malfuctioning/not supported in the local network.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMC0052W: 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.
ADMC0053E: Could not create SOAP Connector to connect to host {0} at port {1} with SOAP Connector security enabled.
Explanation
In most cases, the wrong host and port are provided. If the remote process runs in secure mode, appropriate user and password are required.
User Response:
Make sure the correct data is provided to create a SOAP connector. Supply username and password in soap.client.props file or on 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. Please check any necessary modifications.
Explanation
The JSSE provider must support FIPS on both the client and server.
User Response:
Make sure the server is configured for FIPS support. Verify the JSSE provider on the client supports FIPS.