Explanation | A parsing error occurs when the administrative code tries to read the MBean descriptor file. |
Action | Find XML grammar errors for the MBean descriptor file in question and correct them. |
Explanation | An incorrect visibility value is specified. |
Action | Specify a visibility value as an integer between 1 and 4 (inclusive). |
Explanation | The system cannot find the DTD file that is associated with the MBean descriptor file. |
Action | Verify the corresponding DTD file is in the class path. |
Explanation | The parent MBean descriptor failed to load because of parsing errors or a missing parent type. |
Action | Verify that the MBean descriptor of the parent type exists. |
Explanation | The service did not load the corresponding MBean; in most cases, the MBean descriptor file either cannot be found in the class path or cannot be read. |
Action | Verify that the correct MBean descriptor file is provided and is accessible from the class path. |
Explanation | A conflict has occurred during the MBean registration. |
Action | For custom service MBean, extension MBean, or application MBean, check the code to find the conflict. |
Explanation | Read the nested exception that occurs here. In most cases, the attribute does not exist. |
Action | Follow the nested exception if the attribute is correctly provided. |
Explanation | Read the nested exception that occurs here. In most cases, the attributes do not exist. |
Action | Follow the nested exception if attributes are correctly provided. |
Explanation | Read the nested exception that occurs here. Either the attribute does not exist or the attribute type does not match. |
Action | Follow the nested exception if both the attribute name and the type are correct. |
Explanation | Read the nested exception that occurs here. Either the attribute does not exist or the attribute type does not match. |
Action | Follow the nested exception if both the attribute name and the type are correct. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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 | An incorrect configuration ID is provided. |
Action | Verify the configuration ID. |
Explanation | While registering a notification listener, the service determined that the target MBean is not specified. |
Action | Specify a valid object name for the target MBean. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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 | None |
Action | None |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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 | The service failed to create an MBean object name; in most cases, the MBean descriptor file cannot be found in the class path or cannot be read. |
Action | Verify that the correct MBean descriptor file is provided and is accessible from the class path. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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 | This exception is unexpected. The cause is not immediately known. |
Action | 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 | This exception is unexpected. The cause is not immediately known. |
Action | 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 | No appropriate permission is associated with the request thread. |
Action | Verify that the appropriate credentials (userID and password) are specified before sending out the request. |
Explanation | An incorrect property is specified for the repository configuration. |
Action | Check the property in question and then correct it. |
Explanation | Requests like the getAttribute request need to obtain the ModelMBeanInfo interface for the target MBean during security checking. No such ModelMBeanInfo interface is found for the target MBean. |
Action | Verify that the target MBean exists in the server run time. |
Explanation | None |
Action | None |
Explanation | A valid path is required to create a J2C resource adapter. |
Action | Specifiy a valid RAR file path. |
Explanation | The service failed to open the specified RAR file. |
Action | Verify that the identified path is a valid one. |
Explanation | The service failed to extract the archive to the target directory. |
Action | Verify that the specified archive exists and that it is not corrupted. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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 | The specified path does not exist and cannot be created. |
Action | 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 | None |
Action | None |
Explanation | A problem occurred trying to launch the script that performs the requested operation. |
Action | 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 | The remote process might not be running. |
Action | Verify that the process to which you connect is running. |
Explanation | If the system clocks on the deployment manager and a node is not synchronized closely enough, the operations involving the node might fail when security is enabled. |
Action | Set the systems clocks to within at least a few minutes of each other. |
Explanation | This attribute will be removed in a future release. |
Action | Update the code that uses this attribute to use a non-deprecated attribute or operation. |
Explanation | This operation will be removed in a future release. |
Action | Update the code that uses this operation to use a non-deprecated attribute or operation. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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 | No connection definition exists under the specified resource adapter. |
Action | Verify that the specified connection definition is correct. It might belong to another resource adapter. Check the ra.xml file. |
Explanation | You must specify the connection definition to create a new Java 2 Connector Architecture (J2C) connection factory. |
Action | Specify the connection definition that is defined in the resource adapter. |
Explanation | The specified AdminObject name does not exist under the specified resource adapter. |
Action | Verify that the specified AdminObject name is correct. It might belong to another resource adapter. Check the ra.xml file. |
Explanation | You need to specify the AdminObject value to create a new Java 2 Connector Architecture (J2C) activation specification. |
Action | Specify the AdminObject name that is defined in the resource adapter. |
Explanation | The ActivationSpec name does not exist under the specified resource adapter. |
Action | Verify that the ActivationSpec is correct; it might belong to another resource adapter. Check the ra.xml file. |
Explanation | You need to specify the ActivationSpec name to create a new Java 2 Connector Architecture (J2C) activation specification. |
Action | Specify the ActivationSpec name that is defined in the resource adapter. |
Explanation | The introspection of the bean failed because the class name is not specified. |
Action | Verify that the ra.xml file contains the correct data. For ResourceAdapter:<resourceadapter-class>, For ConnectionFactory: <managedconnectionfactory-class>, for ActivationSpec: <activationspec-class>: AdminObject:<adminobject-class>. |
Explanation | Creating the new instance of the specified class was failed with IllegalAccessException. There is inconsistency in the specified class between the one installed on the machine and the one for the compilation. |
Action | Please check the classpath to make sure if it points to the correct version. You may have to uninstall if there are multiple version of the related software. |
Explanation | Creating the new instance of the specified class was failed because of an InstantiationException exception. The class name specified to be introspected in ra.xml can be incorrect. |
Action | Check the specified class name defined in ra.xml is correct. |
Explanation | The introspection of the specified bean failed because an InvocationTargetException exception occurred while trying to read the value of the specified property. |
Action | Check the specified class in the resource adapter archive (RAR) file. |
Explanation | The introspection of the specified bean failed because of an IntrospectionException exception. |
Action | Check the definition of the specified class in the resource adapter archive(RAR) file. |
Explanation | The introspection of the specified bean failed because of a ClassNotFoundException exception. |
Action | Check the definition of the specified class in the resource adapter archive(RAR) file. |
Explanation | The introspection of the specified bean failed because of a java.lang.Exception. |
Action | Check the module and the class defined in it. |
Explanation | a syntax error occurred in specifying the ResourcePropertiesSet value. |
Action | Check the parameter syntax. |
Explanation | An IOException exception occurred while processing the ResourcePropertiesSet parameter. |
Action | Check the specified ResourcePropertiesSet parameter. |
Explanation | An unknown exception occurred while processing the ResourcePropertiesSet parameter. |
Action | Check the specified ResourcePropertiesSet parameter. |
Explanation | A syntax error occurred when specifying the ResourcePropertiesSet parameter. |
Action | Check the parameter syntax. |
Explanation | A syntax error occurred when specifying the ResourcePropertiesSet parameter. |
Action | Check the parameter syntax. |
Explanation | A syntax error occurred when specifying the ResourcePropertiesSet parameter. Specify the keyword only once. |
Action | Check the parameter syntax. |
Explanation | A syntax error occurred when specifying the ResourcePropertiesSet parameter. An additional data exists at the end of the values. |
Action | Check the parameter syntax. |
Explanation | An IOException exception occurred while processing the ResourcePropertiesSet parameter. |
Action | Check the parameter. |
Explanation | A syntax error occurred when specifying the ResourcePropertiesSet parameter. The keyword {0} is required. |
Action | Check the parameter syntax. Add the specified keyword and its associated value. |
Explanation | The service failed to create an instance of the class loader to load the specified resource adapter archive (RAR) file. |
Action | 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 | The specified entry is missing in the ra.xml file. |
Action | Modify the ra.xml file. |
Explanation | The specified entry is missing in the ra.xml file. |
Action | Modify the ra.xml file to include this entry. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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 | This version of RAR is not supported by the specified target node. |
Action | None. |
Explanation | The serverindex.xml document for this node is missing or has errors. |
Action | Check the serverindex.xml document for errors. If this is in a nodeagent server, run the syncNode command line tool to copy the master version from the deployment manager. |
Explanation | This action is an audit of an attempted process launch by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted process launch. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted process stop by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted process stop. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted node restart by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted node restart. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted node synchronization by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted node synchronization. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted application start by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted application start. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted application stop by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted application stop. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted cluster start by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted cluster start. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted cluster stop by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted cluster stop. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted cluster immediate stop by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted cluster immediate stop. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted cluster ripple start by the specified user. |
Action | No action is required. |
Explanation | This action is an audit of an attempted cluster ripple start. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted server stop by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted server stop. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted server immediate stop by the specified user. |
Action | No user action is required. |
Explanation | This action is an audit of an attempted server immediate stop. The user ID is not available because security is not enabled. |
Action | No user action is required. |
Explanation | Adding or removing a node with WebSphere version < 6.0 into a cell controlled by a dmgr at the 6.0 or higher version is not supported. |
Action | If this message resulted from attempting to add a node, you should upgrade the node that you wish to add to WebSphere 6.0 or higher before adding it to this cell. If this message resulted from attempting to remove a node, please refer to the special instructions for removing a 5.x node from a cell controlled by a 6.x (or higher) dmgr. |
Explanation | Beginning the process of adding a node to a cell. |
Action | No action is necessary. |
Explanation | Deployment Manager version earlier than that of a node is an unsupported configuration. |
Action | Upgrade the Deployment Manager to the same or later version as that of the node. |
Explanation | The extension class file may be missing from the module, or it may not be properly defined in the module's plugin.xml file |
Action | Check the extension is properly defined and the implementation class is located in the module |
Explanation | Unexpected exception from MBean Bouter. |
Action | Contact implementor of the MBean router for a fix. |
Explanation | Unexpected MBean route type while calling an MBean. |
Action | Contact implementor of MBean router for a fix. |
Explanation | Inefficient MBean query executed. This query may lead to performance problems. |
Action | Code that uses this operation may need to be updated to supply a node and process name. |
Explanation | The introspection of the specified bean failed because of an exception. |
Action | Verify that the module and the specified class defined in it are correct. |