Explanation | The name of the Application Response Measurement (ARM) implementation class. This message is for informational purposes only. |
Action | No action is required. |
Explanation | Request metrics was unable to instantiate the class. |
Action | Verify that the class name is correct and that all its dependencies are satisfied. |
Explanation | This is Performance Monitoring Infrastructure (PMI) request metrics timing information. This message is for informational purposes only. |
Action | No action is required. |
Explanation | Performance Monitoring Infrastructure (PMI) request metrics has been initialized on the server. This message is for informational purposes only. |
Action | No action is required. |
Explanation | The PmiRmCallContext parameter passed was null. |
Action | Verify that the parameter is non-null before calling the function |
Explanation | The CallContext parameter contains a null correlator. |
Action | The parameter must contain a non-null correlator before calling the function. |
Explanation | The CallContext parameter contains a null ArmTransaction object. |
Action | The parameter must contain a non-null ArmTransaction object before calling the function. |
Explanation | An external component attempted to peek request metrics correlator which is not allowed. |
Action | Verify that the parameter contains a non-null correlator before calling the function. |
Explanation | A null parameter was passed. |
Action | The parameter must be non-null before calling the function. |
Explanation | The Prepare servers for request metrics collection check box is not selected, which causes Performance Monitoring Infrastructure (PMI) request metrics not be instantiated. |
Action | Select the Prepare servers for request metrics collection check box in the administrative console, save the change, and restart the application server. |
Explanation | The underlying ArmTransaction object is null. |
Action | This is an internal error. Restart the application server and try again. |
Explanation | This method cannot be called for Tivoli agents. |
Action | This is an internal error. Restart the application server and try again. |
Explanation | This method cannot be called on the interface class |
Action | This is an internal error. Restart the application server and try again. |
Explanation | A missing component or request type definition or wrong request type is passed |
Action | This is an internal error. Restart the application server and try again. |
Explanation | The Correlation Service Arm wrapper (PmiRmArmTx object) passed as a parameter is null. |
Action | The PmiRmArmTx object must be non-null. |
Explanation | The PmiRmArmTx object peeked off the stack is null. |
Action | The PmiRmArmTx object peeked off the stack must be non-null. |
Explanation | Cannot perform peek on correlation service when request metrics is disabled. |
Action | Enable request metrics first and then perform peek on correlation service. |
Explanation | The correlator stack is empty when it should not. |
Action | This is an internal error. Restart the application server and try again. |
Explanation | Cannot get thread context from request metrics. |
Action | This is an internal error. Restart the application server and try again. |
Explanation | This problem results from an internal error. The incoming correlator might have an incorrect format. |
Action | This is an internal error. Restart the application server and try again. |
Explanation | The call to the Application Response Measurement (ARM) application programming interface (API) failed. |
Action | The ARM agent must be started. Disable and enable ARM again from the administrative console. |
Explanation | This exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 | A Java Management Extensions (JMX) method attempted to get or set a filter or filter enabled flag using a null filter type. |
Action | Specify a valid filter type to the JMX method. |
Explanation | This exception is unexpected. The cause is not immediately known. |
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 | A Java Management Extensions (JMX) method attempted to set request metrics filters or enabled flags to null values. |
Action | Specify non-null filters and enabled flags to the JMX method. |
Explanation | This exception is unexpected. The cause is not immediately known. |
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 enableFilter Java Management Extensions (JMX) was called with a null filter type. |
Action | Specify a valid filter type to the enableFilter method. |
Explanation | This exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 | Request metrics users cannot reset the PmiRmArmStack class because request metrics starts the edge transaction. |
Action | No action is required. |
Explanation | Request metrics expects a request metrics context but gets a user PmiRmArmTx object. |
Action | Make sure the user PmiRmArmTx object does not miss the Application Response Measurement (ARM) stop call or forget to pop. |
Explanation | Request metrics expects a PmiRmCallContext object but gets a user PmiRmArmTx object. |
Action | Make sure the user PmiRmArmTx object does not miss the Application Response Measurement (ARM) stop call. |
Explanation | Request metrics cannot make the call because there is no parent correlator in the stack. |
Action | The edge transaction must be traced. |
Explanation | Request metrics did not pass the context information when Web services was disabled. |
Action | Pass the context data no matter if Web services is enabled or not so that at Web services outbound, the correlator can be accessed and passed along in the SOAP (formerly known as Simple Object Access Protocol) header. |
Explanation | The obsolete system property has the same value as the configuration data and can be ignored. |
Action | Remove the obsolete system property to avoid confusion. |
Explanation | The obsolete system property has different value than the configuration data and can be ignored. |
Action | Decide what value should be used and set the correct configuration data on the administrative console for request metrics. Remove the obsolete system property. |
Explanation | The Application Response Measurement (ARM) transaction start handle does not match the one on stack. |
Action | Do not call stop on the ARM transaction. |
Explanation | The Application Response Measurement (ARM) agent type is not set correctly. |
Action | Set the ARM agent type correctly when using the PmiRmJmxService managed bean (MBean) object. |
Explanation | The parameter that is passed to the PmiRmJmxService managed bean (MBean) object is not valid. |
Action | Pass a valid parameter. |
Explanation | A component register with request metrics multiple times with the same identity parameter. |
Action | Do not register multiple times or pass a different identity parameter. |
Explanation | This information is for informational purpose only. |
Action | No action is required. |