WebSphere Process Server messages     Operating Systems: All supported

CWRLS

CWRLS0001I: The Recovery Log Service has been suspended ({0}).
Problem The Recovery Log Service has been placed into pending state in order to allow the system to backup the recovery log files.
User response No action is required by the user.
CWRLS0002I: The Recovery Log Service has been resumed ({0}).
Problem The previously suspended Recovery Log Service has been restored to running state.
User response No action is required by the user.
CWRLS0003E: {0}
Problem This message code is used to support messages that have not yet been allocated their own message code.
User response Refer to the message text for more information.
CWRLS0004E: Unable to create recovery log file {0}.
Problem The Recovery Log Service was unable to create the file indicated in the message. Either the target directory is inaccessible or the system does not have sufficient permissions to create the required file.
User response Ensure the required directory hierarchy is valid and accessible to the Recovery Log Service.
CWRLS0005E: Unable to obtain an exclusive file lock on {0}.
Problem The Recovery Log Service was unable to exclusively lock the file indicated in the message.
User response Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support.
CWRLS0006I: Creating new recovery log file {0}.
Problem A new recovery log file has been established in order to store persistent data.
User response No action is required by the user.
CWRLS0007I: No existing recovery log files found in {0}. Cold starting the recovery log.
Problem Either previously recovery log files have been deleted or this is the first time recovery log files have been stored in this location. In either case, the associated service will start and perform no recovery processing
User response No action is required by the user.
CWRLS0008E: Recovery log is being marked as failed. [ {0} {1} ]
Problem The recovery log has failed, and not further access to the recovery log can occur. The component is indicated in the message along with the exception taken.
User response The server must be restarted so that the log can be repaired. Attempt to fix any conditions indicated by the exception in the message. If the problem persists, please contact IBM Support.
CWRLS0009E: Details of recovery log failure: {0}
Problem This message is issued with message CWRLS0008E to indicate the details of the recovery log failure.
User response Use the information in this message along with message CWRLS0008E to correct whatever condition caused the recovery log to fail.
CWRLS0010I: Performing recovery processing for local WebSphere server ({0}).
Problem The recovery log service is directing recovery processing of associated client services.
User response No user action is required.
CWRLS0011I: Performing recovery processing for a peer WebSphere server ({0}).
Problem The recovery log service is directing recovery processing of associated client services for the peer server.
User response No user action is required.
CWRLS0012I: All persistent services have been directed to perform recovery processing for this WebSphere server ({0}).
Problem The recovery log service has prompted all associated client services to begin recovery.
User response No user action is required.
CWRLS0013I: All persistent services have been directed to perform recovery processing for a peer WebSphere server ({0}).
Problem The recovery log service has prompted all associated client services to begin recovery for the peer server.
User response No user action is required.
CWRLS0014I: Halting any current recovery processing for a peer WebSphere server ({0}).
Problem Recovery processing is being transferred to an alternate WebSphere server. Typically, this occurs when a server is restarted and retakes ownership of its recovery logs.
User response No action is required by the user.
CWRLS0015I: Recovery log file locking has been disabled in the transaction service custom properties.
Problem The file locking mechanism used by the recovery log service to ensure exclusive access to recovery log files has been explicitly disabled.
User response Ensure the appropriate constraints are in place to support this configuration setting.
CWRLS0016E: Unable to obtain an exclusive file lock needed to perform recovery processing for server {0}.
Problem Either the target server is active or the recovery log configuration is incorrect.
User response Ensure that recovery log configuration is valid. If you are unable to correct the problem, please contact IBM support.
CWRLS0017I: An attempt to obtain an exclusive file lock needed to perform recovery processing for server {0} was interrupted. Another server is being activated to perform this recovery processing.
Problem This message indicates that control of a recovery log has been passed between to WebSphere servers.
User response No action is required by the user.
CWRLS0018E: An attempt to halt transactional recovery and forward processing for the local server ({0}) has been aborted.
Problem The recovery log service has prevented the local server relinquishing control of its own recovery logs. This may be due to inappropriate Core group policy configuration.
User response Ensure that the policy configuration does not assign ownership of an active server's recovery log to an alternate server.
CWRLS0019I: The Recovery Log Service has been configured as snapshot safe in the transaction service custom properties.
Problem If a snapshot of the log files is taken then the this snapshot will be consistent with other system state.
User response No user action is required.
CWRLS0020W: The Recovery Log Service has NOT been configured as snapshot safe in the transaction service custom properties.
Problem If a snapshot of the log files is taken then the this snapshot may not be consistent with other system state.
User response No user action is required.
CWRLS0021I: The Recovery Log Service has been called to resume ({0}) but there are other outstanding suspends.
Problem The Recovery Log Service will be resumed only when there are no outstanding suspends.
User response No action is required by the user.
CWRLS0022I: A Recovery Log Service suspend operation has timed out ({0}).
Problem If there are no outstanding suspend operations the Recovery Log Service will resume.
User response No action is required by the user.
CWRLS0023I: The Recovery Log Service has been resumed following the timeout of a suspend operation.
Problem Informational.
User response No action is required by the user.
CWRLS0024E: Exception caught during recovery! {0}
Problem An exception was caught whilst attempting to recover from a previous server failure.
User response Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support.
CWRLS0025E: Server recovery mode startup is not compatible with HA enablement.
Problem In a High Availability configuration, server recovery may be automatically initiated on a peer server.
User response Do not attempt to start a HA enabled server in recovery mode.
CWRLS0026W: Unable to obtain an exclusive file lock on {0} - retrying.
Problem The Recovery Log Service was unable to exclusively lock the file indicated in the message during recovery as the file appears to be in use. The recovery service will continue to periodically attempt to gain the exclusive lock so that recovery can proceed. If the recovery log file is one of the main server recovery logs, then startup will be suspended until access to the logs is possible. If the recovery log file belongs to another peer server, then another server may gain the locks and peer recover - in which case this server will stop retrying to recover.
User response Examine any related messages in order to determine the cause of the problem. If there are no related messages check the location of the recovery logs and ensure they are not being accessed by another server. For instance, this condition could occur if more than one server was accidentally configured to use another server's recovery logs.
CWRLS0027W: Common transaction log directory {0} has been defined for servers {1} and {2}
Problem Transaction logs from two servers are using a common directory configuration. This may possibily lead to recovery lock contention or a failure of data integrity.
User response Configure separate log directory paths for each server.
CWRLS0028W: Common compensation log directory {0} has been defined for servers {1} and {2}
Problem Compensation logs from two servers are using a common directory configuration. This may possibily lead to recovery lock contention or a failure of data integrity.
User response Configure separate log directory paths for each server.
CWRLS0029W: Unable to perform recovery processing for local WebSphere server - server being terminated
Problem The Recovery Log Service is unable to perform or complete recovery for the local server and no further work can proceed, so the server is being terminated.
User response Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support.
CWRLS0030W: Waiting for HAManager to activate recovery processing for local WebSphere server
Problem The Recovery Log Service is unable to initiate recovery processing for the local server as it is waiting for the HAManager to activate group membership for this local server's recovery logs.
User response Examine any related messages in order to determine the cause of the problem. If there are no related messages check the configuration of the DefaultCoreGroup settings and associated policy definitions for the recovery log service for the server. For instance, if the Clustered TM policy has been set to not support fail back, then another server may have a hold onto the logs and will stop this server from being activated.
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.recoverylog.resources.RecoveryLogMsgs.html

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