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