- CWRES0005E: After processing a message, the event sequencing run time failed to start work for the next message waiting for the lock. The error is {0}.
- Explanation: The cause of the problem might be that the event sequencing run time application persistentLkMgr is not available or Work Manager es-workmanager failed to process work.
- User Action: Check the logs for the cause of the problem. If the persistentLkMgr application is not started, use the administration console to start it. Otherwise restart the event sequencing application to resume processing.
- CWRES0011E: The connection to the messaging infrastructure cannot be created. The exception is {0}.
- Explanation: The cause of the problem might be that if security is turned on, the user credentials are incorrect or the user does not have authority to connect to the Service Component Architecture (SCA) system bus. If security is off, this error indicates messaging infrastructure failure.
- User Action: Verify the user credentials in J2C authentication alias SCA_Auth_Alias. Check the logs for the cause of the messaging infrastructure failure. After fixing the messaging errors, restart the event sequencing applications.
- CWRES0012E: The event sequencing service for the application {0} did not start. The exception is {1}.
- Explanation: The cause of the problem might be that the event sequencing run time application persistentLkMgr is not available or the messaging infrastructure failures occured.
- User Action: Check the logs for the cause of the problem. If the persistentLkMgr application is not started, use the administration console to start it. Otherwise restart the event sequencing application.
- CWRES0013E: The event sequencing runtime failed to process the message with msgId={0}. The exception is {1}.
- Explanation: The cause of the problem might be that the event sequencing run time application persistentLkMgr is not available or failures occurred in the messaging infrastructure or the Work Manager es-workmanager failed to process work. Due to this failure, the message will be retried up to the configured maximum retries. After all of the retries, the message will be moved to the failed event destination, and the next message waiting for the lock will be processed.
- User Action: Check logs for failure reasons. Since this error is due to basic infrastructure failure, potentially all subsequent messages will fail due to same reason. Therfore, address the infrastructure failures and then restart the event sequencing applications. The failed messages can be resubmitted from the administartion console.
- CWRES0014E: The message with msgHandle={0} cannot be retrieved from the destination {1}.
- Explanation: The event sequencing run time is trying to process a message that cannot be read from the message destination. A possible reason is that user might have accidently deleted the message from destination.
- User Action: Verify if the message is available on destination. If it is not available, use the command 'esAdmin unlock <lockid>' to start processing remaining messages. If it is available, check the logs for any messaging errors that resulted in failure to read the message. After fixing the errors, restart the application.
- CWRES0015E: The message with msgId={0} failed during processing. The error is {1}.
- Explanation: The possible reason is that invocation of the target component failed. The message will be retried up to the configured maximum retries. After all of the retries, the message will be moved to the failed event destination and the next message waiting for the lock will be processed.
- User Action: If more messages fail, check the logs for messaging or other infrastructure-related errors and correct them. The failed messages can be resubmitted from the administartion console.
- CWRES0016E: The message with msgId={1} and the transaction will be rolled back. The exception is {0}.
- Explanation: The possible reason is that invocation of the target component failed. The message will be retried up to the configured maximum retries. After all of the retries, the message will be moved to the failed event destination and the next message waiting for the lock will be processed.
- User Action: If more messages fail, check the logs for messaging or other infrastructure-related errors and correct them. The failed messages can be resubmitted from the administartion console.
- CWRES0017E: The transaction rollback for message msgId={1} failed. The exception is {0}.
- Explanation: The possible reason is that invocation of the target component failed. The message will be retried up to the configured maximum retries. After all of the retries, the message will be moved to the failed event destination and the next message waiting for the lock will be processed.
- User Action: If more messages fail, check the logs for messaging or other infrastructure-related errors and correct them. The failed messages can be resubmitted from the administartion console.
- CWRES0018W: The input does not contain the object {0}. The event sequencing run time will not use the key specifications for it.
- Explanation: The object specified in the event sequencing key specifications is missing from the input message. The event sequencing run time will use rest of the key specifications to determine its key.
- User Action: Ensure that you intended to use objects in event sequencing key specifications that might not be present at run time.
- CWRES0019E: The event sequencing work item was not created because consumer session can not be established with message destination on the Service Component Architecture (SCA) system bus.
- Explanation: After processing a message, the event sequencing service cannot start work for the next message waiting for the lock. The cause of the problem might be that the messaging engine on Service Component Architecture (SCA) system bus is not available or the event sequecning application is not running.
- User Action: Check the logs for details. Ensure that the messaging engine on Service Component Architecture (SCA) system bus and the event sequencing application are running.
- CWRES0020W: The message with the sequencing context {0} failed during processing. The error is {1}.
- Explanation: This is a warning message. The cause of the problem might be that the event sequencing run time application persistentLkMgr is not available or Work Manager es-workmanager failed to process work or other infrastructure errors occured. The event sequencing runtime will keep trying to process the message.
- User Action: Check the logs for the cause of the problem. If the persistentLkMgr application is not started, use the administration console to start it. Otherwise try to address the infrastructure errors.
- CWRES0021I: The event sequencing deployment task has started for the application {0}.
- Explanation: This is an informational message. The event sequencing task is performing configuration actions while deploying the specified application with an event sequencing qualifier.
- User Action: No action is required.
- CWRES0022I: The event sequencing deployment task completed successfully for the application {0}.
- Explanation: This is an informational message. The event sequencing task completed the configuration actions for deploying the specified application with an event sequencing qualifier.
- User Action: No action is required.
- CWRES0023E: The event sequencing deployment task failed for the application {0}. The error is {1}.
- Explanation: The application deployment with an event sequencing qualifier failed to perform the event sequencing tasks because of the specified error.
- User Action: Check the log for details of error message. Enable tracing with the level set to com.ibm.wbiserver.sequencing.*=all, then deploy the application again. If the problem persists, see the Troubleshooting guide on the WebSphere Process Server Support page at http://www.ibm.com/software/integration/wps/support.
- CWRES0024W: The message with msgId={0} has expired. The next message in the queue will be granted the lock.
- Explanation: This is an informational message. The message was not delivered to target component because it expired. The next message waiting for the lock will be processed.
- User Action: No action is required.
- CWRES0027W: The Event Sequencing service was unable to find a blocking sequenced event lock.
- Explanation: The delete operation was called on a Failed Event that is related to a blocking sequence of Event Sequenced events. The Event Sequencing lock related to this Failed Event was not found.
- User Action: Check that the sequence related to this deleted event has been restarted by using the esAdmin utility.