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


PMON

PMON0025W: Error while persisting PMI configuration to pmi-config.xml: {0}
Explanation: Error while persisting PMI configuration to pmi-config.xml.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0010W: Cannot find the file: {0}
Explanation: PMI will produce this generic error when it can not find a file it needs for internal processing. Typically, this processing takes place while PMI is initializing. The file name that can not be located is identified in the body of the message.
User Response: 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/.

PMON0101W: Unable to create default MBean for custom PMI module: {0}
Explanation: Unable to create default MBean for custom PMI module.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0008W: Invalid data ID: {0}
Explanation: This warning will be displayed when a PMI module is unable to identify a data object it has been asked to process. Each PMI module is configured for a finite set of data objects. When this warning is displayed, the PMI module generating the warning has been asked to process a data object that it can not identify. The invalid data identity is provided in the message.
User Response: 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/.

PMON0001W: A null path is passed to PMI: {0}
Explanation: An invalid, null path has been passed into PMI. The path identifier is used by PMI to arrange counters used for tracking application statistics. PMI starts with a root path and all Websphere components and applications store their statistics as branches off the root path. When a null path is passed into PMI, it prevents PMI from fulfilling the request made of it, because it can not locate the item being specified.
User Response: 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/.

PMON0006W: Cannot find a mbean for the PMI data descriptor: {0}
Explanation: This warning is displayed when PMI can not match a PMI name to its associated MBean. The term æMBeanÆ is a short name for a æmanaged beanÆ. The java standard for managing resources is known as JMX or Java Management eXtensions. In JMX, MBeans are java objects that represent a manageable resource. PMI resources are addressable through an MBean interface.
User Response: 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/.

PMON0015W: AdminUtilImpl has exception to connect to AdminClient/AdminService: {0}
Explanation: AdminUtilImpl has encountered an exception while it is connecting to AdminClient or AdminService.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0106W: Error while deactivating custom PMI MBean: {0}
Explanation: Error while deactivating custom PMI MBean.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0031W: Detected both 5.0 and 6.0 PMI configuration. Starting PMI service using the 6.0 configuration. The attribute initialSpecLevel in server.xml is deprecated as of 6.0.
Explanation: This warning message occurs when PMI is initialized for Websphere 6.0, but it finds Websphere 5.0 configuration parameters. The attribute, initialSpecLevel in the server.xml configuration file is deprecated as of version 6.0.
User Response: 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/.

PMON0108W: Unable to register custom PMI module due to duplicate statistic id in the parent stats group/instance: ID={0}; ParentStats={1}
Explanation: This is a message generated by PMI while it is initializing a custom PMI module. PMI is unable to construct a statistic for the custom PMI module because the statistic identity provided already exists for the module. This problem can be caused by an error in the custom PMI XML template.
User Response: 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/.

PMON0028W: Error getting Config service
Explanation: This warning message indicates that PMI was not able to locate the configuration service. The configuration service is used by PMI to interact with configuration information. This information instructs PMI on how to initialize itself and can be manipulated via PMIÆs configuration panel in the administration console.
User Response: This exception is unexpected. The cause is not immediately known.

PMON1102I: Not found in cache: {0}
Explanation: Not found in cache.
User Response: None

PMON0019W: Unexpected runtime config attribute name: {0}
Explanation: This warning message is displayed when a configuration parameter specified for the connection pool module is not valid. The only valid parameter for this option is "PoolSize". Any other value specified will trigger this warning message.
User Response: 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/.

PMON0026W: Error while reading PMI configuration from pmi-config.xml: {0}
Explanation: If this warning message is displayed, PMI is not able to read the pmi-config.xml file from its expected location.
User Response: This exception is unexpected. The cause is not immediately known.

PMON1001I: PMI is enabled
Explanation: This is an audit message that simply acknowledges that PMI is enabled and functioning.
User Response: None

PMON0014W: PmiFactory failed to create TransactionModule: {0}
Explanation: This is a warning message thrown when PMI is unable to successfully create the object that manages the Transaction Module performance statistics. The exception information provided in the message will indicate the cause of the failure.
User Response: This exception is unexpected. The cause is not immediately known.

PMON9999E: Internal error: {0}
Explanation: This message is used internally by PMI to indicate a variety of problems. The unique nature of the problem being identified is indicated in the message body.
User Response: This exception is unexpected. The cause is not immediately known. For more information, see Technote #1201768.

PMON0107W: Unable to register custom PMI module since the PMI service is not enabled: {0}
Explanation: This message will display when PMI is disabled and a component or application attempts to create a PMI object. This is simply a warning message intended to inform the PMI client owner why the request being can not be completed successfully.
User Response: 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/.

PMON0016W: AdminUtilImpl has exception to find/list ObjectNames: {0}
Explanation: This is a PMI internal message that is displayed when PMI is unable to match a PMI name to its corresponding MBean name. The term "MBean" is a short name for a "managed bean". The java standard for managing resources is known as JMX or Java Management eXtensions. In JMX, MBeans are java objects that represent a manageable resource. PMI resources are addressable through an MBean interface. In this instance, PMI is attempting to locate the MBean name and is unable.
User Response: This message is sometimes seen when a third-party performance monitoring tool is used to view PMI statistics. Please check that the configuration is correct for the tool. If a third-party tool is not being used and this message persists, please contact customer service.

PMON0020W: Counter is out of sync: {0}
Explanation: Counter is out of sync.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0032W: PMI Service is not available in the Deployment Manager process.
Explanation: This warning message indicates an attempt has been made to initialize PMI within the Deployment Manager process of a Websphere ND configuration. PMI does not function within the Deployment Manager so any attempt to initialize it will be aborted within this process.
User Response: The PMI service is not available in the deployment manager process. Please review the deployment manager configuration files and turn PMI off.

PMON0201I: Deactivating custom PMI MBean for: {0}
Explanation: Deactivating custom PMI MBean.
User Response: None

PMON0009W: Wrong parameter passed to the updateData method in PmiAbstractModule: {0}
Explanation: This warning is generated when the PmiAbstractModule object is asked to perform an undefined function on the supplied data object.
User Response: 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/.

PMON0022W: Duplicate module name: {0}
Explanation: Duplicate module name.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0004W: Exception to get AdminUtilImpl in PmiJmxMapper: {0}
Explanation: This warning is generated when the PmiJmxMapper class is unable to create a new AdminUtil class. The AdminUtil interface provides a means for PMI to access the Websphere admin object. This is needed for JMX connectivity.
User Response: 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/.

PMON0017W: AdminUtilImpl has exception to getAdminState: {0}
Explanation: This error is created when PMI is unable to successfully communicate with the admin client. It is possible that the admin client is no longer able to communicate with the targeted Websphere admin.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0002W: Cannot find a PMI module name for the MBean: {0}
Explanation: This warning is produced when the MBean name specified by the caller of PMI can not be matched up with an internal PMI name. The term "MBean" is a short name for a "managed bean". The java standard for managing resources is known as JMX or Java Management eXtensions. In JMX, MBeans are java objects that represent a manageable resource. PMI resources are addressable through an MBean interface. If the MBean specified name does not match a currently loaded PMI name, the PMI0002W warning is generated. The cause of this problem can be due to an error made by the calling application or the calling application is trying to reference a PMI name that has yet to be loaded by Websphere.
User Response: This message is sometimes seen when a third-party performance monitoring tool is used to view PMI statistics. Please check that the configuration is correct for the tool. If a third-party tool is not being used and this message persists, please contact customer service.

PMON0012W: Wrong number of parameters passed to PmiFactory: {0}
Explanation: This warning message is displayed when PMI is creating a module and the parameters being passed in to PMI do not match the requirements of the module being created. The module type where the failure occurs is indicated in the message.
User Response: 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/.

PMON0024W: MBean to PMI module mapping is overwritten for: {0}
Explanation: This message is displayed when the MBean path being stored for reference already exists in the cache. The term "MBean" is a short name for a "managed bean". The java standard for managing resources is known as JMX or Java Management eXtensions. In JMX, MBeans are java objects that represent a manageable resource. PMI resources are addressable through an MBean interface. In this instance, PMI is associating an MBean path to an existing internal PMI object. This message will be seen in cases where an external PMI client is referencing a PMI resource that has, perhaps, been stopped and restarted.
User Response: This message is sometimes seen when a third-party performance monitoring tool is used to view PMI statistics. Please check that the configuration is correct for the tool. If a third-party tool is not being used and this message persists, please contact customer service.

PMON1101I: Found in cache: {0}
Explanation: Found in cache.
User Response: None

PMON0011W: Wrong pmiSpec in PmiUtil: {0}
Explanation: This warning message is produced when PMI is asked to set a performance monitoring level to an unknown value. The performance monitoring level is a setting PMI uses to determine which modules, sub-modules and statistics are included in the current monitoring set. If this message is displayed, a client of PMI is requesting a change to a monitoring level and the value specified is not valid.
User Response: 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/.

PMON0105W: Cannot locate PMI module item for: {0}
Explanation: This warning message is created when PMI is unable to locate the module identified by the path displayed in the warning message. PMI is attempting to locate the module so that it may perform a task on that module.
User Response: 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/.

PMON0003W: MultipleObjectNamesExistException: MBean key is: {0}
Explanation: This error is produced when the MBean name specified by the caller of PMI is matched to more than one PMI name. The term "MBean" is a short name for a "managed bean". The java standard for managing resources is known as JMX or Java Management eXtensions. In JMX, MBeans are java objects that represent a manageable resource. PMI resources are addressable through an MBean interface. If the MBean specified name is found to match more than one PMI name this error is generated.
User Response: 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/.

PMON0018W: AdminUtilImpl has no ObjectName returned from query: {0}
Explanation: This is a PMI internal message that is displayed when PMI is unable to match a PMI name to its corresponding MBean name. The term "MBean" is a short name for a "managed bean". The java standard for managing resources is known as JMX or Java Management eXtensions. In JMX, MBeans are java objects that represent a manageable resource. PMI resources are addressable through an MBean interface. In this instance, PMI is attempting to locate the MBean name and is unable.
User Response: This message is sometimes seen when a third-party performance monitoring tool is used to view PMI statistics. Please check that the configuration is correct for the tool. If a third-party tool is not being used and this message persists, please contact customer service.

PMON0007W: No PMI module config found: {0}
Explanation: This error identifies a condition where PMI is unable to locate the configuration of a specified module. Modules are the organizational unit PMI uses to break down functional components within Websphere.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0027W: Error while persisting PMI configuration to server.xml: {0}
Explanation: This warning message is generated when PMI fails in an attempt to store the current PMI configuration information. The failure is a captured exception that is thrown while PMI is trying to physically store the information.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0102W: Unable to read custom PMI module configuration: {0}
Explanation: This warning message is created when PMI is unable to read the source XML file used for configuring a custom PMI module. Custom PMI is an API used by PMI providers to register a module with PMI. When a custom PMI module is initialized, a XML file is read by PMI to determine the module's configuration information. If the custom PMI XML file can not be found or read, this warning message is generated.
User Response: 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/.

PMON0023W: Unable to register PMI module due to duplicate name: {0}
Explanation: This is a warning message generated when PMI is unable to register a module due to a naming conflict. PMI tracks all modules and sub-modules by way of a unique name within the specified path. If this message is displayed, PMI can not perform the module addition because a module with the same name already exists.
User Response: 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/.

PMON0005W: Null parameter is passed to PMI: {0}
Explanation: This event is triggered when PMI is asked perform an update and one of the parameters sent by the PMI client is null. The calling component should be investigated to determine why it is erroneously passing in invalid information.
User Response: 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/.

PMON0013W: Wrong type of parameters passed to PmiFactory: {0}
Explanation: This warning message is displayed when PMI is creating a module and one of the parameters being passed in to PMI is not of the expected object type. The incorrect parameter information is provided in the warning message.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0021W: Wrong data type: {0}
Explanation: Wrong data type.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0030W: Error loading custom PMI resource bundle: {0}
Explanation: This warning is generated when PMI can not locate a localized resource bundle. A resource bundle is a language specific set of information used by PMI when communicating information to the Websphere user.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0104W: Cannot locate a parent MBean for the custom PMI module: {0}
Explanation: Cannot locate a parent MBean for the custom PMI module.
User Response: This exception is unexpected. The cause is not immediately known.

PMON0103W: Unable to register custom PMI module due to duplicate name under the same parent or invalid PMI tree path: {0}
Explanation: This warning message is generated when PMI is asked to create a new module under an invalid parent path or under a parent that contains a module of the same name. PMI module names must be unique for each parent in the PMI tree.
User Response: 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/.

PMON1002I: PMI is disabled
Explanation: PMI is disabled.
User Response: None

Reference topic    

Terms of Use | Feedback

Last updated: Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/PMON.html

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