Express (Distributed operating systems), v8.0 > Reference > Messages
CWPMI
CWPMI0001W: A null path is passed to PMI: {0}
Explanation A path which is null or not valid is passed into Performance Monitoring Infrastructure (PMI). PMI uses the path identifier to arrange counters that are 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 that is made of it, because it cannot locate the item that is being specified. Action More info at:
CWPMI0002W: Cannot find a PMI module name for the MBean: {0}
Explanation The Managed Bean (MBean) name specified by the caller of Performance Monitoring Infrastructure (PMI) cannot be matched up with an internal PMI name. In the Java Management Extensions (JMX) specification, 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 warning is generated. The cause of this problem is due to an error made by the calling application or the fact that the calling application is trying to reference a PMI name that is not loaded by Application Server. Action You receive this message when using a third-party performance monitoring tool to view PMI statistics. Check that the configuration is correct for the tool.
CWPMI0003W: MultipleObjectNamesExistException: MBean key is: {0}
Explanation The Managed Bean (MBean) name specified by the caller of Performance Monitoring Infrastructure (PMI) is matched to more than one PMI name. In the Java Management Extensions (JMX) specification , MBeans are java objects that represent a manageable resource. PMI resources are addressable through an MBean interface. If the MBean specified name matches more than one PMI name, this error occurres. Action More info at:
CWPMI0004W: Exception to get AdminUtilImpl in PmiJmxMapper: {0}
Explanation The PmiJmxMapper class is unable to create a new AdminUtil class. The AdminUtil interface enables PMI to access the administrative object, which the Java Management Extensions (JMX) requires for connectivity. Action More info at:
CWPMI0005W: Null parameter is passed to PMI: {0}
Explanation This event is triggered when Performance Monitoring Infrastructure (PMI) performs an update and one of the parameters that is sent by the PMI client is null. Action More info at:
CWPMI0006W: Cannot find a mbean for the PMI data descriptor: {0}
Explanation Performance Monitoring Infrastructure (PMI) cannot match a PMI name to its associated Managed Bean (MBean). In the Java Management Extensions (JMX) specification, MBeans are java objects that represent a manageable resource. PMI resources are addressable through an MBean interface. Action More info at:
CWPMI0007W: No PMI module config found: {0}
Explanation This error identifies a condition where Performance Monitoring Infrastructure (PMI) is unable to locate the configuration of a specified module. Modules are the organizational unit that PMI uses to break down functional components within Application Server. Action This exception is unexpected. The cause is not immediately known. 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/.
CWPMI0008W: Invalid data ID: {0}
Explanation A Performance Monitoring Infrastructure (PMI) module is unable to identify a data object that the module processes. Each PMI module is configured for a finite set of data objects. The message provides the data identity which is not valid. Action More info at:
CWPMI0009W: Wrong parameter passed to the updateData method in PmiAbstractModule: {0}
Explanation The PmiAbstractModule object is set to perform an undefined function on the supplied data object. Action More info at:
CWPMI0010W: Cannot find the file: {0}
Explanation Performance Monitoring Infrastructure (PMI) cannot find a file for its internal processing which takes place when PMI is initializing. The message identifies the file name that cannot be located. Action More info at:
CWPMI0011W: Wrong pmiSpec in PmiUtil: {0}
Explanation Performance Monitoring Infrastructure (PMI) sets the performance monitoring level to an value that is not valid. PMI uses the performance monitoring level to determine which modules, sub-modules, and statistics that are included in the current monitoring set. Action More info at:
CWPMI0012W: Wrong number of parameters passed to PmiFactory: {0}
Explanation Performance Monitoring Infrastructure (PMI) is creating a module but the parameters that are passed into PMI do not match the requirements of the module that is created. Action More info at:
CWPMI0013W: Wrong type of parameters passed to PmiFactory: {0}
Explanation Performance Monitoring Infrastructure (PMI) is creating a module but one of the parameters that is passed into PMI is not of the expected object type. Action More info at:
CWPMI0014W: PmiFactory failed to create TransactionModule: {0}
Explanation Performance Monitoring Infrastructure (PMI) is unable to create the object that manages the Transaction Module performance statistics. Action More info at:
CWPMI0015W: AdminUtilImpl has exception to connect to AdminClient/AdminService: {0}
Explanation AdminUtilImpl has encountered an exception while it is connecting to AdminClient or AdminService. Action This exception is unexpected. The cause is not immediately known.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/
CWPMI0016W: AdminUtilImpl has exception to find/list ObjectNames: {0}
Explanation Performance Monitoring Infrastructure (PMI) is unable to match a PMI name to its corresponding Managed Bean (MBean) name. In the Java Management Extensions (JMX) specification, MBeans are java objects that represent a manageable resource. An MBean interface addresses the PMI resources. Action You receive this message when using a third-party performance monitoring tool to view PMI statistics. Check that the configuration is correct for the tool.
CWPMI0017W: AdminUtilImpl has exception to getAdminState: {0}
Explanation PMI is unable to communicate with the administrative client. It is possible that the administrative client is no longer able to communicate with the target nodeagent or application server. Action More info at:
CWPMI0018W: AdminUtilImpl has no ObjectName returned from query: {0}
Explanation Performance Monitoring Infrastructure (PMI) created the warning message when PMI is unable to match a PMI name to its corresponding Managed Bean (MBean) name. In the Java Management Extensions (JMX) specification, MBeans are java objects that represent a manageable resource. An MBean interface addresses the PMI resources. Action You receive this message when using a third-party performance monitoring tool to view PMI statistics. Check that the configuration is correct for the tool.
CWPMI0019W: Unexpected runtime config attribute name: {0}
Explanation A configuration parameter specified for the connection pool module is not valid. The only valid parameter for this option is 'PoolSize' Action More info at:
CWPMI0020W: Counter is out of sync: {0}
Explanation Counter is out of synchronization. Action More info at:
CWPMI0021W: Wrong data type: {0}
Explanation This is a wrong data type. Action More info at:
CWPMI0022W: Duplicate module name: {0}
Explanation This is a dupliate module name. Action More info at:
CWPMI0023W: Unable to register PMI module due to duplicate name: {0}
Explanation Performance Monitoring Infrastructure (PMI) is unable to register a module because of 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 cannot perform the module addition because a module with the same name already exists. Action More info at:
CWPMI0024W: MBean to PMI module mapping is overwritten for: {0}
Explanation This message is displayed when the Managed Bean (MBean) path is stored for reference that already exists in the cache. In the Java Management Extensions (JMX) specification, MBeans are java objects that represent a manageable resource. An MBean interface addresses the PMI resources In this instance, PMI is associating an MBean path to an existing internal PMI object. Action You receive this message when using a third-party performance monitoring tool to view PMI statistics. Check that the configuration is correct for the tool.
CWPMI0025W: Error while persisting PMI configuration to pmi-config.xml: {0}
Explanation An error occured when you persisted Performance Monitoring Infrastructure (PMI) configuration to the pmi-config.xml file. Action More info at:
CWPMI0026W: Error while reading PMI configuration from pmi-config.xml: {0}
Explanation Performance Monitoring Infrastructure (PMI) is not able to read the pmi-config.xml file from its expected location. Action More info at:
CWPMI0027W: Error while persisting PMI configuration to server.xml: {0}
Explanation Performance Monitoring Infrastructure (PMI) fails in an attempt to store the current PMI configuration information. The failure is a captured exception that is created when PMI is trying to physically store the information. Action More info at:
CWPMI0028W: Error getting Config service
Explanation Performance Monitoring Infrastructure (PMI)could not locate the configuration service. PMI uses the configuration service to interact with configuration information. Action More info at:
CWPMI0030W: Error loading custom PMI resource bundle: {0}
Explanation Performance Monitoring Infrastructure (PMI) cannot locate a localized resource bundle. A resource bundle is a language specific set of information used by PMI when communicating information to the Application Server users. Action More info at:
CWPMI0031W: 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 Performance Monitoring Infrastructure (PMI) is initialized for Application Server v6.x, but it finds v5.x configuration parameters. The initialSpecLevel attribute in the server.xml configuration file is deprecated in v6.0. Action More info at:
CWPMI0032W: PMI Service is not available in the Deployment Manager process.
Explanation The Performance Monitoring Infrastructure (PMI) could not be initialized within the dmgr process of a network deployment configuration. PMI does not function within the dmgr so any attempts to initialize it might fail. Action The PMI service is not available in the dmgr process. Review the dmgr configuration files and turn PMI off.
CWPMI0101W: Unable to create default MBean for custom PMI module: {0}
Explanation Unable to create default Managed Bean (MBean) for custom Performance Monitoring Infrastructure (PMI) module. Action More info at:
CWPMI0102W: Unable to read custom PMI module configuration: {0}
Explanation Performance Monitoring Infrastructure (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, PMI reads an XML file to determine the configuration information of the module. Action More info at:
CWPMI0103W: Unable to register custom PMI module due to duplicate name under the same parent or invalid PMI tree path: {0}
Explanation Performance Monitoring Infrastructure (PMI) creates a new module under an parent path that is not valid or under a parent path that contains a module of the same name. PMI module names must be unique for each parent path in the PMI tree. Action More info at:
CWPMI0104W: Cannot locate a parent MBean for the custom PMI module: {0}
Explanation Cannot locate a parent Managed Bean (MBean) for the custom Performance Monitoring Infrastructure (PMI) module. Action More info at:
CWPMI0105W: Cannot locate PMI module item for: {0}
Explanation Performance Monitoring Infrastructure (PMI) is unable to locate the module identified by the path that is displayed in the warning message. PMI is attempting to locate the module so that it might perform a task on that module. Action More info at:
CWPMI0106W: Error while deactivating custom PMI MBean: {0}
Explanation An error occured when deactivating custom Performance Monitoring Infrastructure (PMI) Managed Bean (MBean). Action More info at:
CWPMI0107W: Unable to register custom PMI module since the PMI service is not enabled: {0}
Explanation Performance Monitoring Infrastructure (PMI) is disabled and a component or application attempts to create a PMI object. This message informs the PMI client owner why the request cannot be completed. Action More info at:
CWPMI0108W: Unable to register custom PMI module due to duplicate statistic id in the parent stats group/instance: ID={0}; ParentStats={1}
Explanation Performance Monitoring Infrastructure (PMI) created the message when it was initializing a custom PMI module. PMI is unable to construct a statistic identity for the custom PMI module because the statistic identity provided already exists for the module. An error in the custom PMI XML template might create the problem. Action More info at:
CWPMI0201I: Deactivating custom PMI MBean for: {0}
Explanation Deactivating custom PMI MBean. Action No user action is required.
CWPMI1001I: PMI is enabled
Explanation This is an audit message that acknowledges Performance Monitoring Infrastructure (PMI) is enabled and functioning. Action No user action is required.
CWPMI1002I: PMI is disabled
Explanation Performance Monitoring Infrastructure (PMI) is disabled. Action No user action is required.
CWPMI1101I: Found in cache: {0}
Explanation Found in cache. Action No user action is required.
CWPMI1102I: Not found in cache: {0}
Explanation Not found in cache. Action No user action is required.
CWPMI9999E: Internal error: {0}
Explanation Performance Monitoring Infrastructure (PMI) indicates a variety of problems. The unique nature of the problem is indicated in the message body. Action More info at: