WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


ADMN

ADMN0001W: The service is unable to parse the MBean descriptor file {0}.
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.
ADMN0002E: {0} is not a valid visibility value, which must be an integer within the range of 1 to 4 (inclusive).
Explanation An incorrect visibility value is specified.
Action Specify a visibility value as an integer between 1 and 4 (inclusive).
ADMN0003E: The service is unable to load a document type definition (DTD) file {0}.
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.
ADMN0004E: The service is unable to load parent type {0}.
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.
ADMN0005E: The service is unable to activate MBean: type {0}, collaborator {1}, configuration ID {2}, descriptor {3}.
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.
ADMN0006W: More than one MBean is registered with the same configuration identifier {0}.
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.
ADMN0007I: The getAttribute method results in exception {0}.
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.
ADMN0008I: The getAttributes method results in exception {0}.
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.
ADMN0009I: The setAttribute method results in exception {0}.
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.
ADMN0010I: The setAttributes method results in exception {0}.
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.
ADMN0011I: The invoke method results in exception {0}.
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/.
ADMN0012I: The specified configuration ID {0} contains the illegal character '*' or ',' and is replaced as {1}.
Explanation An incorrect configuration ID is provided.
Action Verify the configuration ID.
ADMN0013E: The name parameter cannot be null.
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.
ADMN0014W: The service cannot send {0} notification: {1}
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/.
ADMN0015I: The administration service is initialized.
Explanation None
Action None
ADMN0016E: The File Transfer Service cannot be initialized. The configuration object cannot be created. Exception {0}
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/.
ADMN0017E: The service is unable to create ObjectName: type {0}, configuration ID {2}, descriptor {3}.
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.
ADMN0018W: An error occurred registering the AppManagementMBean MBean: {0}
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/.
ADMN0020W: An exception occurred getting the local IP address: {0}
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/.
ADMN0021W: The service cannot dump the Java virtual machine (JVM) thread stack: {0}
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/.
ADMN0022E: Access is denied for the {0} operation on {1} MBean because of insufficient or empty credentials.
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.
ADMN0024W: The repository configuration contains a property with an undefined variable {0}. Exception information: {1}
Explanation An incorrect property is specified for the repository configuration.
Action Check the property in question and then correct it.
ADMN0025E: The service failed to get the ModelMBeanInfo interface for MBean: {0}; access is denied.
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.
ADMN0026I: Recycle the node {0} with file synchronization option: {1}
Explanation None
Action None
ADMN0027E: The path for the resource adapter archive (RAR) file cannot be null.
Explanation A valid path is required to create a J2C resource adapter.
Action Specifiy a valid RAR file path.
ADMN0028E: An exception occurred while opening resource adapter archive (RAR) file {0}. The exception is {1}
Explanation The service failed to open the specified RAR file.
Action Verify that the identified path is a valid one.
ADMN0029E: An error occurred while extracting archive {0}. The exception is {1}
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.
ADMN0030W: An error occurred while recycling node {0}. The exception is: {1}
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/.
ADMN0031E: An error occurred while extracting an archive: cannot create directory path {0}.
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/.
ADMN0032I: Running script {0}
Explanation None
Action None
ADMN0033E: An error occurred launching {0}: {1}
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/.
ADMN0034E: The service is unable to obtain a valid administrative client to connect process "{0}" from process "{1}", because of exception: {2}
Explanation The remote process might not be running.
Action Verify that the process to which you connect is running.
ADMN0035W: The system clock of node {0} is not synchronized with that of the deployment manager.
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.
ADMN0036W: The {0} attribute "{1}" is deprecated. {2}
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.
ADMN0037W: The {0} operation "{1}" is deprecated. {2}
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.
ADMN0038E: The service failed to save the resource adapter to assign object IDs. The exception is {0}
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/.
ADMN0039E: The specified connection definition (Connection factory interface = {0} ) does not exist under the specified resource adapter.
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.
ADMN0040E: The connection definition is not specified.
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.
ADMN0041E: The specified AdminObject name (AdminObjectClass name = {0}) does not exist under the specified 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.
ADMN0042E: The AdminObject value is not specified.
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.
ADMN0043E: The ActivationSpec name (ActivationSpecClass name = {0}) does not exist under the specified 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.
ADMN0044E: The ActivationSpec name is not specified.
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.
ADMN0045E: Introspection of the bean failed because the class name is not specified.
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>.
ADMN0046E: The service failed to create a new instance of the class:{0}. The exception is {1}
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.
ADMN0047E: The specified class:{0} can not be instanticated. The exception is {1}
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.
ADMN0048W: The service failed to introspect the class:{0} to read the value of property {1}.
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.
ADMN0049E: The service failed to introspect the class:{0}. The exception is {1}
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.
ADMN0050E: The service failed to introspect the class:{0}. The exception is {1}
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.
ADMN0051E: The service failed to introspect the class:{0}. The exception is {1}
Explanation The introspection of the specified bean failed because of a java.lang.Exception.
Action Check the module and the class defined in it.
ADMN0052E: A ResourcePropertiesSet syntax error occurred: A word is expected. Encountered {0}
Explanation a syntax error occurred in specifying the ResourcePropertiesSet value.
Action Check the parameter syntax.
ADMN0053E: A ResourcePropertiesSet parameter error occurred. An IOException exception occurred. (0)
Explanation An IOException exception occurred while processing the ResourcePropertiesSet parameter.
Action Check the specified ResourcePropertiesSet parameter.
ADMN0054E: A ResourcePropertiesSet parameter error occurred. An UnknownException exception occurred. (0)
Explanation An unknown exception occurred while processing the ResourcePropertiesSet parameter.
Action Check the specified ResourcePropertiesSet parameter.
ADMN0055E: A ResourcePropertiesSet syntax error occurred: keyword (name, type, value, desc, and required) is expected. Encountered {0}.
Explanation A syntax error occurred when specifying the ResourcePropertiesSet parameter.
Action Check the parameter syntax.
ADMN0056E: A ResourcePropertiesSet syntax error occurred: The value of {0} is expected. Encountered {1}.
Explanation A syntax error occurred when specifying the ResourcePropertiesSet parameter.
Action Check the parameter syntax.
ADMN0057E: A ResourcePropertiesSet syntax error occurred: {0} is specified more than once.
Explanation A syntax error occurred when specifying the ResourcePropertiesSet parameter. Specify the keyword only once.
Action Check the parameter syntax.
ADMN0058E: A syntax error occurred when specifying the ResourcePropertiesSet parameter resulting in an unrecognized value.
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.
ADMN0059E: An IOException exception occurred while processing the ResourcePropertiesSet parameter.
Explanation An IOException exception occurred while processing the ResourcePropertiesSet parameter.
Action Check the parameter.
ADMN0060E: A ResourcePropertiesSet syntax error occurred: {0} is required.
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.
ADMN0061E: The service failed to set up a class loader for {0}. The exception is {1}
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/.
ADMN0062E: {0} is not defined in the ra.xml file.
Explanation The specified entry is missing in the ra.xml file.
Action Modify the ra.xml file.
ADMN0063W: {0} is not defined in 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.
ADMN0064E: The system is unable to create the OS/400 repository listener: {0}
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/.
ADMN1000I: An attempt is made to launch {0} on node {1}. (User ID = {2})
Explanation This action is an audit of an attempted process launch by the specified user.
Action No user action is required.
ADMN1001I: An attempt is made to launch {0} on node {1}.
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.
ADMN1002I: An attempt is made to stop node {0}. (User ID = {1})
Explanation This action is an audit of an attempted process stop by the specified user.
Action No user action is required.
ADMN1003I: An attempt is made to stop node {0}.
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.
ADMN1004I: An attempt is made to restart node {0}. (User ID = {1})
Explanation This action is an audit of an attempted node restart by the specified user.
Action No user action is required.
ADMN1005I: An attempt is made to restart node {0}.
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.
ADMN1006I: An attempt is made to synchronize the {0} node. (User ID = {1})
Explanation This action is an audit of an attempted node synchronization by the specified user.
Action No user action is required.
ADMN1007I: An attempt is made to synchronize the {0} node.
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.
ADMN1008I: An attempt is made to start the {0} application. (User ID = {1})
Explanation This action is an audit of an attempted application start by the specified user.
Action No user action is required.
ADMN1009I: An attempt is made to start the {0} application.
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.
ADMN1010I: An attempt is made to stop the {0} application. (User ID = {1})
Explanation This action is an audit of an attempted application stop by the specified user.
Action No user action is required.
ADMN1011I: An attempt is made to stop the {0} application.
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.
ADMN1012I: An attempt is made to start the {0} cluster (User ID = {1}).
Explanation This action is an audit of an attempted cluster start by the specified user.
Action No user action is required.
ADMN1013I: An attempt is made to start the {0} cluster.
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.
ADMN1014I: An attempt is made to stop the {0} cluster (User ID = {1}).
Explanation This action is an audit of an attempted cluster stop by the specified user.
Action No user action is required.
ADMN1015I: An attempt is made to stop the {0} cluster.
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.
ADMN1016I: An attempt is made to immediately stop the {0} cluster (User ID = {1}).
Explanation This action is an audit of an attempted cluster immediate stop by the specified user.
Action No user action is required.
ADMN1017I: An attempt is made to immediately stop the {0} cluster.
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.
ADMN1018I: An attempt is made to ripple start the {0} cluster (User ID = {1}).
Explanation This action is an audit of an attempted cluster ripple start by the specified user.
Action No action is required.
ADMN1019I: An attempt is made to ripple start the {0} cluster.
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.
ADMN1020I: An attempt is made to stop the {0} server. (User ID = {1})
Explanation This action is an audit of an attempted server stop by the specified user.
Action No user action is required.
ADMN1021I: An attempt is made to stop the {0} server.
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.
ADMN1022I: An attempt is made to immediately stop the {0} server. (User ID = {1})
Explanation This action is an audit of an attempted server immediate stop by the specified user.
Action No user action is required.
ADMN1023I: An attempt is made to immediately stop the {0} server.
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.
ADMN1100E: Invalid request: attempt was made to add or remove a node with WebSphere version < 6.0 to a cell controlled by dmgr at version {0}.
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.
ADMN1101I: Beginning attempt to federate a node with WebSphere version {0} to a cell controlled by dmgr at version {1}.
Explanation Beginning the process of adding a node to a cell.
Action No action is necessary.
ADMN1200W: Unexpected exception from MBean Router {0}: {1}
Explanation Unexpected exception from MBean Bouter.
Action Contact implementor of the MBean router for a fix.
ADMN1201W: Unknown route type {0} from MBeanRouter {1}
Explanation Unexpected MBean route type while calling an MBean.
Action Contact implementor of MBean router for a fix.
ADMN1202W: Inefficient MBean query executed: {0}
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.
Reference topic    

Terms of Use | Feedback

Last updated: Feb 21, 2008 7:07:28 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.resources.adminservice.html

© Copyright IBM Corporation 2006, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)