WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


CWSID

CWSID0001I: Messaging engine {0} is initializing.
Explanation The specified messaging engine is commencing initialization.
Action None.
CWSID0002I: Messaging engine {0} has started subcomponents.
Explanation The specified messaging engine has completed its initialization and all subcomponents have been started. Any errors occurring in those subcomponents will be reported as separate messages.
Action None.
CWSID0003E: An internal error occurred; reason: {0}
Explanation An unexpected internal error occurred during system operation.
Action None. This information will be used by IBM Software Support if necessary.
CWSID0005W: The initialization of the administration service failed with exception: {0}.
Explanation A problem occurred while initializing the administration service. Previous messages may contain information about the problem.
Action See previous messages for more information about the problem.
CWSID0006I: The SIB service was not enabled and will not be started.
Explanation The SIB service has not been configured to start when the server process starts.
Action None, unless you want to enable the SIB service.
CWSID0007I: Messaging engine {0} is not enabled and will not be started.
Explanation The specified messaging engine has been disabled by administrative action and will consequently not be started.
Action Start the messaging engine if required.
CWSID0008E: Configuration document {0} could not be loaded.
Explanation The specified WCCM configuration document could not be loaded. This may cause other errors during runtime operation.
Action Check whether the indicated document exists. Contact IBM Software Support.
CWSID0009E: Destination {0} cannot be created.
Explanation An error occurred when attempting to create the specified destination.
Action If JACL scripts or custom JMX programs were used to create the configuration, check these for errors. Otherwise, contact IBM Software Support.
CWSID0010E: WCCM Integrity error - message point found for UUID={0} with identifier={1} but destination did not.
Explanation An integrity error was detected when reading the WCCM configuration documents.
Action If JACL scripts or custom JMX programs were used to create the configuration, check these for errors. Otherwise, contact IBM Software Support.
CWSID0011W: It is not possible to activate JMX {0} MBean named {1}.
Explanation 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.
Action If this continues to occur, contact IBM Software Support.
CWSID0012W: It is not possible to deactivate JMX {0} MBean named {1}.
Explanation An error occurred attempting to deactivate a JMX MBean with the specified type and name.
Action If this continues to occur, contact IBM Software Support.
CWSID0013W: It is not possible to load class {0}.
Explanation An error occurred attempting to load the specified class.
Action This should not occur. Contact IBM Software Support.
CWSID0014E: WCCM configuration error - an incorrect message point was found for UUID={0} with identifier={1}
Explanation An integrity error was detected when reading the WCCM configuration documents.
Action If JACL scripts or custom JMX programs were used to create the configuration, check these for errors. Otherwise, contact IBM Software Support.
CWSID0015E: The messaging engine {0} cannot start in secure mode when WebSphere does not have security enabled.
Explanation The messaging engine cannot start because the bus in which it resides has been configured as secure. However, the WAS Server does not have Security enabled.
Action If appropriate, modify the configuration to enable WebSphere security, and restart the server.
CWSID0016I: Messaging engine {0} is in state {1}.
Explanation The specified messaging engine has completed a stage of start/stop processing.
Action None.
CWSID0017I: The bus configuration reload is starting.
Explanation Bus configuration file changes are being processed.
Action None.
CWSID0018I: The bus configuration reload is complete.
Explanation All bus configuration file changes have been processed and all relevant destinations have been reloaded.
Action None.
CWSID0019I: The messaging engine configuration reload starting.
Explanation All messaging engine configuration documents are about to be checked for updates.
Action None.
CWSID0020I: The messaging engine configuration reload is complete.
Explanation All messaging engine configuration documents have been read and updates have been processed.
Action None.
CWSID0021I: Configuration reload is enabled for bus {0}.
Explanation The configuration document reloading has been enabled for the named bus.
Action None.
CWSID0022E: Destination {0} contains a Context property {1} with an invalid value {2} for type {3}.
Explanation The configuration of the property is invalid.
Action Run configuration validation.
CWSID0023E: Destination Default for Foreign Bus {0} contains a Context property {1} with an invalid value {2} for type {3}.
Explanation The configuration of the property is invalid.
Action Run configuration validation.
CWSID0024E: Mediation {0} contains a Context property {1} with an invalid value {2} for type {3}.
Explanation The configuration of the property is invalid.
Action Run configuration validation.
CWSID0025I: SIB is not using the HAManager GroupManager service.
Explanation The SIB messaging components are not using HAManager GroupManager service because the HA_DISABLED environment variable is defined.
Action If HA operation is wanted, then undefine the HA_DISABLED environment variable and restart the server.
CWSID0026I: Messaging engine {0} cannot be started from current state {1}.
Explanation 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.
Action Check the state of the messaging engine and re-issue the operation when valid.
CWSID0027I: Messaging engine {0} cannot be restarted because a serious error has been reported.
Explanation 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.
Action Restart the server or move the messaging engine to an alternate cluster server.
CWSID0028I: Messaging engine {0} cannot be stopped from current state {1}.
Explanation 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.
Action Check the state of the messaging engine and re-issue the operation when valid.
CWSID0029I: Messaging engine {0} suffered a common mode error.
Explanation The messaging engine detected an error that is likely to recur on an alternate server, so failover will not be attempted.
Action Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0030I: Messaging engine {0} suffered a common mode error and will be stopped.
Explanation The messaging engine detected a common mode error and is being automatically stopped. No failover will be attempted.
Action Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0031I: Messaging engine {0} suffered a common mode error and has been stopped.
Explanation The messaging engine detected a common mode error and was automatically stopped. No failover will be attempted.
Action 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; reason {1}
Explanation When reading the WCCM configuration document, an unexpected configuration was encountered.
Action 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}
Explanation An unexpected error occurred during engine initialization.
Action 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}
Explanation An unexpected error occurred during engine initialization. The start phase is terminated and engine components that have already been started will be stopped.
Action 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}
Explanation An error occurred when starting an engine component. No other engine components will be started.
Action 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
Explanation An error occurred when attempting to stop the messaging engine.
Action 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
Explanation An error was detected by an engine component.
Action Check the logs to determine the error, correct the cause of the error and restart the server.
CWSID0038E: Failed to join group
Explanation
Action
CWSID0039E: HAManager-initiated activation has failed, messaging engine {0} will be disabled.
Explanation
Action
CWSID0040E: HAManager and messaging engine loss of synch. Server will be killed
Explanation
Action
CWSID0041E: HAManager-initiated deactivation has failed, messaging engine {0} will be disabled.
Explanation
Action
CWSID0042E: Failed to create group name
Explanation
Action
CWSID0043W: It is not possible to send an Event Notification from JMX {0} MBean named {1}.
Explanation 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.
Action If this continues to occur, contact IBM Software Support.
CWSID0044I: Messaging Engine {0} with UUID {1} has been started.
Explanation The Messaging Engine is available for use.
Action None.
CWSID0045I: Messaging Engine {0} with UUID {1} has stopped.
Explanation The Messaging Engine is no longer available for use.
Action None.
CWSID0046E: Messaging engine {0} detected an error and cannot continue to run in this server.
Explanation 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.
Action 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.
CWSID9999E: {0}
Explanation If the message does not give sufficient information, check previous messages for further help.
Action See previous messages for further information.
Reference topic    

Terms of Use | Feedback

Last updated: Apr 23, 2009 7:19:30 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.sib.admin.impl.CWSIDMessages.html

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