WebSphere Process Server messages     Operating Systems: All supported

CWSID

CWSID0001I: Messaging engine {0} is initializing.
Problem The specified messaging engine is commencing initialization.
User response None.
CWSID0003E: An internal error occurred; reason: {0}
Problem An unexpected internal error occurred during system operation.
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/.
CWSID0006I: The SIB service was not enabled and will not be started.
Problem The SIB service has not been configured to start when the server process starts.
User response None, unless you want to enable the SIB service.
CWSID0007I: Messaging engine {0} is not enabled and will not be started.
Problem The specified messaging engine has been disabled by administrative action and will consequently not be started.
User response Start the messaging engine if required.
CWSID0008E: Configuration document {0} could not be loaded.
Problem The specified WCCM configuration document could not be loaded. This may cause other errors during runtime operation.
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/.
CWSID0009E: Destination {0} cannot be created.
Problem An error occurred when attempting to create the specified destination. If JACL scripts or custom JMX programs were used to create the configuration, check these for errors.
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/.
CWSID0011W: It is not possible to activate JMX {0} MBean named {1}.
Problem An error occurred attempting to activate a JMX MBean with the specified type and name. Although this does not prevent the messaging server from starting, it does mean that any administrative functions which require the existence of this MBean, may not function as expected.
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/.
CWSID0012W: It is not possible to deactivate JMX {0} MBean named {1}.
Problem An error occurred attempting to deactivate a JMX MBean with the specified type and name.
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/.
CWSID0013W: It is not possible to load class {0}.
Problem An error occurred attempting to load the specified class.
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/.
CWSID0014E: WCCM configuration error - an incorrect message point was found for UUID={0} with identifier={1}
Problem An integrity error was detected when reading the WCCM configuration documents. If JACL scripts or custom JMX programs were used to create the configuration, check these for errors.
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/.
CWSID0016I: Messaging engine {0} is in state {1}.
Problem The specified messaging engine has completed a stage of start/stop processing.
User response None.
CWSID0017I: Configuration reload is starting for bus {0}.
Problem Bus configuration file changes are being processed.
User response None.
CWSID0018I: Configuration reload is complete for bus {0}.
Problem All bus configuration file changes have been processed and all relevant destinations have been reloaded.
User response None.
CWSID0019I: Configuration reload is starting for messaging engine {0}.
Problem All messaging engine configuration documents are about to be checked for updates.
User response None.
CWSID0020I: Configuration reload is complete for messaging engine {0}.
Problem All messaging engine configuration documents have been read and updates have been processed.
User response None.
CWSID0021I: Configuration reload is enabled for bus {0}.
Problem The configuration document reloading has been enabled for the named bus.
User response None.
CWSID0022E: Destination {0} contains a Context property {1} with an invalid value {2} for type {3}.
Problem The configuration of the property is invalid.
User response Run configuration validation.
CWSID0023E: Destination Default for Foreign Bus {0} contains a Context property {1} with an invalid value {2} for type {3}.
Problem The configuration of the property is invalid.
User response Run configuration validation.
CWSID0024E: Mediation {0} contains a Context property {1} with an invalid value {2} for type {3}.
Problem The configuration of the property is invalid.
User response Run configuration validation.
CWSID0025I: SIB is not using the HAManager GroupManager service.
Problem The SIB messaging components are not using HAManager GroupManager service because the HA_DISABLED environment variable is defined.
User response If HA operation is wanted, then undefine the HA_DISABLED environment variable and restart the server.
CWSID0026W: Messaging engine {0} cannot be started from current state {1}.
Problem An attempt was made to start the specified messaging engine, but start is not a valid operation when the messaging engine is in the current state. This check prevents inadvertant manual start of a standby messaging engine in a cluster.
User response Check the state of the messaging engine and re-issue the operation when valid.
CWSID0027E: Messaging engine {0} cannot be restarted because a serious error has been reported.
Problem An attempt was made to start the specified messaging engine, but a serious error condition has previously been reported, so the messaging engine will not be restarted.
User response Restart the server or move the messaging engine to an alternate cluster server.
CWSID0028W: Messaging engine {0} cannot be stopped from current state {1}.
Problem An attempt was made to stop the specified messaging engine, but stop is not a valid operation when the messaging engine is in the current state.
User response Check the state of the messaging engine and re-issue the operation when valid.
CWSID0029E: Messaging engine {0} suffered a common mode error.
Problem The messaging engine detected an error that is likely to recur on an alternate server, so failover will not be attempted.
User response Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0030E: Messaging engine {0} suffered a common mode error and will be stopped.
Problem The messaging engine detected a common mode error and is being automatically stopped. No failover will be attempted.
User response Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0031E: Messaging engine {0} suffered a common mode error and has been stopped.
Problem The messaging engine detected a common mode error and was automatically stopped. No failover will be attempted.
User response Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0032W: An inconsistency in the WCCM document {0} was detected, for the message point {1}
Problem When reading the WCCM configuration document, an unexpected configuration was encountered.
User response The configuration is possibly invalid. Run WCCM validation to identify possible errors.
CWSID0033E: Messaging engine {0} cannot be initialized; caught exception thrown by {1} {2}
Problem An unexpected error occurred during engine initialization.
User response Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0034E: Messaging engine {0} cannot be started: caught exception thrown by {1} {2}
Problem An unexpected error occurred during engine initialization. The start phase is terminated and engine components that have already been started will be stopped.
User response Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0035E: Messaging engine {0} cannot be started; detected error reported during {1} {2}
Problem An error occurred when starting an engine component. No other engine components will be started.
User response Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0036E: Messaging engine {0} caught exception thrown by {1} {2} method during cleanup of failed start
Problem An error occurred when attempting to stop the messaging engine.
User response Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0037E: Messaging engine {0} caught exception thrown by {1} {2} method
Problem An error was detected by an engine component.
User response Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0038E: Messaging engine {0} could not join an HAManager group
Problem The messaging engine will not be able to run in this server.
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/.
CWSID0039E: HAManager-initiated activation has failed, messaging engine {0} will be disabled. Reason {1}
Problem The messaging engine did not activate, for the reason stated.
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/.
CWSID0040E: Messaging engine {0} could not report completion to HAManager. Server will be killed
Problem HAManager callback context was rejected, during the call to report completion of an asynchronous operation.
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/.
CWSID0041E: HAManager-initiated deactivation has failed, messaging engine {0} will be disabled. Reason {1}
Problem The messaging engine did not deactivate, for the reason stated.
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/.
CWSID0042E: Failed to create group name for messaging engine {0}
Problem The group name required by the messaging engine could not tbe created by HAManager.
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/.
CWSID0043W: It is not possible to send an Event Notification from JMX {0} MBean named {1}.
Problem An error occurred when attempting to send an Event Notification from a JMX MBean with the specified type and name. Although this does not prevent the continued operation of the messaging server, it does mean that this MBean cannot notify listeners of important messaging system events.
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/.
CWSID0044I: Messaging Engine {0} with UUID {1} has been started.
Problem The Messaging Engine is available for use.
User response None.
CWSID0045I: Messaging Engine {0} with UUID {1} has stopped.
Problem The Messaging Engine is no longer available for use.
User response None.
CWSID0046E: Messaging engine {0} detected an error and cannot continue to run in this server.
Problem The messaging engine is reporting the error to HAManager which will stop the server. With ND, the server will be restarted if the nodeagent is monitoring it. With an ND cluster, the messaging engine will failover to an alternate cluster server if the configured policy allows.
User response Check the logs to determine the cause of the error and correct it so that it does not recur. Either restart the server, or if using ND check that automatic restart/failover succeeded and the messaging engine is running.
CWSID0047W: Concurrent mediations have been disallowed on destination {0}.
Problem The destination is set to maintain message ordering. Therefore concurrent mediations are not allowed and have been disabled.
User response If ordering is not required, unset the maintainMessageOrder attribute to disable concurrent mediation override.
CWSID0048W: The value for receiveExclusive has been overriden to become "true", on destination {0}
Problem The destination is set to maintain message ordering. Therefore the value for the receiveExclusive attribute has been overriden to become "true".
User response If ordering is not required, unset the maintainMessageOrder attribute to disable receiveExclusive override.
CWSID9999E: {0}
Problem If the message does not give sufficient information, check previous messages for further help.
User response See previous messages for further information.
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.sib.admin.impl.CWSIDMessages.html

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