CWSID

CWSID0001I: Messaging engine {0} is initializing.

Explanation

The specified messaging engine is commencing initialization.

Action

No action is required.

CWSID0003E: An internal error occurred; reason: {0}

Explanation

An unexpected internal error occurred during system operation.

Action

If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .

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

No action is required, 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 therefore will 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 might cause other errors during runtime operation.

Action

CWSID0009E: Destination {0} cannot be created.

Explanation

The specified destination could not be created. If JACL scripts or custom JMX programs were used to create the configuration, check these for errors.

Action

CWSID0011W: It is not possible to activate JMX {0} MBean named {1}.

Explanation

The JMX MBean of the specified type and name could not be activated. Although this does not prevent the messaging server from starting, it does mean that any administrative functions that require the existence of this MBean might not work as expected.

Action

CWSID0012W: It is not possible to deactivate JMX {0} MBean named {1}.

Explanation

The specified JMX MBean could not be deactivated.

Action

CWSID0013W: It is not possible to load class {0}.

Explanation

The specified class could not be loaded.

Action

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. If JACL scripts or custom JMX programs were used to create the configuration, check these for errors.

Action

CWSID0016I: Messaging engine {0} is in state {1}.

Explanation

The specified messaging engine has completed a stage of startup or shutdown processing.

Action

No action is required.

CWSID0017I: Configuration reload is starting for bus {0}.

Explanation

Bus configuration file changes are being processed.

Action

No action is required.

CWSID0018I: Configuration reload is complete for bus {0}.

Explanation

All bus configuration file changes have been processed and all relevant destinations have been reloaded.

Action

No action is required.

CWSID0019I: Configuration reload is starting for messaging engine {0}.

Explanation

All messaging engine configuration documents are about to be checked for updates.

Action

No action is required.

CWSID0020I: Configuration reload is complete for messaging engine {0}.

Explanation

All messaging engine configuration documents have been read and updates have been processed.

Action

No action is required.

CWSID0021I: Configuration reload is enabled for bus {0}.

Explanation

Configuration document reloading has been enabled for the named bus.

Action

No action is required.

CWSID0022E: Destination {0} contains a Context property {1} with an invalid value {2} for type {3}.

Explanation

The configuration of the property is not valid.

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 not valid.

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 not valid.

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, undefine the HA_DISABLED environment variable then restart the server.

CWSID0026W: 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 then reissue the operation when valid.

CWSID0027E: 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.

CWSID0028W: 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 then reissue the operation when valid.

CWSID0029E: 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 then restart the server.

CWSID0030E: 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 then restart the server.

CWSID0031E: 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 then restart the server.

CWSID0032W: An inconsistency in the WCCM document {0} was detected, for the message point {1}

Explanation

When reading the WCCM configuration document, an unexpected configuration was encountered.

Action

The configuration might not be valid. 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 then 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 are stopped.

Action

Check the logs to determine the error, correct the cause of the error then restart the server.

CWSID0035E: Messaging engine {0} cannot be started; detected error reported during {1} {2}

Explanation

A messaging engine component could not be started. No other engine components will be started.

Action

Check the logs to determine the error, correct the cause of the error then restart the server.

CWSID0036E: Messaging engine {0} caught exception thrown by {1} {2} method during cleanup of failed start

Explanation

The specified messaging engine could not be stopped.

Action

Check the logs to determine the error, correct the cause of the error then 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 then restart the server.

CWSID0038E: Messaging engine {0} could not join an HAManager group

Explanation

The messaging engine will not be able to run in this server.

Action

CWSID0039E: HAManager-initiated activation has failed, messaging engine {0} will be disabled. Reason {1}

Explanation

The messaging engine did not activate, for the reason stated.

Action

Refer to previous errors in the log. There are two common reasons for this problem. The first reason is that the messaging engine is unable to obtain a lock on its message store, due to it being locked by another active messaging engine. A message store can only be owned by one messaging engine. If this is the case, ensure that the messaging engine has sole access to the given message store. The second reason is that the database or filesystem share being used by the message store is unavailable. In this case, ensure that the database or filesystem share is active then re-enable the SIB service.

CWSID0040E: Messaging engine {0} could not report completion to HAManager. Server will be killed

Explanation

HAManager callback context was rejected, during the call to report completion of an asynchronous operation.

Action

CWSID0041E: HAManager-initiated deactivation has failed, messaging engine {0} will be disabled. Reason {1}

Explanation

The messaging engine did not deactivate, for the reason stated.

Action

CWSID0042E: Failed to create group name for messaging engine {0}

Explanation

The group name required by the messaging engine could not be created by HAManager.

Action

CWSID0043W: It is not possible to send an Event Notification from JMX {0} MBean named {1}.

Explanation

An Event Notification could not be sent from the 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

CWSID0044I: Messaging Engine {0} with UUID {1} has been started.

Explanation

The messaging engine is available for use.

Action

No action is required.

CWSID0045I: Messaging Engine {0} with UUID {1} has stopped.

Explanation

The messaging engine is no longer available for use.

Action

No action is required.

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 the Application Server Network Deployment, the server will be restarted if the nodeagent is monitoring it. With a network deployment 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 then correct it so that it does not recur. Either restart the server, or (if you are using network deployment) check that the automatic restart or failover has succeeded and the messaging engine is running.

CWSID0047W: Concurrent mediations have been disallowed on destination {0}.

Explanation

The destination is set to maintain message ordering. Therefore concurrent mediations are not allowed and have been disabled.

Action

If ordering is not required, unset the maintainMessageOrder attribute to disable the concurrent mediation override.

CWSID0048W: The value for receiveExclusive has been overriden to become "true", on destination {0}

Explanation

The destination is set to maintain message ordering. Therefore the value for the receiveExclusive attribute has been overriden to become true.

Action

If ordering is not required, unset the maintainMessageOrder attribute to disable receiveExclusive override.

CWSID0049I: Messaging Engine {0} with UUID {1} is starting.

Explanation

The messaging engine is being started.

Action

No action is required.

CWSID0050I: Messaging Engine {0} with UUID {1} is stopping.

Explanation

The messaging engine is being stopped.

Action

No action is required.

CWSID0051I: Messaging Engine {0} with UUID {1} failed to start.

Explanation

The messaging engine failed to start.

Action

CWSID0052I: Messaging Engine {0} with UUID {1} failed to stop.

Explanation

The messaging engine failed to stop.

Action

CWSID0053I: Disabled Messaging engine {0} enabled.

Explanation

The Messaging engine is in Joined state and available for failover.

Action

No action is required.

CWSID0054E: Messaging engine {0} is not enabled, as the re-enable count {1} exceeded.

Explanation

The Messaging engine remains in disabled state as the ME re-enable count exceeded.

Action

Refer WebSphere Application Sever documentation and manually enable the Messaging engine.

CWSID0055I: Probing connection to database {0} of {1} time(s)

Explanation

Before initiation the start of messaging engine the health of datastore is probed.

Action

No action is required.

CWSID0056I: Connection to database is successful

Explanation

Probing connection to database resulted in success

Action

No action is required.

CWSID0057I: Connection to database could not be established

Explanation

Probing connection to database resulted in error

Action

Check the connection to the database.

CWSID0058E: Error getting datasource configid

Explanation

There was error getting datasource configid

Action

No action is required.

CWSID0059I: Testing connection to data source ID={0} is successful

Explanation

Testing the connection to datasource

Action

No action is required.

CWSID0060I: Testing connection to data source ID={0} is successful with warnings

Explanation

Testing the connection to datasource

Action

No action is required.

CWSID0061I: Connection to data source ID={0} is not successful

Explanation

Testing the connection to datasource

Action

No action is required.

CWSID0062I: Global error will be reported

Explanation

If its an authorization error then global error will be reported

Action

No action is required.

CWSID0063I: Local error will be reported

Explanation

If its not an authorization error then local error will be reported

Action

No action is required.

CWSID0064W: The HA Manager Service is unavailable, hence the messaging engine {0} in the cluster will start without the HA/Scalability capabilities

Explanation

HA Manager Service is unavailable, hence the messaging engine in the cluster will not have some HA features such as scalability and HA/Failover

Action

Enable the HA Manager Service to resume the HA/Scalability features for the messaging engine

CWSID0080I: The messaging engine {0} defined in the server is starting in synchronous mode.

Explanation

The messaging engine defined in the server is starting in synchronous mode.

Action

No action is required.

CWSID0081I: The messaging engine {0} is defined as critical.

Explanation

The custom property sib.property.isMECritical of the messaging engine has the value true, so the messaging engine is defined as critical.

Action

No action is required.

CWSID0082I: The value of the critical property of the messaging engine {0} cannot be determined.

Explanation

The custom property sib.property.isMECritical of the messaging engine does not have a boolean value, so the critical status cannot be evaluated.

Action

Set the custom property sib.property.isMECritical of the messaging engine to a boolean value.

CWSID0083I: The messaging engines {0} are waiting for the server to start.

Explanation

A messaging engine cannot start until the server has started. When the server has started, the messaging engine startup is completed.

Action

No action required.

CWSID0084I: The messaging engine {0} on the service integration bus {1} is in the PendingServerStart state.

Explanation

The messaging engine has finished the reconstitution and reconciliation of its destinations and links, and is waiting for the CRA start notification so that its startup can be completed.

Action

No action is required.

CWSID0085I: The state check thread is started for messaging engine {0} .

Explanation

The state check thread is started for messaging engine {0} started in synchronous start mode.

Action

No action is required.

CWSID0086I: The critical messaging engine {0} has started in synchronous mode.

Explanation

The critical messaging engine {0} has started in synchronous mode.

Action

No action is required.

CWSID0087I: Returning state check thread as no critical messaging engines are defined in server.

Explanation

Returning the state check thread as no critical messaging engines are defined in server.

Action

No action is required.

CWSID0088I: ME State Observer registered successfully

Explanation

ME State Observer registered successfully for all messaging engines defined in the server.

Action

No action is required.

CWSID0089I: ME State Observer notified successfully

Explanation

ME State Observer notified successfully for all messaging engines defined in the server.

Action

No action is required.

CWSID0090I: ME State Observer registered and notified successfully

Explanation

ME State Observer registered and notified successfully for all messaging engines defined in the server.

Action

No action is required.

CWSID0091I: Messaging engine {0} notified all hagroup members for started notification

Explanation

Messaging engine {0} notified all hagroup members to declare that it has started successfully

Action

No action is required.

CWSID0092I: Passive Messaging engine {0} is notified by active instance as started.

Explanation

Passive Messaging engine {0} is notified by active instance as started since another instance in same HAGroup has already started.

Action

No action is required.

CWSID9999E: {0}

Explanation

If the message does not give sufficient information, check previous messages for further help.

Action

See the accompanying error messages for further information.