WebSphere Process Server messages     Operating Systems: All supported

PMRM

PMRM0001I: ARM implementation is: {0}
Problem The name of the ARM implementation class
User response No action required
PMRM0002E: Failed to instantiate: {0}
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
PMRM0003I: {0}
Problem PMI Request Metrics timing information
User response No action required
PMRM0004I: PmiRmInit servername={0}
Problem PMI Request Metrics has been initialized on server
User response No action required
PMRM0017E: CallContext passed is null
Problem 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
Problem 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
Problem 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.
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.
PMRM0021E: Parameter passed is null
Problem Null parameter was passed
User response Verify that the parameter is non-null before calling the function.
PMRM0022E: PmiReqMetricsImpl is null
Problem PmiReqMetricsImpl is null
User response This is an internal error. Restart the application server and try again.
PMRM0023E: Underlying ArmTransaction is null
Problem 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
Problem 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
Problem 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}
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.
PMRM0027E: The PmiRmArmTx passed as a parameter is null
Problem 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
Problem 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
Problem 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.
Problem 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.
Problem 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}.
Problem 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}
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.
PMRM0100E: Unable to register lite data service (HLSLiteData): {0}
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/.
PMRM0101E: Method createCorrelator called with null instance handle. Internal error.
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/.
PMRM0102E: Method setData called with no incoming correlator.
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/.
PMRM0103E: Error registering PmiRmJmxService MBean
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/.
PMRM0104E: Internal error: attempt to obtain non-existent ip filter configuration.
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/.
PMRM0105E: Internal error: attempt to obtain non-existent uri filter configuration.
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/.
PMRM0106E: Internal error: attempt to obtain non-existent ejb filter configuration.
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/.
PMRM0107E: Internal error: attempt to copy null filter
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/.
PMRM0108E: Exception thrown {0}
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/.
PMRM0109E: JMX cannot access filters or enabled flags with null filter type
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
PMRM0110E: Internal error. Filter configuration not previously initialized
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/.
PMRM0111E: JMX cannot set filters or enabled flags to null values
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
PMRM0112E: Filter configuration not initialized for filter type {0}
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/.
PMRM0113E: Invalid attempt to enable null filter type
Problem 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.
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/.
PMRM0115E: Internal error. Stack not empty at end of request
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/.
PMRM0116E: Exception during startup configuration
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/.
PMRM0200W: Failed to instantiate {0}
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/.
PMRM0206W: Request metrics users cannot reset the PmiRmArmStack since request metrics starts the edge transaction
Problem 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}
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.
PMRM0208W: Request metrics expects a PmiRmCallContext but gets a user PmiRmArmTx {0}
Problem 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
Problem 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.
Problem 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.
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.
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.
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.
PMRM0213W: {0}: The ARM transaction start handle does not match the one on stack, so do not call stop on this transaction
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.
PMRM0214W: {0}: Wrong ARM agent type: {0}
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.
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}
Problem The parameter that is passed to the PmiRmJmxService MBean is not valid.
User response Pass a valid parameter.
PMRM0216W: Duplicate registration with the existing registration id {0}: component name {1}, identity {2}.
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.
PMRM0300I: {0} config change committed
Problem Config change committed
User response No action required
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.pmi.reqmetrics.reqmetrics.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)