Express (Distributed operating systems), v8.0 > Reference > Messages
ADMC
ADMC0001E: Unable to serialize object: {0}
Explanation The object needs to implement the java.io.Serializable class to be marshalled. Action 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 connector. Generally this error occurs because of a port conflict. Action 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 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. Action Connect through the AdminClient interface, which is the only supported mechanism for connecting to the AdminService interface from a separate process.
ADMC0006E: No port is specified for the SOAP connector.
Explanation The SOAP connector must listen to one specific port. Action 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. Action 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 connector failed to marshall the Java (TM) object, which probably does not implement the java.io.Serializable interface. Action Verify that the Java Class implements the java.io.Serializable interface.
ADMC0009E: The system failed to make the SOAP RPC call: {0}
Explanation This generic exception indicates that the SOAP RPC (remote procedure call) failed. Either the remote process is not reachable, or there is a marshalling problem. Action Verify that the remote process is reachable and that the SOAP connector is running on the remote process. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this connector error.
ADMC0011E: The SOAP remote procedure call (RPC) cannot be unmarshalled.
Explanation The SOAP connector fails to extract the SOAP Call object from a received SOAP message; some other general exceptions have occurred. Action Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error.
ADMC0013I: The SOAP connector is available at port {0}
Explanation This informational message indicates the availability of the SOAP connector. Action No action is required.
ADMC0014E: A failure occurred starting connector {0}.
Explanation The AdminService interface cannot start the JMX (Java Management Extensions) connector with the specified type. Action Check the logs, trace, and the First Failure Data Capture (FFDC) 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. Action Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this connector error.
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 a secure mode, an appropriate user ID and password are required. On the z/OS operating systems in a secure mode, register the CA certificate for the remote process in the keyring for your client user ID. On other operating systems in a secure mode, specify the self-signed certificate for the remote process in the truststore for your client user ID. Action 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. Action 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. Action Check the serverindex.xml file for the current node and verify that the BOOTSTRAP_ADDRESS endpoint is specified for this server.
ADMC0019E: No 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. Action 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 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. Action Check the server logs and look for message NMSV0018I which is Name server available on bootstrapport. Examine the displayed exception and the First Failure Data Capture (FFDC) log to find the most relevant root cause for naming error.
ADMC0021W: The RMI connector failed to start with NamingException: {0}
Explanation The RMI (Java Remote Method Invocation) connector failed to create an InitialContext object and bind itself to the name space. Action Check the server logs and look for message NMSV0018I which is Name server available on bootstrapport. Examine the displayed exception and the First Failure Data Capture (FFDC) log to find the most relevant root cause for naming error.
ADMC0022W: The RMI (Java Remote Method Invocation) connector could not start and RemoteException: {0}
Explanation A problem occurred attempting to start the RMI (Java Remote Method Invocation) connector. Action Examine the displayed exception for more details. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this connector error.
ADMC0023W: The RMI (Java Remote Method Invocation) connector could not be stopped and NamingException: {0}
Explanation A problem occurred attempting to stop the RMI (Java Remote Method Invocation) connector. Action Examine the displayed exception for more details. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this connector error.
ADMC0026I: The RMI Connector is available at port {0}
Explanation This informational message indicates the availability of the RMI (Java Remote Method Invocation) connector. Action No action is required.
ADMC0027I: The Tivoli HTTPAdapter is available on port {0}
Explanation This informational message indicates the availability of the Tivoli HTTPAdapter. Action No action is required.
ADMC0028W: Error starting the Tivoli HTTPAdapter: {0}
Explanation A problem occurred attempting to start the HTTP adapter. Action Examine the displayed exception for more details. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this connector error.
ADMC0029E: Unable to initialize the discovery adapter for the dmgr: {0}
Explanation The dmgr process failed to initialize the discovery service. Action Examine the serverindex.xml file to check the port number defined for dmgr 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. Action Open the serverindex.xml file to check the NODE_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. Action 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 header. Action Provide a userID and password or set the thread credential before creating a SOAP client.
ADMC0034W: The system cannot obtain WSSecurityContext.
Explanation The system cannot obtain the WSSecurityContext instance. The SOAP connector and SWAM (Simple WebSphere Authentication Mechanism) combination are not supported in the Network Deployment environment. Action 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 SOAP secure administrative client. Action User name either in the properties file or through parameters passed to the AdminClientFactory class.
ADMC0036E: No password has been specified to create a secure SOAP administrative client.
Explanation The password is a required attribute for the SOAP secure administrative client. Action Specify the password either in the properties file or through parameters passed to the AdminClientFactory class.
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 SOAP secure administrative client. Action Specify the truststore file either in the properties file or through parameters passed to the AdminClientFactory class.
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. Action Specify the keystore file either in the properties file or through parameters passed to the AdminClientFactory class.
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.
Action 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 connector. Action Verify that a host name is provided. Make sure the properties passed in to create an AdminClient instance contains the key value for the host name. 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 connector. Action Verify that a port number is provided. Make sure the properties passed in to create an AdminClient instance contains the key value for the port. The property key for port is AdminClient.CONNECTOR_PORT.
ADMC0043E: An error occurred while deserializing the received exception.
Explanation The SOAP administrative client failed to restore the exception object from the received SOAP response message. Action Verify that the exception class is in the client side class path.
ADMC0044E: The system encountered an unsupported AdminClient operation: {0}
Explanation The specified exception can occur if an unsupported administrative client (AdminClient) operation called the SOAP connector. Action More info at:
ADMC0045E: The system is unable to create a SOAP header to carry the security attributes.
Explanation A SOAP connector calls the DOM (Document Object Model) API to create a SOAP header, but is unable to create the header. Action Verify that the XML parsing engine is functioning.
ADMC0046W: The system failed to load properties from com.ibm.SOAP.configURL: {0}
Explanation The AdminClientFactory class failed to load the file as specified by com.ibm.SOAP.configURL system property. Security related data could not be obtained. Action The com.ibm.Soap.ConfigUrl property can be set on the command line, programatically in your Java client or by default it is set in setupCmdLine script of your Application Server bin directory. Make sure the soap.client.props file exists in the directory it point to inside the setupCmdLine script.
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 node agent at fixed intervals. The lost connection can result from a network connectivity failure or a stopped node agent. Action If the node agent is not intentionally stopped, make sure the network is up; for instance, try performing a ping <nodeagent host name>.
ADMC0048I: The system established the connection to a previously disconnected node agent at node {0}.
Explanation The dmgr keeps pinging each previously disconnected node agent at fixed intervals. Normally the connection can be reestablished if the network failure is recovered. Action No action is required.
ADMC0049E: The dmgr failed to ping the node agent at node "{0}" because of a null administrative client. The ping thread is terminated.
Explanation The dmgr 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. Action Verify that all the Java Management Extensions (JMX) connectors are running inside the targeted node agent when the node agent starts. Check the server logs 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. Action More info at:
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. Action More info at:
ADMC0052W: Failed to send out the discovery message to the process: {0}
Explanation The Discovery MBean on the process it is connecting to is not found or problem invoking the method on the Discovery MBean. Action Verify the JMX SOAP connector is running. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this discovery error. If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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. If FIPS is enabled on the remote process, client side properties files need to be updated as well. Action Verify that the correct data is provided to create a SOAP connector. Supply a user name and password in a soap.client.props file or at the command line. Ensure that soap.client.props, ssl.client.props and java.security file on the client side are appropriately updated if running in FIPS enabled mode.
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. Action Verify that the server is configured for FIPS support. Verify that the JSSE provider on the client supports FIPS.
ADMC0055I: The JMX SOAP connector has been disabled.
Explanation This informational message indicates the availability of the SOAP connector. Action No action is required.
ADMC0056I: The JMX RMI connector has been disabled.
Explanation This informational message indicates the availability of the Java Management Extensions (JMX) RMI connector. Action No action is required.
ADMC0057I: The JMX JSR160RMI connector has been disabled.
Explanation This informational message indicates the availability of the Java Management Extensions (JMX) RMI connector. Action No action is required.
ADMC0058I: The JMX JSR160RMI connector is available at port {0}
Explanation This informational message indicates the availability of the JSR160 RMI (Java Remote Method Invocation - javax.management.remote.rmi ) connector. Action No action is required.
ADMC0067I: The JMX IPC connector has been disabled.
Explanation This informational message indicates the availability of the Java Management Extensions (JMX) RMI connector. Action No action is required.
ADMC0068I: The JMX IPC connector is available at port {0}
Explanation This informational message indicates the availability of the IPC connector. Action No action is required.
ADMC0069E: The endpoint definition is empty for the IPC connector; the IPC connector will not be available
Explanation There is no endpoint entry for the IPC connector in the relevant configuration file serverindex.xml. Action Check whether the configuration is corrupted.
ADMC0070I: The IPC connector is available at port {0}
Explanation This informational message indicates the availability of the IPC connector. Action No action is required.
ADMC0071E: ChannelFrameworkService is unavilable at this point; IPC connector will not be available
Explanation At the point the IPC connector is to get initialized and started, the channel framework is not available yet. Action Verify the channel framework is initialized correctly.
ADMC0072E: Failed to initialize or start channel chain {0} due to exception {1}
Explanation A channel framework chain for the IPC connctor failed to initialize or start. Action Verify the channel framework is functioning correctly.
ADMC0073E: Failed to stop channel chain {0} due to exception {1}
Explanation A channel framework chain for the IPC connctor failed to stop. Action Verify the channel framework is functioning correctly.
ADMC0074E: Connection will be closed due to unrecoverable error {0}
Explanation A non-recoverable error occurred, connection will be closed and data may be lost. Action Check to see if there are incorrect changes made to the system configuration, or whether network connection is functioning properly.
ADMC0075E: Failed to get ChannelFrameworkService due to {0}; IPC connector will not be available
Explanation At the point the IPC connector is to get initialized and started, the channel framework is not available yet. Action Verify the channel framework is initialized correctly.
ADMC0076E: Failed to get security token due to {0}
Explanation The client is a server process, yet the security token was not available. Action Verify the security service is initialized correctly.
ADMC0077E: Invalid credential
Explanation The Kerberos login failed. Two possible reasons for this failure exist: The username or the password is not valid. The credential cache expired. Action Check whether the user name and password are correct, and correct them if they are not. If the Kerberos credential cache is used, check whether the cache has expired and renew the cache if it has expired.