IBM BPM, V8.0.1, All platforms > Reference > Business Process Management messages > Business Monitor messages

CWMRT

CWMRT messages are IBM Business Monitor server messages.

They are divided as follows:

• Runtime [0000–3400]
• Bootstrap [6000–6400]
• Lifecycle [7000–7400]
• Cross-cell [7900–7999]

• CWMRT0019E
  Unable to verify locked messages. Queue Name: 1 Caused by: 0
• CWMRT0020E
  Error deserializing event. Caused by: 0
• CWMRT0026E
  Unable to signal queue draining completion. Caused by: 0
• CWMRT0030E
  An error while processing events. Monitor will attempt to retry. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0031E
  Locked messages are present on the queue. Monitor will wait until no locked messages are present. Monitoring Model ID: 0 Monitoring Model Version: 1 Queue Name: 2
• CWMRT0032E
  Unable to stop the consumer daemon. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0033E
  Unable to stop the readiness timer. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0034E
  Unable to stop the issuing timer. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0035E
  Unable to leave the High Availability Group. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0036E
  Unable to send CBE for locked message resolution error. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0038E
  Error rebuilding the fragment cache. It will be retried. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0039E
  An error occurred while processing events. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0040E
  An error occurred while trying to close a JMS Queue Connection. Monitor will continue, but connections may be leaking. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0041E
  An error occurred while trying to process a fragment. The fragment will be retried in 0 milliseconds. Monitoring Model ID: 1 Monitoring Model Version: 2 Hierarchy Instance ID: 3 Caused by: 4
• CWMRT0042E
  An error occurred while enqueuing a processing request. The fragment will be retried in 0 milliseconds. Monitoring Model ID: 1 Monitoring Model Version: 2 Hierarchy Instance ID: 3 Caused by: 4
• CWMRT0043E
  An error occurred while issuing time based triggers. Monitor will retry at the next scheduled interval. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0044E
  An unrecognized error occurred while processing an event. The message will be retried. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0047E
  An error occurred while trying persist an event. Monitor will rollback the transaction and attempt to consume the message again. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0048E
  An error occurred while submitting a fragment to the failed event manager. The fragment will be retried in 0 milliseconds. Monitoring Model ID: 1 Monitoring Model Version: 2 Hierarchy Instance ID: 3 Caused by: 4
• CWMRT0049E
  An error occurred while submitting a fragment to the failed event manager. Monitoring Model ID: 0 Monitoring Model Version: 1 Hierarchy Instance ID: 2 Caused by: 3
• CWMRT0051E
  Hierarchy Instance ID not found. Monitoring Model ID: 0 Monitoring Model Name: 1 Monitoring Model Version: 2 Context ID: 3 Context Name: 4 Inbound Event ID: 5 Inbound Event Name: 6 Expression: 7 Event ID: 8 Caused By: 9
• CWMRT0052E
  Event Sequence Index not found. Monitoring Model ID: 0 Monitoring Model Name: 1 Monitoring Model Version: 2 Context ID: 3 Context Name: 4 Inbound Event ID: 5 Inbound Event Name: 6 Expression: 7 Event ID: 8 Caused by: 9
• CWMRT0053E
  Could not deserialize the event from the message.
• CWMRT0054E
  Could not retrieve the hierarchy instance ID from the event.
• CWMRT0055E
  Could not retrieve the event sequence number from the event.
• CWMRT0056E
  Parsing event failed unexpectedly. Caused by: 0
• CWMRT0057E
  An error occurred while submitting an unrecoverable event to the unrecoverable event manager. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0058E
  Canceling this time based trigger evaluation after 0 errors out of 1 total updates. The MM will retry time based trigger evaluation in about 4 seconds. Monitoring Model ID: 2 Monitoring Model Name: 3
• CWMRT0059E
  A non-processing error occurred while issuing time based triggers. Monitor will retry at the next scheduled interval. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0060E
  A non-processing error occurred while to process a fragment. The fragment will be retried in 0 milliseconds. Monitoring Model ID: 1 Monitoring Model Version: 2 Hierarchy Instance ID: 3 Caused by: 4
• CWMRT0061E
  A non-processing error occurred while processing events. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0062E
  Error retrieving fragment entries. Caused by: 0
• CWMRT0063E
  Error deleting fragment entries. Caused by: 0
• CWMRT0064E
  Error persisting fragment entries. Caused by: 0
• CWMRT0065E
  An error has occurred while accessing CEI. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0066E
  An error occurred while enqueuing a fragment cache insertion request. The fragment will be retried in 0 milliseconds. Monitoring Model ID: 1 Monitoring Model Version: 2 Hierarchy Instance ID: 3 Caused by: 4
• CWMRT0067E
  An error occurred trying to receive the KPI data bean from KPI access. Monitoring Model ID: 0 Monitoring Model Version: 1 KPI Context Name: 2 KPI Context ID: 3 KPI Name: 4 KPI ID: 5 Caused by: 6
• CWMRT0068E
  An error occurred trying to refresh the KPI data bean from KPI access. Monitoring Model ID: 0 Monitoring Model Version: 1 KPI Context Name: 2 KPI Context ID: 3 KPI Name: 4 KPI ID: 5 Caused by: 6
• CWMRT0069E
  An error occurred trying to initialize the KPI Access API. Monitoring Model ID: 0 Monitoring Model Version: 1 KPI Context Name: 2 KPI Context ID: 3 Caused by: 4
• CWMRT0070E
  An error occurred trying to receive the KPI range data bean from KPI access. Monitoring Model ID: 0 Monitoring Model Version: 1 KPI Context Name: 2 KPI Context ID: 3 KPI Name: 4 KPI ID: 5 KPI Range Name: 6 KPI Range ID: 7 Caused by: 8
• CWMRT0071E
  A hard exception occurred during processing. The event will be retried. Monitoring Model ID: 0 Monitoring Model Version: 1 Context ID: 2 Root Instance ID: 3 Context Instance ID: 4 Server: 5 Event ID: 6 Caused By: 7
• CWMRT0072E
  A hard exception occurred during processing. The event will be put on the Error Queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Context ID: 2 Root Instance ID: 3 Context Instance ID: 4 Server: 5 Event ID: 6 Caused By: 7
• CWMRT0073E
  The required metric has not been given a value. The new instance will not be stored in the database. Monitoring Model ID: 0 Monitoring Model Version: 2 Metric database column ID: 4
• CWMRT0074E
  An event was received out of order. The event will be put on the failed event queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Root Instance ID: 2 Current Event ID: 3 Current Event Sequence Index: 4 Prior Event Sequence Index: 5
• CWMRT0075E
  Error updating fragment entries. Caused by: 0
• CWMRT0076E
  Error persisting event sequence indices. Caused by: 0
• CWMRT0077E
  Error retrieving event sequence indices. Caused by: 0
• CWMRT0078E
  Error updating event sequence indices. Caused by: 0
• CWMRT0079E
  Error deleting event sequence indices. Caused by: 0
• CWMRT0080E
  Error persisting unique ID. Caused by: 0
• CWMRT0081E
  Error retrieving unique ID. Caused by: 0
• CWMRT0082E
  Error updating unique ID. Caused by: 0
• CWMRT0083E
  Error deleting unique ID. Caused by: 0
• CWMRT0084E
  Error persisting recorded event. Caused by: 0
• CWMRT0085E
  Error retrieving recorded event. Caused by: 0
• CWMRT0086E
  Error updating recorded event. Caused by: 0
• CWMRT0087E
  Error deleting recorded event. Caused by: 0
• CWMRT0088E
  An error occurred while setting a metric. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Metric Name: 5 Metric ID: 6 Expression: 7 Event ID: 8 Caused by: 9
• CWMRT0090E
  An error occurred while changing a counter value. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Counter Name: 5 Counter ID: 6 Action: 7 Event ID: 8 Caused by: 9
• CWMRT0091E
  An error occurred while changing a stopwatch state. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Stopwatch Name: 5 Stopwatch ID: 6 Action: 7 Event ID: 8 Caused by: 9
• CWMRT0092E
  An error occurred while executing a trigger. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Trigger Name: 5 Trigger ID: 6 Event ID: 7 Caused by: 8
• CWMRT0093E
  An error occurred while initializing execution for an inbound event. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Inbound Event Name: 5 Inbound Event ID: 6 Event ID: 7 Caused by: 8
• CWMRT0094E
  An error occurred while correlating instances. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8 Caused by: 9
• CWMRT0095W
  No instances were found for this event. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8
• CWMRT0096E
  One instance was found for this event. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8 Instance ID: 10
• CWMRT0097E
  Multiple instances were found for this event. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8 Instance IDs: 10
• CWMRT0098E
  No parent instance was found for this event. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8
• CWMRT0099E
  Multiple parent instances were found for this event. No related events will be processed until this event is successfully processed. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8 Instance IDs: 10
• CWMRT0113E
  Unable to start the ConsumerDaemon. The MM will attempt to fail over. If it is not in a cluster, stop this application and troubleshoot. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused By: 2
• CWMRT0115E
  An error while processing events. The MM can NOT recover. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0116E
  Unable to join the High Availability Group. Monitoring Model ID: 0 Monitoring Model Version: 1 HA Group: 2 Caused by: 3
• CWMRT0118E
  The fragment cache inserter has failed. Attempting to shut down the application. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0119E
  Unable to determine if this MM application is allowed to start. The application will NOT be started. Monitoring Model ID: 0 Monitoring Model Version: 1 Caused by: 2
• CWMRT0120E
  This MM application has encountered a fatal error during processing. Processing CANNOT continue on this application server or cluster member. Exiting the HA Group to force failover to another application server or cluster member. Monitoring Model ID: 0 Monitoring Model Version: 1
• CWMRT0202E
  The maximum number of no correlation match retries for a given event has been exceeded. This event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8
• CWMRT0203E
  A null value was received for a required metric. The metric will not be changed to null. This could be an error or just indicate that no value was found during event processing for this metric. In certain modes, this event and related events can be managed from the error queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Metric Name: 5 Metric ID: 6 Expression: 7 Event ID: 8
• CWMRT0204E
  Error during initial filtering of event. Monitoring Model ID: 0 Monitoring Model Name: 1 Monitoring Model Version: 2 Context ID: 3 Context Name: 4 Inbound Event ID: 5 Inbound Event Name: 6 Filter Expression: 7 Event ID: 8 Caused By: 9
• CWMRT0205E
  Unable to locate a target MM version for the MC instance transfer. Monitoring Model ID: 0 Monitoring Model Version: 1 BPEL Process Template Name: 3 BPEL Process Template Valid From: 4 Event ID: 2
• CWMRT0206E
  The maximum time to wait for an MC instance to be transferred has been exceeded. Monitoring Model ID: 0 Monitoring Model Version: 1 Hierarchy Instance ID: 2 Caused by: 3
• CWMRT0207E
  A transfer event was resubmitted, but the MC instance has not yet been transferred. Monitoring Model ID: 0 Monitoring Model Version: 1 Hierarchy Instance ID: 2
• CWMRT0208E
  Could not evaluate the XPath expressions against the incoming event.
• CWMRT0209E
  XPath expression evaluation failed on this event. Monitoring Model ID: 0 Monitoring Model Version: 1 Hierarchy Instance ID: 2 Event ID: 3 Caused by: 4
• CWMRT0210E
  Error accessing the MM database tables. Caused by: 0
• CWMRT0211E
  Error while handling a moderator controller state. Caused by: 0
• CWMRT0212E
  Error while handling a moderator agent state. Caused by: 0
• CWMRT2001W
  Registration with the FFDC system was previously done, duplicate registration request. Continuing.
• CWMRT2002W
  Registration with the FFDC system was not successful, DiagnosticModule did not meet the criteria to contain a single dump method. Continuing.
• CWMRT2003W
  Registration with the FFDC system was not successful, an Unknown error occurred. Continuing.
• CWMRT2005W
  Unsupported event notification type: 0
• CWMRT2006W
  The consumer daemon was unexpectedly awakened. Caused by: 0
• CWMRT2007W
  It took more than a third of the time based triggers check interval to evaluate the time based triggers. This might cause a performance degradation. Monitoring Model ID: 0 Monitoring Model Version: 1 Execution Time (so far): 2
• CWMRT2009W
  The MM application is not in a startable state. This is usually because lifecycle steps are not complete. Monitoring Model ID: 0 Monitoring Model Version: 1 Reason: 2
• CWMRT2010W
  A request was made to resume the already running root instance with ID " 0".
• CWMRT2011W
  2 events were found waiting to be processed. This is larger than 3, the configured maximum number of events to cache. This Monitoring Model version will force itself into pass by reference to limit memory footprint. Monitoring Model ID: 0 Monitoring Model Version: 1
• CWMRT2012W
  The maximum number of events to cache, 2, has been reached. This Monitoring Model version will not consume any more messages for 3 seconds to limit memory footprint. Monitoring Model ID: 0 Monitoring Model Version: 1 Number of Events in Fragment Cache: 4
• CWMRT2013W
  The KPI value is null. This could be an error or just indicate that no metrics for this KPI have been processed. Monitoring Model ID: 0 Monitoring Model Version: 1 KPI Context Name: 2 KPI Context ID: 3 KPI Name: 4 KPI ID: 5 Caused by: 6
• CWMRT2014W
  The KPI target value is null. The KPI target value was used to evaluate an expression. No target value was set, therefore null will be used. Monitoring Model ID: 0 Monitoring Model Version: 1 KPI Context Name: 2 KPI Context ID: 3 KPI Name: 4 KPI ID: 5 Caused by: 6
• CWMRT2015W
  The KPI range value is null. The KPI range value was used to evaluate an expression. No range value was set, therefore null will be used. Monitoring Model ID: 0 Monitoring Model Version: 1 KPI Context Name: 2 KPI Context ID: 3 KPI Name: 4 KPI ID: 5 Caused by: 6
• CWMRT2016W
  Unsupported database management system detected. Reference number: 0 JNDI Name: 1 Schema: 2
• CWMRT2017W
  A null value was received for a required metric. The metric will not be changed to null. This monitoring context instance will continue processing the current event. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Metric Name: 5 Metric ID: 6 Expression: 7 Event ID: 8
• CWMRT2019W
  The maximum number of events to reorder, 2, has been reached. This Monitoring Model version will not consume any more messages for 3 seconds to limit memory footprint. Monitoring Model ID: 0 Monitoring Model Version: 1 Number of Events in Fragment Cache: 4
• CWMRT2020W
  The maximum number of no correlation match retries for a given event has been exceeded. It will be treated as a no correlation match exception. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8
• CWMRT2021W
  An error occurred while setting a metric. This monitoring context instance will continue processing the current event. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Metric Name: 5 Metric ID: 6 Expression: 7 Event ID: 8 Caused by: 9
• CWMRT2023W
  An error occurred while changing a counter value. This monitoring context instance will continue processing the current event. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Counter Name: 5 Counter ID: 6 Action: 7 Event ID: 8 Caused by: 9
• CWMRT2024W
  An error occurred while changing a stopwatch state. This monitoring context instance will continue processing the current event. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Stopwatch Name: 5 Stopwatch ID: 6 Action: 7 Event ID: 8 Caused by: 9
• CWMRT2025W
  An error occurred while executing a trigger. This monitoring context instance will continue processing the current event. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Trigger Name: 5 Trigger ID: 6 Event ID: 7 Caused by: 8
• CWMRT2026W
  An error occurred while initializing execution for an inbound event. This monitoring context definition will continue processing the current event with the next monitoring context instance. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Monitoring Context Instance ID: 4 Inbound Event Name: 5 Inbound Event ID: 6 Event ID: 7 Caused by: 8
• CWMRT2027W
  An error occurred while correlating instances. This monitoring model will continue processing the current event with the next monitoring context definition. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8 Caused by: 9
• CWMRT2028W
  No instances were found for this event. This monitoring model will continue processing the current event with the next monitoring context definition. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8
• CWMRT2029W
  One instance was found for this event. This monitoring model will continue processing the current event with the next monitoring context definition. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8 Instance ID: 10
• CWMRT2030W
  Multiple instances were found for this event. This monitoring model will continue processing the current event with the next monitoring context definition. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8 Instance IDs: 10
• CWMRT2031W
  No parent instance was found for this event. This monitoring model will continue processing the current event with the next monitoring context definition. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8
• CWMRT2032W
  Multiple parent instances were found for this event. This monitoring model will continue processing the current event with the next monitoring context definition. Monitoring Model ID: 0 Monitoring Model Version: 1 Monitoring Context Name: 2 Monitoring Context ID: 3 Inbound Event Name: 4 Inbound Event ID: 5 Table Name: 6 Correlation Expression: 7 Event ID: 8 Instance IDs: 10
• CWMRT2034W
  A resubmitted event is ineligible for processing. This is usually because a previously resubmitted event failed during re-processing. This event can still be managed from the Failed Event Queue. Monitoring Model ID: 0 Monitoring Model Version: 1 Hierarchy Instance ID: 2 Failed Event Queue Index: 3
• CWMRT2035W
  XPath expression evaluation failed on this event. The MM will attempt to process this event anyway. Monitoring Model ID: 0 Monitoring Model Version: 1 Hierarchy Instance ID: 2 Event ID: 3 Caused by: 4
• CWMRT2036W
  Error deserializing event. Caused by: 0
• CWMRT2037W
  An event was received out of order. No action will be taken. Monitoring Model ID: 0 Monitoring Model Version: 1 Root Instance ID: 2 Current Event ID: 3 Current Event Sequence Index: 4 Prior Event Sequence Index: 5
• CWMRT3001I
  Registration with the FFDC system was successful
• CWMRT3003I
  The 0 message has occurred 1 times in the past 2 seconds. Further occurrences will be suppressed for the next 3 minutes.
• CWMRT3004I
  The 0 message has occurred 1 times in the past 2 minutes. Suppression ended.
• CWMRT3005I
  The Monitor Model " 0 1" (codegen: 5, library: 6) is activating on this application server or cluster member in 2 mode with reordering= 4 from 3: 7.
• CWMRT3006I
  The Monitor Model " 0 1" is stopping consumption on this application server or cluster member.
• CWMRT3007I
  The Monitor Model " 0 1" is waiting for 2 consumer threads to shut down.
• CWMRT3009I
  The Monitor Model " 0 1" is attempting to rejoin the HA group on this application server or cluster member.
• CWMRT3010I
  The Monitor Model " 0 1" confirmed no locked messages on queue " 2".
• CWMRT3011I
  Controller 0 detected a change to the pool of available agents.
• CWMRT3012I
  Controller 0 has not received a response from all agents. It will purge the non-responsive agents.
• CWMRT3013I
  Control 0 received acknowledgment from all agents.
• CWMRT3014I
  Controller 0 is telling Agent 1 to begin work on partitions 2 through 3, inclusive.
• CWMRT3015I
  Controller 0 is removing Agent 1 from the available pool.
• CWMRT3016I
  Controller 0 is telling Agent 1 to quiesce.
• CWMRT3017I
  Controller 0 took ownership of the agents.
• CWMRT3018I
  Agent 0 registered with controller.
• CWMRT3019I
  Agent 0 received a message from the controller.
• CWMRT3020I
  Agent 0 is quiescing.
• CWMRT3021I
  Agent 0 is beginning work on partitions 1 through 2, inclusive.
• CWMRT3022I
  Agent 0 has lost its lease. It will re-register.
• CWMRT6001I
  Created queue destination 0 on Service Integration Bus 1.
• CWMRT6002I
  Created JMS queue connection factory 0 on scope 1.
• CWMRT6003I
  Created JMS queue 0 on scope 1.
• CWMRT6004I
  Created work manager 0 on scope 1.
• CWMRT6005I
  Removed queue destination 0 from Service Integration Bus 1.
• CWMRT6006I
  Removed JMS queue connection factory 0 from scope 1.
• CWMRT6007I
  Removed JMS queue 0 from scope 1.
• CWMRT6008I
  Removed work manager 0 from scope 1.
• CWMRT6301E
  Error creating queue destination. Stopping the installation of the MM EAR. Scope: 1 DestinationInfo: 0 Caused by: 2
• CWMRT6302E
  Error creating JMS queue connection factory. Stopping the installation of the MM EAR. Scope: 1 QueueFactoryInfo: 0 Caused by: 2
• CWMRT6303E
  Error creating JMS queue. Stopping the installation of the MM EAR. Scope: 1 QueueInfo: 0 Caused by: 2
• CWMRT6304E
  CWMRT6304E: Error creating work manager. Stopping the installation of the MM EAR. Scope: 1 WorkManagerInfo: 0 Caused by: 2
• CWMRT6305E
  Error removing queue destination. Continuing the uninstallation of the MM EAR. Some resources may remain. Scope: 1 Destination Name: 0 Caused by: 2
• CWMRT6306E
  Error removing JMS queue connection factory. Continuing the uninstallation of the MM EAR. Some resources may remain. Scope: 1 JMS Queue Connection Factory Name: 0 Caused by: 2
• CWMRT6307E
  Error removing JMS queue. Continuing the uninstallation of the MM EAR. Some resources may remain. Scope: 1 JMS Queue Name: 0 Caused by: 2
• CWMRT6308E
  Error removing work manager. Continuing the uninstallation of the MM EAR. Some resources may remain. Scope: 1 Work Manager Name: 0 Caused by: 2
• CWMRT6310E
  The Monitor Bus, " 0", does not contain any Bus Members.
• CWMRT6311E
  Error getting Bus Memebers. Stopping the installation of the MM EAR. Bus Name: 0 Caused by: 1
• CWMRT6314E
  Invalid module target. The node, 0, does not have monitor installed. The Monitoring Model will not be installed.
• CWMRT6315E
  Invalid module target. One of the target nodes only has Monitor version 1 installed. The MM application is from version 0.
• CWMRT6701W
  An unknown database management system was detected. Reference number: 0 JNDI Name: 1 Schema: 2
• CWMRT6711E
  An error occurred while inserting an event. Schema: 0 Table: 1 Version: 2 Queue ID: 3 Caused by: 4
• CWMRT6712E
  An error occurred while retrieving an event. Schema: 0 Table: 1 Version: 2 Queue ID: 3 Caused by: 4
• CWMRT6713E
  An error occurred while updating an event. Schema: 0 Table: 1 Version: 2 Queue ID: 3 Caused by: 4
• CWMRT6714E
  An error occurred while deleting an event. Schema: 0 Table: 1 Deleting: 2 Caused by: 3
• CWMRT6721E
  Error while routing event. The transaction will be rolled back. Event Group: 0 Caused by: 1
• CWMRT6722E
  Error during initialization. Selector: 0 Caused by: 1
• CWMRT6731W
  Unable to load the requested filter class. Monitoring Model ID: 0 Monitoring Model Version: 1 Filter Class: 2 Caused By: 3
• CWMRT6732W
  Unable to find the requested filter class. Check to make sure the plug-in is resolved. Monitoring Model ID: 0 Monitoring Model Version: 1 Filter Class: 2
• CWMRT6733W
  Using the default filtering class. This means that all events will be distributed to the affect Monitoring Model. Monitoring Model ID: 0 Monitoring Model Version: 1
• CWMRT6741E
  Error creating persistence manager. JDBC JNDI: 0 Schema name: 1 Caused by: 2
• CWMRT6742E
  Error while routing event. The transaction will be rolled back. Event Group: 0 Caused by: 1
• CWMRT6773E
  Invalid event group selector for Event Recording. Expected: 1 Received: 0
• CWMRT7006I
  Automatic node synchronization succeeded.
• CWMRT7007I
  The WAS node " 1" does not support custom CEI selector strings. This means that Queue Bypass will be unavailable for this CEI target. Target CEI Scope: 0 WAS Node: 1 WAS Node Version: 2 Minimum Required WAS Level: 3
• CWMRT7008I
  The WAS node " 1" does not have the Monitor CEI routing plug-ins. This means that Queue Bypass and XPath2 selectors will be unavailable for this CEI target. Target CEI Scope: 0 WAS Node: 1
• CWMRT7009I
  The WAS cell " 0" does not have the " 1" data source. This means that Queue Bypass will be unavailable for this CEI target.
• CWMRT7010I
  The WAS cell " 0" does not have the " 1" bus. This means that JMS transport will be unavailable for this CEI target.
• CWMRT7011I
  The WAS target " 2" on node " 1" does not have a Monitor CEI routing plug-in resolved. This means that Queue Bypass and XPath2 selectors will be unavailable for this CEI target. Bundle Name: 3 Target CEI Scope: 0 WAS Node: 1 WAS Target: 2
• CWMRT7012I
  Monitor was unable to dynamically determine the Monitor CEI routing plugin status on the WAS target " 2" on node " 1" . Monitor will fall back to non-dynamic checking on this target. Target CEI Scope: 0 WAS Node: 1 WAS Target: 2 Caused by: 3
• CWMRT7013I
  The WAS cell " 0" does not have the " 1" foreign bus defined on the " 2" bus. This means that JMS transport will be unavailable for this CEI target.
• CWMRT7014I
  The monitoring model was generated with " 0", but the minimum level to use " 2" is " 1".
• CWMRT7101W
  Automatic node synchronization failed. Synchronize your node manually. Caused by: 0
• CWMRT7102W
  The detected version of CEI does not match recognized versions. Monitor will attempt to reload the CEI configuration. If it fails, an error message will be provided suggesting alternative actions. Detected CEI version: 0
• CWMRT7305E
  Event Group Profile List " 0" not found at the Cell Scope Cell: 1
• CWMRT7306E
  Event Group Profile List " 0" not found at the Node Scope Cell: 1 Node: 2
• CWMRT7307E
  Event Group Profile List " 0" not found at the application server scope Cell: 1 Node: 2 Server: 3
• CWMRT7308E
  Event Group Profile List " 0" not found at the Cluster Scope Cell: 1 Node: 2 Cluster: 4
• CWMRT7314E
  Error while trying to reload the CEI configuration. The process can be reattempted by calling the restartConfigureCEIDistribution(String modelID) method on the Lifecycle Services MBean. This will attempt to reload the configuration progammatically. The process can be completed manually by restarting your CEI application server (or cluster) and then calling the confirmCEIServerReboot(String modelID) on the Lifecycle Services MBean. Model ID: 0 Model Version: 1 CEI Scope: 2 Caused by: 3
• CWMRT7315E
  Error while trying to restart the CEI application. This application can be restarted from the wsadmin command line. Model ID: 0 Model Version: 1 Applications: 2 Caused by: 3
• CWMRT7316E
  MonitorAdminTaskForwarder MBean not available on the destination application server. Check the connection information and make sure that the necessary cross cell files have been extracted to the remote application server and the remote application server has been rebooted. Connection Information: 0
• CWMRT7317E
  The distribution type must be specified. Check to make sure the type of distribution selected is valid for the routing target. Model ID: 0 Model Version: 1 Distribution State: 2

Messages