WebSphere Process Server messages     Operating Systems: All supported

RASD

RASD0001W: Parsing error in Registration xml {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/.
RASD0002W: TestMsg: {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/.
RASD0003I: No AlertConfig object for AlertKey {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/.
RASD0004W: Method called with a null parameter. This is invalid {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/.
RASD0005W: Method called with an invalid paramter of: {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/.
RASD0006W: JMX Error Info: ObjectName: {0} Other1: {1} Other2: {2} Other3: {3}
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/.
RASD0007W: Diagnostic Provider Registry Propagation failed because {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/.
RASD0008W: Regular Expression String is invalid {0}
Problem Regular expression compilation of the string failed
User response If part of setStateCollectionSpec, then re-specify string to be a valid entry
RASD0009W: ApplicationException in evaluteTriggerConditions {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/.
RASD0010W: Runtime Throwable Exception in evaluteTriggerConditions
Problem A lower level exception was thrown in evaluateTriggerConditions. View that exception.
User response Review thrown exception for further details.
RASD0011W: Invalid object type of {0} in DiagnosticEvent HashMap
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/.
RASD0012I: Updating State Collection Spec from {0} to {1}
Problem The State Collection Specification was updated, this is an informational message
User response No user action required
RASD0013W: Attempting to update State Collection spec, but new spec is null
Problem The State Collection Spec passed in to the method was null
User response If this is a result of invalid data due to driving an MBean method, review your procedures
RASD0014W: Attempting to update State Collection spec, but new spec is invalid {0}
Problem The State Collection Spec passed in to the method was invalid
User response If this is a result of invalid data due to driving an MBean method, review your procedures
RASD0015W: Retrieve of DiagnosticConfig object for DPName, DPName passed in was null
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/.
RASD0016W: CBE Completion Exception Populating CBE
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/.
RASD0017W: CBE Completion Exception Populating CBE, 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/.
RASD0018W: Exception retrieving the DTD for parsing DiagnosticProvider.xml
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/.
RASD0019W: Exception resulted from z/OS Servant MBean JMX call
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/.
RASD0020W: JMX Query to convert DPid to ObjectName threw exception
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/.
RASD0021W: JMX Call threw exception
Problem An exception occurred in a JMX invocation
User response See prior exception for further details
RASD0022W: Registry result: {0} could not be parsed
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/.
RASD0023W: No DPName associated with that DPID: {0}
Problem Diagnostic Provider ID is not registered and, thus has no Diagnostic Provider Name associated with it
User response Verify that the Diagnostic Provider ID was entered accurately
RASD0024W: Failed to activateMBean w/exception: {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/.
RASD0025W: Aggregator called with an invalid method of: {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/.
RASD0026I: Null MessageDataElement on CBE, could not get ResourceBundleName
Problem CBE was created with a ResourceBundle, so no localization will be taking place
User response No User Action Required
RASD0027W: CommonBaseEventDiagnosticEventImpl constructed with null CBE
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/.
RASD0028W: No Extended Data Element found for this CBE
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/.
RASD0029W: InstanceId of {0} not fully parseable to WebSphere topology elements
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/.
RASD0030W: Failed to find property {0} in Hash/Property Lookup
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/.
RASD0031W: No Bean or hashMap data held
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/.
RASD0032W: Admin Service null, should exists, cannot register with DiagnosticService MBean
Problem This is a sample message, don''t sweat it
User response This is a sample message, don''t sweat it at all
RASD0033W: Multiple DiagnosticService MBeans found: {0}. Should be just 1.
Problem This is a sample message, don''t sweat it
User response This is a sample message, don''t sweat it
RASD0034W: No rule/configuration data found for AlertKey: {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/.
RASD0035I: No configuration registry data found of 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/.
RASD0038I: Failed to send alert, DiagnosticEvent getContent did not return a CBE
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/.
RASD0041W: Error processing DiagnosticProvider XML: {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/.
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.rasdiag.resources.RasDiagMessages.html

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