WebSphere Performance Monitoring Request Metrics messages

PMRM0001I: ARM implementation is: {0}
Explanation: The name of the ARM implementation class
User Response: No action required

PMRM0002E: Failed to instantiate: {0}
Explanation: Request Metrics was unable to instantiate the class
User Response: Verify that the class name is correct and that all its dependencies are satisfied

PMRM0003I: {0}
Explanation: PMI Request Metrics timing information
User Response: No action required

PMRM0004I: PmiRmInit servername={0}
Explanation: PMI Request Metrics has been initialized on server
User Response: No action required

PMRM0017E: CallContext passed is null
Explanation: The PmiRmCallContext parameter passed was null.
User Response: Verify that the parameter is non-null before calling the function

PMRM0018E: CallContext contains a null correlator
Explanation: CallContext contains a null correlator
User Response: Verify that the parameter contains a non-null correlator before calling the function.

PMRM0019E: CallContext contains a null ArmTransaction
Explanation: CallContext contains a null ArmTransaction
User Response: Verify that the parameter contains a non-null ArmTransaction before calling the function.

PMRM0020E: External Component attempted to peek Request Metrics correlator. This operation is not allowed.
Explanation: 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.

PMRM0021E: Parameter passed is null
Explanation: Null parameter was passed
User Response: Verify that the parameter is non-null before calling the function.

PMRM0022E: PmiReqMetricsImpl is null
Explanation: PmiReqMetricsImpl is null
User Response: This is an internal error. Restart the application server and try again.

PMRM0023E: Underlying ArmTransaction is null
Explanation: Underlying ArmTransaction is null
User Response: This is an internal error. Restart the application server and try again.

PMRM0024E: This method cannot be called for Tivoli Agents
Explanation: This method cannot be called for Tivoli Agents
User Response: This is an internal error. Restart the application server and try again.

PMRM0025E: This method cannot be called on the interface class
Explanation: This method cannot be called on the interface class
User Response: This is an internal error. Restart the application server and try again.

PMRM0026E: Cannot find the component or request for the request type {0}
Explanation: 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.

PMRM0027E: The PmiRmArmTx passed as a parameter is null
Explanation: The PmiRmArmTx passed as a parameter is null
User Response: The PmiRmArmTx passed as a parameter has null value

PMRM0028E: The PmiRmArmTx peeked off the stack is null
Explanation: The PmiRmArmTx peeked off the stack is null
User Response: The PmiRmArmTx peeked off the stack has null value

PMRM0029E: Cannot perform {0} on correlation service when Request Metrics is disabled
Explanation: Cannot perform peek on correlation service when Request Metrics is disabled
User Response: Enable Request Metrics

PMRM0030E: No correlator is found in the stack. Expect one.
Explanation: The correlator stack is empty when it should not.
User Response: This is an internal error. Restart the application server and try again.

PMRM0031E: Got a null thread context.
Explanation: Cannot get thread context from request metrics.
User Response: This is an internal error. Restart the application server and try again.

PMRM0032E: An exception occurred when parsing the incoming correlator {0}.
Explanation: This problem results from an internal error. The incoming correlator might have an incorrect format.
User Response: No user action is required.

PMRM0033E: ARM API {0} returns error code {1}
Explanation: 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.

PMRM0100E: Unable to register lite data service (HLSLiteData): {0}
Explanation: 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/.

PMRM0101E: Method createCorrelator called with null instance handle. Internal error.
Explanation: 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/.

PMRM0102E: Method setData called with no incoming correlator.
Explanation: 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/.

PMRM0103E: Error registering PmiRmJmxService MBean
Explanation: 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/.

PMRM0104E: Internal error: attempt to obtain non-existent ip filter configuration.
Explanation: 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/.

PMRM0105E: Internal error: attempt to obtain non-existent uri filter configuration.
Explanation: 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/.

PMRM0106E: Internal error: attempt to obtain non-existent ejb filter configuration.
Explanation: 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/.

PMRM0107E: Internal error: attempt to copy null filter
Explanation: 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/.

PMRM0108E: Exception thrown {0}
Explanation: 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/.

PMRM0109E: JMX cannot access filters or enabled flags with null filter type
Explanation: 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

PMRM0110E: Internal error. Filter configuration not previously initialized
Explanation: 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/.

PMRM0111E: JMX cannot set filters or enabled flags to null values
Explanation: 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

PMRM0112E: Filter configuration not initialized for filter type {0}
Explanation: 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/.

PMRM0113E: Invalid attempt to enable null filter type
Explanation: JMX method enableFilter was called with a null filter type
User Response: Specify a valid filter type to the enabledFilter method

PMRM0114E: Unable to determine pid.
Explanation: 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/.

PMRM0115E: Internal error. Stack not empty at end of request
Explanation: 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/.

PMRM0116E: Exception during startup configuration
Explanation: 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/.

PMRM0200W: Failed to instantiate {0}
Explanation: 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/.

PMRM0206W: Request metrics users cannot reset the PmiRmArmStack since request metrics starts the edge transaction
Explanation: Request metrics users cannot reset the PmiRmArmStack since request metrics starts the edge transaction
User Response: No action required

PMRM0207W: Request metrics has to pop user PmiRmArmTx from the correlator stack {0}
Explanation: 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.

PMRM0208W: Request metrics expects a PmiRmCallContext but gets a user PmiRmArmTx {0}
Explanation: Request metrics expects a PmiRmCallContext but gets a user PmiRmArmTx
User Response: Make sure user PmiRmArmTx does not miss the ARM stop call.

PMRM0209W: Request metrics cannot make the call for {0} because there is no parent correlator in the stack
Explanation: Request metrics cannot make the call because there is no parent correlator in the stack.
User Response: Make sure edge transaction is traced

PMRM0210W: {0}: Request metrics expects a correlator in the stack but cannot find one.
Explanation: Request metrics expects a correlator in the stack but cannot find one.
User Response: No action required

PMRM0211W: Request metrics finds an obsolete system property {0}. Its value is {1}, same as the relevant configuration data. The configuration data will be used and the property will be ignored.
Explanation: 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.

PMRM0212W: Request metrics finds an obsolete system property {0}. Its value is {1}, different from the relevant configuration data, whose value is {2}. The configuration data will be used and the property will be ignored.
Explanation: 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.

PMRM0213W: {0}: The ARM transaction start handle does not match the one on stack, so do not call stop on this transaction
Explanation: 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.

PMRM0214W: {0}: Wrong ARM agent type: {0}
Explanation: 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.

PMRM0215W: The parameter that is passed to method {0}: parameter name {1}, value {2} is not valid. Use one of the following values instead: {3}
Explanation: The parameter that is passed to the PmiRmJmxService MBean is not valid.
User Response: Pass a valid parameter.

PMRM0300I: {0} config change committed
Explanation: Config change committed
User Response: No action required