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 | 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 Managed Bean (MBean) name that is 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. |
Explanation | The Managed Bean (MBean) name that is 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 | 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 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 | 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 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 | 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 | 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 | 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 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 WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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 | 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 PmiAbstractModule object is set to perform an undefined function on the supplied data object. |
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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | Performance Monitoring Infrastructure (PMI) is unable to create the object that manages the Transaction Module performance statistics. |
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 | 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 WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
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. |
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 | 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 | 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. |
Explanation | A configuration parameter that is specified for the connection pool module is not valid. The only valid parameter for this option is 'PoolSize' |
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 | Counter is out of synchronization. |
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 is a wrong data type. |
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 is a dupliate module name. |
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 | 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 | 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 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. |
Explanation | An error occured when you persisted Performance Monitoring Infrastructure (PMI) configuration to the pmi-config.xml file. |
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 | Performance Monitoring Infrastructure (PMI) is not able to read the pmi-config.xml file from its expected location. |
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 | 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 | 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 | Performance Monitoring Infrastructure (PMI)could not locate the configuration service. PMI uses the configuration service to interact with configuration information. |
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 | Performance Monitoring Infrastructure (PMI) cannot locate a localized resource bundle. A resource bundle is a language specific set of information that is used by PMI when communicating information to the Application Server users. |
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 | Performance Monitoring Infrastructure (PMI) is initialized for Application Server Version 6.x, but it finds Version 5.x configuration parameters. The initialSpecLevel attribute in the server.xml configuration file is deprecated in Version 6.0. |
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 Performance Monitoring Infrastructure (PMI) could not be initialized within the deployment manager process of a network deployment configuration. PMI does not function within the deployment manager so any attempts to initialize it might fail. |
Action | The PMI service is not available in the deployment manager process. Review the deployment manager configuration files and turn PMI off. |
Explanation | Unable to create default Managed Bean (MBean) for custom Performance Monitoring Infrastructure (PMI) module. |
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 | Performance Monitoring Infrastructure (PMI) is unable to read the source XML file that is used for configuring a custom PMI module. Custom PMI is an application programming interface (API) that is 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 | 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 | 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 | 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 | Cannot locate a parent Managed Bean (MBean) for the custom Performance Monitoring Infrastructure (PMI) module. |
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 | 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 | 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 | An error occured when deactivating custom Performance Monitoring Infrastructure (PMI) Managed Bean (MBean). |
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 | 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 | 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 | 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 that is provided already exists for the module. An error in the custom PMI XML template might create the problem. |
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 | Deactivating custom PMI MBean. |
Action | No user action is required. |
Explanation | This is an audit message that acknowledges Performance Monitoring Infrastructure (PMI) is enabled and functioning. |
Action | No user action is required. |
Explanation | Performance Monitoring Infrastructure (PMI) is disabled. |
Action | No user action is required. |
Explanation | Found in cache. |
Action | No user action is required. |
Explanation | Not found in cache. |
Action | No user action is required. |
Explanation | Performance Monitoring Infrastructure (PMI) indicates a variety of problems. The unique nature of the problem is indicated in the message body. |
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/ . |