- CWLBS0000E: An unexpected runtime exception has occured.
- Explanation: This is an informational message. An unexpected runtime exception has occured. If there is more information on the cause of this error it is recorded in the application server logs.
- User Action: Check the log file(s) for more information on the cause of this error. You may also refer to Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/
- CWLBS0001E: Cannot create a logger for element:<{0}>, falling back to logger:<{1}>
- Explanation: This is an informational message. The element is part of an artifact with an unsupported name structure. There may be missing events in the server log due to misconfiguration.
- User Action: Check that the Websphere Application Server logging mechanism is working. You may also refer to Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/
- CWLBS0002E: Cannot create logger name for event point:<{0}>.
- Explanation: This is an informational message. The event point is part of an artifact with an unsupported name structure. There may be missing events in the server log due to misconfiguration.
- User Action: Check that the Websphere Application Server logging mechanism is working. You may also refer to Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/
- CWLBS0003E: Cannot initialize event point <{0}><{1}>.
- Explanation: This is an informational message. The event point will not be functional. There may be missing events due to misconfiguration.
- User Action: Check the log file(s) for more information on the cause of this error. You may also refer to Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/
- CWLBS0004E: Cannot fire event from:<{0}> nature:<{1}>.
- Explanation: This is an informational message. The event point could not fire an event of the specified nature. There may be missing events due to misconfiguration.
- User Action: Check the log file(s) for more information on the cause of this error. You may also refer to Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/
- CWLBS0004W: The EventSource name is invalid.
- Explanation: There is an invalid EventSource specified.
- User Action: Please consult the monitor.xsd file for information on correctly formatting attributes.
- CWLBS0005E: Failed to create static monitor <{0}><{1}>.
- Explanation: The runtime encountered an unexpected error while loading the .mon file for the specified component.
- User Action: Check the deployed application monitoring specification (.mon file) for errors.
- CWLBS0005W: The EventSource element name has an invalid value.
- Explanation: The EventSource element name does not contain a valid value.
- User Action: Redefine the attribute with a non-negative integer.
- CWLBS0006E: Logger created event point logger <{0}>, bundle<{1}> not found.
- Explanation: This is an informational message. Cannot find the resource bundle with the specified name. Log messages may not contain locale specific information.
- User Action: No action is required.
- CWLBS0006W: EventSource {0} either does not exist, or has multiple occurrences in the monitored artifact.
- Explanation: The EventSource is specified incorrectly.
- User Action: Define an EventSource that is unique for the artifact.
- CWLBS0007E: The kind(componentTypeQName) component is either invalid or not supported.
- Explanation: The kind(componentTypeQName) component is either invalid or not supported.
- User Action: Please check your monitor kind component type.
- CWLBS0008E: The monitoring event specification, usually found in the .mes file, does not exist.
- Explanation: Unable to find your monitoring event specification.
- User Action: Please check your monitoring event specification (.mes)
- CWLBS0008W: Cannot find the monitoring event specification (.mes) for the component type <{0}>.
- Explanation: Cannot find the monitoring event specification for the specified component type, the specification should have been already loaded. This may be an unsupported component type.
- User Action: Check that the component specified in the monitoring specification is a valid monitorable component. If the component type is valid and the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/
- CWLBS0009W: The monitoring specification <{0}> of type <{1}> refers to a non-valid element type <{2}>.
- Explanation: This is an informational message. The monitoring specification refers to an element type that is not declared by the monitoring event specification (.mes file) for the component type.
- User Action: A monitoring specification used was not valid, please fix the monitoring specification. If the monitoring specification is valid and the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/
- CWLBS0010W: Event Nature {0} is invalid. The monitored artifact does not exist.
- Explanation: Unable to find your monitored artifact.
- User Action: Please check your project.
- CWLBS0011W: The artifact loader aborted the search for the artifact type <{0}> name <{1}> scope <{2}>.
- Explanation: The artifact specified cannot be found and the search ended abnormally.
- User Action: Check that all of the application schemas (.xsd files) have been deployed and that the server started successfully. You may also refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/
- CWLBS0012E: The monitoring service component of this server has been disabled.
- Explanation: This is an informational message. During installation the configuration of this server has disabled the activation of the monitoring service. As a result, monitoring will not log events.
- User Action: Please enable MonitorCoreService in server-core.xml.
- CWLBS0013E: The events service for monitoring component of this server has been disabled.
- Explanation: The events service has been disabled, As a result, customer can not fire the cbe into cei db.
- User Action: Please enable events service in server-core.xml.
- CWLBS0014E: The sessionmonitored for monitoring component has been disabled.
- Explanation: The sessionmonitored has been disabled, As a result, the customer can not fire the cbe correlated session monitored.
- User Action: Please enable sessionMonitored in server-core.xml.
- CWLBS0015E: The monitored BRG/SEL cannot be found.
- Explanation: Unable to find your monitored BRG/SEL
- User Action: Please check your project.
- CWLBS0016E: The monitor name is null.
- Explanation: You must enter a value for the name attribute.
- User Action: Consult the monitor.xsd file for information on defining names.
- CWLBS0017E: The monitor targetName is null.
- Explanation: You must enter a value for the targetName attribute.
- User Action: Consult the monitor.xsd file for information on defining target names.
- CWLBS0018E: Failed to load event schema file.
- Explanation: Failed to load event schema file.
- User Action: Please check the componentTypeQName.
- CWLBS0018W: The monitored map transformation {0} has multiple occurrences in the monitored artifact.
- Explanation: You may not define multiple occurences of a monitored artifact.
- User Action: Define a map transformation that is unique to the artifact.
- CWLBS0019W: Can not find the elementkind:<{0}> in the monitoring event specification (.mes).
- Explanation: The elementkind name is invalid, not defined in monitoring event specification (.mes).
- User Action: Please fix the elementkind name, make sure which is one valid elementkind.
- CWLBS0020E: Monitoring of the component kind {0} is not supported.
- Explanation: This type of component kind cannot be currently monitored.
- User Action: Refer to the list of supported components.
- CWLBS0021E: Monitored SCA component cannot be found.
- Explanation: Unable to find your monitored SCA component.
- User Action: Please check your workspace for required dependent projects.
- CWLBS0022E: Mon file does not conform to monitor.xsd, details:\n{0}.
- Explanation: Your monitoring specification is invalid.
- User Action: Refer to the monitor.xsd file for monitored schema definitions.
- CWLBS0023E: The monitored Business State Machine cannot be found.
- Explanation: Unable to find your monitored business state machine project.
- User Action: Please check your workspace for required dependent projects.
- CWLBS0024W: The event {0} transaction is different from others, Mixed transactions may impact event sequencing.
- Explanation: Having mixed transaction types for event points can have a potential impact to event sequencing resulting in unpredictable events ordering
- User Action: Please check the events transaction settings