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

PMRM0100E: Unable to register lite data service (HLSLiteData): {0}
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0101E: Method createCorrelator called with null instance handle. Internal error.
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0102E: Method setData called with no incoming correlator.
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0103E: Error registering PmiRmJmxService MBean
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0104E: Internal error: attempt to obtain non-existent ip filter configuration.
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0105E: Internal error: attempt to obtain non-existent uri filter configuration.
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0106E: Internal error: attempt to obtain non-existent ejb filter configuration.
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0107E: Internal error: attempt to copy null filter
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0108E: Exception thrown {0}
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

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 is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

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 is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

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 is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0115E: Internal error. Stack not empty at end of request
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0116E: Exception during startup configuration
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

PMRM0200W: Failed to instantiate {0}
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

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


WebSphere Application Server  Last updated:  Fri Jul 18 16:46:35 EDT 2003
Library | Support | Trademarks | Feedback