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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | This informational message indicates the availability of the SOAP connector. |
Action | No action is required. |
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. |
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. |
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, you must register the CA certificate for the remote process in the keyring for your client user ID. On other operating systems in a secure mode, you must 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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | This informational message indicates the availability of the RMI (Java Remote Method Invocation) connector. |
Action | No action is required. |
Explanation | This informational message indicates the availability of the Tivoli HTTPAdapter. |
Action | No action is required. |
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. |
Explanation | The deployment manager process failed to initialize the discovery service. |
Action | Examine the serverindex.xml file to check the port number defined for deployment manager discovery. Verify that there is no port conflict. |
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. |
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. |
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. |
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. |
Explanation | The user name is a required attribute for the SOAP secure administrative client. |
Action | Specify the user name either in the properties file or through parameters passed to the AdminClientFactory class. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The specified exception can occur if an unsupported administrative client (AdminClient) operation called the SOAP connector. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
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. |
Action | If the node agent is not intentionally stopped, make sure the network is up; for instance, try performing a ping <nodeagent host name>. |
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. |
Action | No action is required. |
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. |
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. |
Explanation | The administrative run time failed to obtain the node discovery protocol. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
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 Federal Information Processing Standard (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. |
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. |
Explanation | This informational message indicates the availability of the SOAP connector. |
Action | No action is required. |
Explanation | This informational message indicates the availability of the Java Management Extensions (JMX) Remote Method Invocation (RMI) connector. |
Action | No action is required. |
Explanation | This informational message indicates the availability of the Java Management Extensions (JMX) Remote Method Invocation (RMI) connector. |
Action | No action is required. |
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. |
Explanation | This informational message indicates the availability of the Java Management Extensions (JMX) Remote Method Invocation (RMI) connector. |
Action | No action is required. |
Explanation | This informational message indicates the availability of the IPC connector. |
Action | No action is required. |
Explanation | There is no endpoint entry for the IPC connector in the relevant configuration file serverindex.xml. |
Action | Check whether the configuration is corrupted. |
Explanation | This informational message indicates the availability of the IPC connector. |
Action | No action is required. |
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. |
Explanation | A channel framework chain for the IPC connctor failed to initialize or start. |
Action | Verify the channel framework is functioning correctly. |
Explanation | A channel framework chain for the IPC connctor failed to stop. |
Action | Verify the channel framework is functioning correctly. |
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. |
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. |
Explanation | The client is a server process, yet the security token was not available. |
Action | Verify the security service is initialized correctly. |
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. |