Express (Distributed operating systems), v8.0 > Reference > Messages
PMRM
PMRM0001I: ARM implementation is: {0}
Explanation The name of the Application Response Measurement (ARM) implementation class. This message is for informational purposes only. Action No action is required.
PMRM0002E: Failed to instantiate: {0}
Explanation Request metrics was unable to instantiate the class. Action Verify that the class name is correct and that all its dependencies are satisfied.
PMRM0003I: {0}
Explanation This is Performance Monitoring Infrastructure (PMI) request metrics timing information. This message is for informational purposes only. Action No action is required.
PMRM0004I: PmiRmInit servername={0}
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.
PMRM0017E: CallContext passed is null
Explanation The PmiRmCallContext parameter passed was null. Action Verify that the parameter is non-null before calling the function
PMRM0018E: CallContext contains a null correlator
Explanation The CallContext parameter contains a null correlator. Action The parameter must contain a non-null correlator before calling the function.
PMRM0019E: CallContext contains a null ArmTransaction
Explanation The CallContext parameter contains a null ArmTransaction object. Action The parameter must contain a non-null ArmTransaction object before calling the function.
PMRM0020E: External Component attempted to peek Request Metrics correlator. This operation is not allowed.
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.
PMRM0021E: Parameter passed is null
Explanation A null parameter was passed. Action The parameter must be non-null before calling the function.
PMRM0022E: PmiReqMetricsImpl is null
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.
PMRM0023E: Underlying ArmTransaction is null
Explanation The underlying ArmTransaction object is null. Action 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. Action 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 Action 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 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.
PMRM0027E: The PmiRmArmTx passed as a parameter is null
Explanation The Correlation Service Arm wrapper (PmiRmArmTx object) passed as a parameter is null. Action The PmiRmArmTx object must be non-null.
PMRM0028E: The PmiRmArmTx peeked off the stack is null
Explanation The PmiRmArmTx object peeked off the stack is null. Action The PmiRmArmTx object peeked off the stack must be non-null.
PMRM0029E: Cannot perform {0} on correlation service when Request Metrics is disabled
Explanation Cannot perform peek on correlation service when request metrics is disabled. Action Enable request metrics first and then perform peek on correlation service.
PMRM0030E: No correlator is found in the stack. Expect one.
Explanation The correlator stack is empty when it should not. Action 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. Action 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. Action This is an internal error. Restart the application server and try again.
PMRM0033E: ARM API {0} returns error code {1}
Explanation The call to the Application Response Measurement (ARM) API failed. Action The ARM agent must be started. Disable and enable ARM again from the administrative console.
PMRM0100E: Unable to register lite data service (HLSLiteData): {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0101E: Method createCorrelator called with null instance handle. Internal error.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0102E: Method setData called with no incoming correlator.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0103E: Error registering PmiRmJmxService MBean
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0104E: Internal error: attempt to obtain non-existent ip filter configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0105E: Internal error: attempt to obtain non-existent uri filter configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0106E: Internal error: attempt to obtain non-existent ejb filter configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0107E: Internal error: attempt to copy null filter
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0108E: Exception thrown {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0109E: JMX cannot access filters or enabled flags with null filter type
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.
PMRM0110E: Internal error. Filter configuration not previously initialized
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0111E: JMX cannot set filters or enabled flags to null values
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.
PMRM0112E: Filter configuration not initialized for filter type {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0113E: Invalid attempt to enable null filter type
Explanation The enableFilter Java Management Extensions (JMX) was called with a null filter type. Action Specify a valid filter type to the enableFilter method.
PMRM0114E: Unable to determine pid.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0115E: Internal error. Stack not empty at end of request
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0116E: Exception during startup configuration
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0200W: Failed to instantiate {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
PMRM0206W: Request metrics users cannot reset the PmiRmArmStack since request metrics starts the edge transaction
Explanation Request metrics users cannot reset the PmiRmArmStack class because request metrics starts the edge transaction. Action No action is 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 object. Action Make sure the user PmiRmArmTx object does not miss the Application Response Measurement (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 object but gets a user PmiRmArmTx object. Action Make sure the user PmiRmArmTx object does not miss the Application Response Measurement (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. Action The edge transaction must be traced.
PMRM0210W: {0}: Request metrics expects a correlator in the stack but cannot find one.
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.
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 can be ignored. Action 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 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.
PMRM0213W: {0}: The ARM transaction start handle does not match the one on stack, so do not call stop on this transaction
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.
PMRM0214W: {0}: Wrong ARM agent type: {0}
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.
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 managed bean (MBean) object is not valid. Action Pass a valid parameter.
PMRM0216W: Duplicate registration with the existing registration id {0}: component name {1}, identity {2}.
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.
PMRM0300I: {0} config change committed
Explanation This information is for informational purpose only. Action No action is required.