Explanation | The name of the ARM implementation class |
Action | No action 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 | PMI Request Metrics timing information |
Action | No action required |
Explanation | PMI Request Metrics has been initialized on server |
Action | No action required |
Explanation | The PmiRmCallContext parameter passed was null. |
Action | Verify that the parameter is non-null before calling the function |
Explanation | CallContext contains a null correlator |
Action | Verify that the parameter contains a non-null correlator before calling the function. |
Explanation | CallContext contains a null ArmTransaction |
Action | Verify that the parameter contains a non-null ArmTransaction before calling the function. |
Explanation | External Component attempted to peek Request Metrics correlator. This operation is not allowed. |
Action | Verify that the parameter contains a non-null correlator before calling the function. |
Explanation | Null parameter was passed |
Action | Verify that the parameter is non-null before calling the function. |
Explanation | PmiReqMetricsImpl is null |
Action | This is an internal error. Restart the application server and try again. |
Explanation | Underlying ArmTransaction 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 | 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 PmiRmArmTx passed as a parameter is null |
Action | The PmiRmArmTx passed as a parameter has null value |
Explanation | The PmiRmArmTx peeked off the stack is null |
Action | The PmiRmArmTx peeked off the stack has null value |
Explanation | Cannot perform peek on correlation service when Request Metrics is disabled |
Action | Enable Request Metrics |
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 | No user action is required. |
Explanation | The call to the ARM API failed. |
Action | Make sure the ARM agent is started successfully. Disable and enable ARM again from the adminconsole. |
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/. |
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/. |
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/. |
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/. |
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/. |
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/. |
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/. |
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/. |
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/. |
Explanation | 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 JMX method |
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/. |
Explanation | A JMX method attempted to set Request Metrics filters or enabled flags to null values |
Action | Specify non-null filters and enabled flags to JMX method |
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/. |
Explanation | JMX method enableFilter was called with a null filter type |
Action | Specify a valid filter type to the enabledFilter method |
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/. |
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/. |
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/. |
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/. |
Explanation | Request metrics users cannot reset the PmiRmArmStack since request metrics starts the edge transaction |
Action | No action required |
Explanation | Request metrics expects a request metrics context but gets a user PmiRmArmTx |
Action | Make sure user PmiRmArmTx does not miss the ARM stop call or forget to pop. |
Explanation | Request metrics expects a PmiRmCallContext but gets a user PmiRmArmTx |
Action | Make sure user PmiRmArmTx does not miss the ARM stop call. |
Explanation | Request metrics cannot make the call because there is no parent correlator in the stack. |
Action | Make sure edge transaction is traced |
Explanation | Request metrics expects a correlator in the stack but cannot find one. |
Action | No action required |
Explanation | The obsolete system property has the same value as the configuration data and will be ignored |
Action | Remove the obsolete system property to avoid confusion. |
Explanation | The obsolete system property has different value than the configuration data and will be ignored |
Action | Decide what value should be used and set the correct configuration data via adminconsole for request metrics. Remove the obsolete system property. |
Explanation | The ARM transaction start handle does not match the one on stack, so do not call stop on this transaction |
Action | This is an internal error, which should not happen. |
Explanation | The ARM agent type is not set correctly by a user. |
Action | User need to set the ARM agent type correctly when using PmiRmJmxService MBean. |
Explanation | The parameter that is passed to the PmiRmJmxService MBean is not valid. |
Action | Pass a valid parameter. |
Explanation | Config change committed |
Action | No action required |