Express (Distributed operating systems), v8.0 > Reference > Messages
CWSIP
CWSIP0001E: An internal messaging error occurred in {0}, {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0002E: An internal messaging error occurred in {0}, {1}, {2}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0003E: An internal messaging error occurred {3} in {0}, {1}, {2}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0005E: An internal messaging error occurred {2} in {0}, {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0006E: An internal destination configuration error occurred to destination {2} in {0}, {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0007E: The link with name {0} and UUID {1} cannot be created because of an incorrect configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0008E: An internal messaging error occurred in {0}, {1}, : related values are {2}, {3}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0021E: Unable to create a consumer to a Service Destination with name {0} on messaging engine {1}.
Explanation Service destinations cannot have Consumers attached to them. An exception is created for any attempt to create a consumer session to a Service destination Action Create a destination which is not a Service destination and create a Consumer against this destination.
CWSIP0022E: Unable to create a Browser to a Service Destination with name {0} on messaging engine {1}.
Explanation Service destinations cannot have Browsers attached to them. An exception is created for any attempt to create a Browser session to a Service destination Action Create a destination which is not a Service destination and create a browser against this destination.
CWSIP0023E: The destination prefix {0} is incorrect for a system destination.
Explanation The prefix given for the system destination is greater than 24 characters or contains characters which are not in the ranges a-z, A-Z, 0-9, ., /, and %. Action Ensure that the destination prefix for a system destination is less than 24 characters, and only contains characters in the ranges a-z, A-Z, 0-9, ., /, and %.
CWSIP0024E: An attempt was made to access a non system destination {0} from a system connection on messaging engine {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0025E: Durable Subscription mismatch error, the destination name {0} does not match the subscriptions destination {1} for durable subscription {2} on messaging engine {3}
Explanation An attempt to create a Consumer for the specified durable subscription name failed as the destination specified did not match the destination used to create the durable subscription. Action Attach to the durable subscription using the same destination as used when the subscription was created.
CWSIP0026E: MQ Link with UUID {0} was not found on messaging engine {1}
Explanation An attempt was made to use an MQ Link, but this was not found on the specified messaging engine. Action Define the MQ Link in the Administrative Console and restart your Server.
CWSIP0027E: Publish/Subscribe MQ Link with UUID {0} was not found on messaging engine {1}
Explanation An attempt was made to use a Publish/Subscribe MQ Link, but this was not found on the specified messaging engine. Action Define the MQ Link in the Administrative Console and restart your Server.
CWSIP0028W: Support for multiple subscribers to subscription {0}, on destination {1}, has been disabled.
Explanation The destination is set to maintain message ordering. Therefore any subscriptions on the destination can only have one subscriber. Action If ordering is not required, unset the maintainMessageOrder attribute to disable multiple subscriber override.
CWSIP0029W: An internal messaging error occurred. The parameter with name mqLinkUuidStr has not been supplied at location {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0030E: Consuming messages from destination {0} on bus {1} while connected to bus {2} is not permitted.
Explanation Message consumption is only permitted from destinations in the locally connected bus, not from foreign buses. Action Modify the destination that the consumer is attempting to consume from or modify the connection to connect to the bus where the destination is located.
CWSIP0031E: An attempt to create a subscription on destination {0} failed due to error {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0033E: An attempt to create a subscription on destination {0} with name {1} failed due to a data store Resource Problem {2}
Explanation When creating a durable subscription an item is added into the data store. This failed due to a Cache resource problem Action Increase the Cache size for the data store using the administrative console
CWSIP0034E: An attempt to create a subscription on destination {0} failed due to a Persistent Store Resource Problem {2}
Explanation When creating a subscription an item is added into the data store. This failed due to a Cache resource problem Action Increase the Cache size for the data store using the administrative console
CWSIP0035E: An attempt to attach a consumer to the subscription {0} on the remote messaging engine {1} failed as the subscription is already homed locally.
Explanation A durable subscription can only live on one messaging engine. A subscription with a similar name is currently homed on the local ME, so it cannot be homed on the remote ME. Action Change the durable subscription home property of the durable subscription or delete the local subscription.
CWSIP0036E: An attempt to send a control message to an internal system destination {0} destination for messaging engine {1} has failed as the destination is full.
Explanation A control message cannot be sent to the destination as the destination is full. This means that the Publish Subscribe topology is now inconsistent. Action Clear the messages from the system destination and restart the server. Ensure that the remote messaging engine is started and communications have been established between them.
CWSIP0038E: The destination prefix {0} is incorrect for a temporary destination.
Explanation The prefix given for the temporary destination is greater than 12 characters or contains characters which are not in the ranges a-z, A-Z, 0-9, ., /, and %. Action Ensure that the destination prefix for a temporary destination is less than 12 characters, and only contains characters in the ranges a-z, A-Z, 0-9, ., /, and %.
CWSIP0041E: The link with name {0} was not found on messaging engine {1}.
Explanation A message arrived at the named messaging engine destined for the named link, but this link is unknown. Action Check that the link name is correct and defined in the administrative console. Check that the messaging engine has the latest configuration applied to it.
CWSIP0043E: The link with name {0} already exists on messaging engine {1}.
Explanation An attempt was made to create a link, but the named link already exists on the named messaging engine. Action Check that the link name is correct and defined in the administrative console. Check that the messaging engine has the latest configuration applied to it.
CWSIP0044W: An internal messaging error occurred. The destinationName has not been supplied on messaging engine {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0045W: An internal messaging error occurred. An invalid destination alter command was supplied for destination {0} on messaging engine {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0046W: An internal messaging error occurred. Unable to delete system destination {0} on messaging engine {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0048E: The destination {0} cannot be recovered from the data store.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0049E: The Link {0} cannot be recovered from data store.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0050W: The temporary destination unique count has reached its maximum value.
Explanation The temporary destination unique count has reached its maximum value and has wrapped. Temporary destinations are no longer guaranteed to be unique. Action None
CWSIP0051E: The destination {0} cannot be recovered from the data store due to error {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0052E: The temporary destination with name {0} is in use by another application and can not be deleted.
Explanation The temporary destination is in use. Deleting the temporary destination cannot occur until all consumers have disconnected. Action Close any active consumers for the named temporary destination and try again.
CWSIP0054E: The WebSphere MQ link with name {0} and UUID {1} is corrupt
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0056E: The link with name {0} and UUID {1} cannot be recovered from data store. {2}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0057E: Cannot find publish/subscribe broker profile {0} on MQLink {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0062E: The destination {0} with UUID {1} could not be recovered due to a possible WCCM configuration error
Explanation The WCCM configuration for this destination on this messaging engine has become incorrect, so the destination will not be made available on this messaging engine. Action Correct the WCCM configuration and then restart the server. The destination will then be made available again on this messaging engine.
CWSIP0063I: The local destination {0} with UUID {1} has been marked for deletion.
Explanation The WCCM configuration for this destination on this messaging engine has been removed, so its resources will be scheduled for deletion. Action none
CWSIP0064I: The WebSphere MQ link {0} with UUID {1} has been marked for deletion.
Explanation The WCCM configuration for this WebSphere MQ link on this messaging engine has been removed, so its resources will be scheduled for deletion. Action none
CWSIP0065I: The local Link {0} with UUID {1} has been marked for deletion.
Explanation The WCCM configuration for this link on this messaging engine has been removed, so its resources will be scheduled for deletion. Action none
CWSIP0066I: The remote destination {0} with UUID {1} has been marked for deletion.
Explanation The WCCM configuration for this destination on a remote messaging engine has been removed, so its resources will be scheduled for deletion. Action none
CWSIP0067I: The remote Link {0} with UUID {1} has been marked for deletion.
Explanation The WCCM configuration for this Link on a remote messaging engine has been removed, so its resources will be scheduled for deletion. Action none
CWSIP0072E: Durable subscription with name {0} does not exist on messaging engine {1}.
Explanation An attempt has been made to access a durable subscription with the given name and this subscription does not exist. Action Either create the durable subscription with the given name, or try again with a valid durable subscription identifier.
CWSIP0081E: Browser Session is closed on destination {0} and cannot be used.
Explanation The browser has been closed and cannot be used on the specified destination. Action Create a new browser session to the specified destination.
CWSIP0085E: An attempt was made to open destination {0} to browse on messaging engine {1}. The destination is temporarily locked.
Explanation Destinations are locked during some administrative actions, for example, deletion. Action Attempt to connect to the destination again.
CWSIP0092E: Unable to create BifurcatedConsumer to original consumer {0} on messaging engine {1}.
Explanation An attempt was made to create a BifurcatedConsumer, but the originating consumer was not found with the identifier supplied. Action Make sure that the originating consumer is active and retry the operation with the correct identifier.
CWSIP0094E: Unable to create BifurcatedConsumer to original consumer {0} on messaging engine {1} as they have different user ids.
Explanation An attempt was made to create a BifurcatedConsumer but the security context used to created the BifurcatedConsumer and the originating consumer are different. Action Make sure that the originating consumer and the BifurcatedConsumer are using the same security context or Connection and retry the command.
CWSIP0097E: The temporary destination with name {0} cannot be found.
Explanation An attempt was made to delete the named temporary destination, but the named destination cannot be found. Action Ensure that the temporary destination exists and retry the delete operation.
CWSIP0098E: Cannot create durable subscription {0} to a temporary destination {1}.
Explanation An attempt to was made to create a durable subscription to a temporary destination, but this is not allowed. Action Create the durable subscription on a topic space that isn't temporary. Check the administrative console for this list of available topic space destination.
CWSIP0099E: The temporary destination with name {0} cannot be found because the temporary destination was created on a different connection.
Explanation Temporary destinations can be accessed from the same connection only. Action Verify that the destination being used was created on the current connection.
CWSIP0100E: The supplied parameter combination is not valid for the creation of cloned durable subscription {0} on destination {1} for messaging engine {2}
Explanation An attempt to create a cloned durable subscription failed because noLocal behavior was requested, but this is not supported for cloned subscribers Action Reconfigure the durable subscription in the administrative console by removing the noLocal option.
CWSIP0111E: The destination with name {0} is being deleted on messaging engine {1}.
Explanation An attempt to use a destination was made while the destination is being deleted. Action Re-create the destination in the administrative console or use a different destination and try again.
CWSIP0112E: Destination {0} on messaging engine {1} cannot be deleted while consumers are attached.
Explanation An attempt was made to delete a destination with consumers still attached. Action A destination cannot be deleted while there are consuming applications attached to it. Remove all consuming applications from the destination and try again.
CWSIP0114E: The destination with name {0} on messaging engine {1} is receive exclusive.
Explanation An attempt has been made to create a consumer session to a destination configured with receive exclusive. This operation has failed because a consumer is already attached to the destination. Action Retry the operation when no consumers are attached, or update the destination so it is not receive exclusive and then retry the create consumer session operation.
CWSIP0115E: A message matched to subscription {0} on messaging engine {1} could not be sent to destination {2} because the destination could not be found.
Explanation An attempt has been made to match a message to an internal subscription and forward on to its target destination. The target destination could not be found. Action The destination may not exist or has been deleted. Check that the destination exists and is accessible.
CWSIP0116E: The destination with name {0} on messaging engine {1} is ordered and already has a consumer attached
Explanation An attempt has been made to create a consumer session to a destination configured with ordering maintained. This operation has failed because a consumer is already attached to the destination. Action Detach all other consumers before attempting to reattach.
CWSIP0117E: The destination with name {0} on messaging engine {1} can no longer guarantee message ordering.
Explanation An internal error has occurred which may have affected the ability to maintain message ordering. Action A restart of the messaging engine will resume maintainence of message order.
CWSIP0121E: The operation attempted is incorrect on the destination {0} on messaging engine {1}.
Explanation The destination does not support this operation. Action More info at:
CWSIP0133E: An attempt was made to open destination {0} on messaging engine {1} for Consuming. The destination is temporarily locked.
Explanation Destinations are locked during some administrative actions, for example, deletion. Action Try again.
CWSIP0141E: Destination mismatch error, A subscription {2} is attempting to use destination {0} which has been defined as a queue on messaging engine {1}.
Explanation An attempt was made to associate a subscription with destination defined to be a queue. Subscriptions can only be created against topic spaces Action Redefine the destination to be a topic space destination, or create a new destination of type Topicspace.
CWSIP0143E: The subscription with name {0} already exists on messaging engine {1}.
Explanation An attempt to create a durable subscription was made with the given name, but this subscription already exists. Action Delete the existing subscription and try again, or create the subscription with a new name.
CWSIP0146E: The durable subscription with name {0} does not exist on messaging engine {1}.
Explanation An attempt was made to access a durable subscription, but this durable subscription doesn't exist. Action The subscription may have been deleted or not yet created. Check that the subscription exists and retry the command.
CWSIP0147E: The durable subscription with name {0} on messaging engine {1} is an internal subscription and therefore cannot be attached to.
Explanation An attempt was made to access a durable subscription, but this durable subscription is internal and cannot be used. Action An Internal Subscription is used to map publications to a target destination. Internal subscription cannot be attached to by external consumers. Retry using a valid subscription name.
CWSIP0152E: The durable subscription with name {0} is in use by another consumer on messaging engine {1}.
Explanation A durable subscription with the specified name is in use by another consumer. Operations cannot be performed on the subscription until all consumers have disconnected. Action Only a single consumer is allowed to attach to a durable subscription. Detach any consumers and try again.
CWSIP0153E: The durable subscription with name {0} has messages that are uncommitted on messaging engine {1}.
Explanation A durable subscription has messages that are uncommitted so the attempt to delete failed. Action Commit any outstanding units of work created by either been sending to or receiving from the durable subscription consuming application, then try again.
CWSIP0156E: An error occurred while locating the remote messaging engine {0}.
Explanation Processing could not be completed because the remote messaging engine could not be found. Action Verify that messaging engine name is valid and the Remote messaging engine is running and that communications between messaging engine are active.
CWSIP0171E: A receive command is not possible while an asynchronous consumer is registered on destination {0} on messaging engine {1}
Explanation A consumer cannot receive messages while attached as an asynchronous consumer. Action Make sure the consumer is not registered as an asynchronous consumer and try again.
CWSIP0173E: Unable to locate message {0} on destination {1} on messaging engine {2}
Explanation A request was made to locate a message on a destination, but the message does not exist. Action The message may have previously been deleted, or expired. Check that the message exists on the specified destination and retry the operation.
CWSIP0174E: An asynchronous consumer cannot be registered on destination {0} on messaging engine {1} when issuing a synchronous receive command.
Explanation An attempt was made to register an asynchronous consumer while a receive command was being issued. Action Wait until the receive command has completed, then register the asynchronous consumer.
CWSIP0175E: An attempt to run an asynchronous consumer was made, but none have been registered on destination {0} on messaging engine {1}.
Explanation An application has requested to run an asynchronous consumer, but none have been registered on the specified destination. Action Register an asynchronous consumer on the destination and try again.
CWSIP0176E: An asynchronous consumer cannot be registered on destination {0}, messaging engine {1} when the session is started.
Explanation An attempt was made to register an asynchronous consumer on a destination when the session used to create the consumer is not in a stopped state. Action Stop the consumer and try again.
CWSIP0177E: The consumer session on destination {0} on messaging engine {1} has been closed.
Explanation An operation cannot be performed on the consumer session when it has been closed. Action Create a new consumer Session for the specified destination, or perform the operation before closing the consumer.
CWSIP0178E: The receive operation is not valid at this time on destination {0} on messaging engine {1}.
Explanation Another receive operation is already in progress for this consumer session on the specified destination. Action Allow the original receive operation to complete and try again.
CWSIP0180E: The destination with name {0} on messaging engine {1} is receive disallowed due to a current transacted receive taking place.
Explanation An attempt has been made to receive messages from a destination when it is configured with ordering maintained. Another transaction is currently outstanding on this destination. Action Complete all other transactions on this destination before attempting to receive with a new transaction.
CWSIP0181W: The maximum batch size for the consumer on destination {0}, has been set to 1.
Explanation The destination is set to maintain message ordering. Therefore the maximum batch size for a consumer has been set to 1. Action If ordering is not required, unset the maintainMessageOrder attribute to disable maximum batch size override.
CWSIP0182W: Consumer {0} of resource {1} on messaging engine {2} has been blocked for {3} seconds.
Explanation The message consumer on the named resource has been blocked for an unexpectedly long period of time, processing the same set of messages. While in this state it is unable to process any further messages. Action Resolve why the message consumer has become blocked, investigate the state of the applications currently consuming messages from the resource.
CWSIP0183I: Consumer {0} of resource {1} on messaging engine {2} is no longer blocked.
Explanation The message consumer on the named resource is no longer blocked on a set of messages. This is either because the reason for the blockage has been resolved or the consumer has been closed. Action None.
CWSIP0191E: The current message is not valid on destination {0} on messaging engine {1}.
Explanation An attempt was made to unlock the current message, but there was no message to unlock. Action The message may have already been unlocked or deleted by the current consumer.
CWSIP0192E: The current message is not valid on destination {0} on messaging engine {1}.
Explanation An attempt was made to delete the current message, but there was no message to delete. Action The message may have already been unlocked or deleted by the current consumer.
CWSIP0193E: The lock has expired for message with id {0} on messaging engine {1}.
Explanation An attempt was made to use a message inside a Consumer, but the lock timeout has expired and the message was made reavailable. Action When a lock expires the message is made reavailable for another Consumer to process.
CWSIP0194E: The destination with name {0} on messaging engine {1} is unavailable for receiving messages due to a current transacted receive taking place.
Explanation An attempt has been made to receive messages from a destination when it is configured with ordering maintained. Another transaction is currently outstanding on this destination. Action Complete all other transactions on this destination before attempting to receive with a new transaction.
CWSIP0201E: This operation is not available
Explanation This message handler is corrupt or is in reset state. Action Reset the message handler if it is not already in reset state. Then restart the messaging engine.
CWSIP0211E: Messaging engine {0} on bus {1} is not started.
Explanation A request was made to access the named messaging engine, but it has not been started Action Start the named messaging engine .
CWSIP0212I: Messaging engine {0} on bus {1} is starting to reconcile the WCCM destination and link configuration.
Explanation The WCCM destination and link configuration is being reconciled with the configuration stored by the messaging engine when it was stopped. Action none
CWSIP0213I: Messaging engine {0} on bus {1} has finished reconciling the WCCM destination and link configuration.
Explanation The WCCM destination and link configuration has been reconciled with the configuration stored by the messaging engine when it was stopped. Appropriate resources will have been changed, created or scheduled for deletion. Action none
CWSIP0221E: The destination with name {0} on messaging engine {1} has been deleted.
Explanation An application that was connected to the specified destination has been disconnected as the destination has been deleted. Action none
CWSIP0222E: The destination with name {0} on messaging engine {1} has been changed to Receive Exclusive.
Explanation An application that was connected to the specified destination has been disconnected as the destination changed to become receive exclusive. All applications connected to the destination will be disconnected and only a single application will be allowed to reconnect. Action none
CWSIP0223E: The destination with name {0} on messaging engine {1} has a message point which cannot be reached.
Explanation An application that was connected to the specified destination has been disconnected as the messaging engine localising the destination could not be reached. Action Ensure the messaging engine localising the destination is available.
CWSIP0247E: The destination {0} has been deleted and the message cannot be put to the exception destination do to reason {1}.
Explanation An attempt to commit a message on a deleted destination resulted in an error. Action The destination has been deleted and is no longer usable.
CWSIP0249E: A message could not be delivered to a destination in the forward routing path as destination {0} is a topic space on messaging engine {1}
Explanation A forward routing path contained a topic space, which was not the final element in the path. Any following destinations cannot be delivered to. Action A topic space can only be the final element in a forward routing path. Correct the path and retry.
CWSIP0251E: The destination {0} on messaging engine {2} is not available because the high limit {1} for the number of messages for this destination has already been reached.
Explanation All queues to the named destination have already reached their configured high limit therefore the message cannot be accepted. Action Check that the configured high messages limit for the destination is correct.
CWSIP0253E: The destination {0} is send disallowed for messaging engine {1}
Explanation An attempt has been made to send a message to a destination and a check has been made to ensure that a publication point is available for this destination. This check failed as the publication point for this destination is send disallowed. Action Update the publication point for the destination so it is send allowed and retry the send operation.
CWSIP0261E: Messaging engine recovery error. Expected version {0}, received {1}
Explanation When recovering an item from the messaging engine persistent storage a version check was made. This check failed. The reason for this error could be a new version of WebSphere was installed and subsequently removed. Or the persistent store has become corrupt. Action Restore the messaging engine state from a backup and consult the information center for information on doing this.
CWSIP0262E: The current message is corrupt and can not be added to the persistent store due to exception {0}
Explanation Messages are added to the Persistent Store, but this failed due to a problem being encountered. Action Check the linked exception and correct any problems before resending the message
CWSIP0271E: Subscription with id {0} not found
Explanation Attaching at Runtime to a subscription failed as the subscription could not be found. This could have been caused by the subscription being deleted. Action Reconnect using the Administrative Console to another subscription to view the state
CWSIP0272E: Subscription with id {0} cannot be deleted as it is not durable
Explanation Using the Runtime panels in the Administrative Console to delete subscriptions will only delete subscriptions that are durable. A delete operation will fail if tried against non durable subscriptions Action Retry the delete operation against a durable subscription.
CWSIP0281E: Failed to encode message for transmit to remote messaging engine {0} on destination {1} with value {2}, {3} and error {4}
Explanation A message that is bound for a remote messaging engine failed to be encoded and could not be sent Action Check the ffdc logs for the reason the message failed to encode and correct the error. The current message needs to be removed from the outbound stream. This can be done removing from the Remote Queue Point using the Administrative Console.
CWSIP0291W: An attempt to send a message to exception destination {0} on messaging engine {1} failed due to the following : {2}
Explanation An attempt to send a message to the specified exception destination failed. This will be retried using the default exception destination. Action Check that the specified destination exists and that it is operational.
CWSIP0295E: An attempt to generate an exception report failed so the original message was not sent to exception destination {0} on messaging engine {1}
Explanation An attempt to route a message to exception destination failed because an exception report was requested but could not be sent for the message. Action More info at:
CWSIP0301E: Unable to authenticate user {0} when creating a connection to secure messaging engine {1} on bus {2}.
Explanation The user specified could not be authenticated when trying to create a connection to the messaging engine bus Action Check the user has been added to the WAS security repository and that the correct password has been specified
CWSIP0302E: A user {0} is not authorized to access the messaging engine {1} on bus {2}.
Explanation The user specified is not authorized to access the messaging engine bus. Action If the user should have authority to access the messaging engine bus then update the authorization rights for the messaging engine bus.
CWSIP0303E: No user specified when creating a connection to secure messaging engine {0} on bus {1}.
Explanation An attempt was made to create a connection on a secure messaging engine but no user was supplied. Action Create the connection to the messaging engine supplying a user and a password
CWSIP0304E: Browse access to destination {0} was denied for subject {1}
Explanation A user is not authorized to browse the destination. Action If the user should have authority to browse messages on the given destination then update the users authorization rights for the destination
CWSIP0305E: The user with subject {1} is not authorized to create temporary destinations with prefix {0}.
Explanation A user is not authorized to create temporary destinations with the named prefix. Action If the user should have authority to create temporary destinations with the named prefix then update the users authorization rights for the named prefix.
CWSIP0309E: Receive access from destination {0} was denied for user with subject {1}.
Explanation A user is not authorized to receive from the destination. Action If the user should have authority to receive messages on the given destination then update the users authorization rights for the destination
CWSIP0310E: Receive access from discriminator {1} on destination {0} was denied for user with subject {2}.
Explanation A user is not authorized to receive from the destination using the specified topic. Action If the user should have authority to receive messages on the given topic then update the users authorization rights for the topic on the given destination.
CWSIP0311E: A user {0} is not authorized to delete a durable subscription {1} on destination {2}.
Explanation A user has attempted to delete a durable subscription, but is not the user that created the durable subscription. Action Delete the durable subscription with the originating user.
CWSIP0312E: A user {0} is not authorized to activate a durable subscription {1} on destination {2}.
Explanation A user is not authorized to activate durable subscription, but is not the user that created the durable subscription. Action Activate the durable subscription with the originating user.
CWSIP0313E: A user {0} is not authorized to access exception destination {1}.
Explanation A user is not authorized to put messages to the Exception destination specified. Action If the user should have access to the exception destination, edit the exception destination access control in the adminstration console by adding the specified user
CWSIP0314E: Inquire access for destination {0} was denied for user with subject {1}
Explanation A user is not authorized to inquire about the configuration for the destination Action If the user should have access to inquire about the configuration of a destination, edit the Inquire access control in the adminstration console by adding the specified user
CWSIP0315E: Inquire access for foreign bus {0} was denied for user with subject {1}
Explanation A user is not authorized to inquire about the configuration for the specified Foreign Bus Action If the user should have access to inquire about the configuration of the Foreign Bus, edit the Inquire access control in the adminstration console by adding the specified user
CWSIP0316E: User {0} must be SIBServerSubject to use invokeCommand() method
Explanation The user is not authorized to call the invokeCommand() method in the connection Action Invoke the method on a connection with SIBServerSubject access
CWSIP0331W: The destination {0} on messaging engine {1} has already been marked for deletion.
Explanation A request has been made to delete a destination, but this destination has already been marked for deletion. Action The destination should be removed from the messaging engine by the system.
CWSIP0341W: The destination {0} was not found on messaging engine {1}.
Explanation The named destination is unknown on the local messaging engine. Action =Check that the destination name is correct. If the destination exists on another messaging engine, ensure that communication with the other messaging engine is working.
CWSIP0361W: The message with id {0} can not be deleted as the transaction used to add it to destination {1} has not been committed.
Explanation A message has been sent to the specified destination using a MessageProducer using a transaction. This transaction has not been committed to the destination so the message cannot be deleted. Action Review the information center section "Resolving in-doubt transactions" to commit or rollback the transaction.
CWSIP0362W: The message with id {0} can not be deleted from destination {1} as the message has been delivered to a consumer.
Explanation The message cannot be deleted as it has been delivered to a consumer. Action Stop any MDB or applications consuming from the destination and try the delete again. If the message still cannot be deleted, review the information center section "Resolving in-doubt transactions" to commit or rollback the transaction.
CWSIP0371E: The selector syntax {0} is not valid.
Explanation The selector syntax supplied is not valid. Action Correct the syntax for the selector and try again.
CWSIP0372E: The topic syntax {0} is not valid.
Explanation The topic syntax supplied is not valid. Action Correct the syntax for the topic and try again.
CWSIP0373W: Unable to load access control list to due to exception {0}.
Explanation When the access control list was loaded an exception occurred. Action Check and correct the related exception to enable the access control list to load correctly.
CWSIP0374W: Unable to load access control list to due to exception {2} for discriminator {0} and user {1}
Explanation When the access control list was loaded an exception occurred. Action Check and correct the related exception to enable the access control list to load correctly.
CWSIP0375W: Unable to load access control list to due to exception {1} for discriminator {0}
Explanation When the access control list was loaded an exception occurred. Action Check and correct the related exception to enable the access control list to load correctly.
CWSIP0376E: The selector could not be parsed due to an internal error.
Explanation The parsing environment for the selector is not valid. Action Check and correct the related exception.
CWSIP0377I: The XPath Optimization Bus custom property was incorrectly set to {0}. XPath Optimization will be enabled.
Explanation The XPath Optimization Bus custom property has been set incorrectly. The expected value is either "enabled" or "disabled". The ME will start with optimization enabled. Action Check and correct the value of the custom property and restart the server.
CWSIP0381W: No Response received from messaging engine {0} for subscription request message.
Explanation A request message has been sent to a remote messaging engine which has not responded in a timely manner. This means that the messaging engine Publish Subscribe Topology may be inconsistent. Action Make sure that the remote messaging engine listed is started. If the problem persists, contact your IBM Support representative.
CWSIP0382I: Messaging engine {0} responded to subscription request, Publish Subscribe topology now consistent.
Explanation Successful communications have been made between messaging engines and the Publish subscribe Topology is consistent. Action none
CWSIP0383E: Unable to send initial subscription state message to messaging engine {0}. Until this problem is resolved Publish Subscribe messaging will not be consistent. {1}.
Explanation Communication between messaging engines were unsuccessful. Publish Subscribe topology will not be consistent. Action Resolve any problem highlighted by the error and restart the messaging engine.
CWSIP0391E: An error occurred when trying to configure the list of remote messaging engines for messaging engine {0}, {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0422E: A requested expiry report message type could not be sent on messaging engine {0}. {1}
Explanation A problem occurred generating an Expiry report message type. Action Correct any associated errors. If problems persist, contact your IBM Support representative.
CWSIP0423E: A requested Confirm on Delivery report message type could not be sent on messaging engine {0}. {1}
Explanation A problem occurred generating a Confirm on delivery report message type. Action Correct any associated errors. If problems persist, contact your IBM Support representative.
CWSIP0451I: Force flush completed for Anycast streams for the given ME {0} and destination {1} that is localised here
Explanation None Action None
CWSIP0452I: Force flush completed for Anycast stream for destination {0} that is localised on messaging engine {1} since remote ME {2} has been deleted
Explanation None Action None
CWSIP0457E: Failed to persist state for remote consumer access for destination {0} that is localised at this ME.
Explanation The local state for remotely attached consumers to the destination may be corrupt because a local transaction failed to commit after many retries. Action More info at:
CWSIP0471E: Unable to communicate with the messaging engine {1} where the destination {0} is Localised.
Explanation Unable to communicate with the localisation messaging engine for the destination. This may be because messaging engine is still being initialized, or due to a network partition. Action Verify that it is possible to communicate with the localisation messaging engine, and then try again.
CWSIP0472E: The consumer attach is not being permitted or it is being detached because the consumer cardinality limit for destination {0} localised at ME {1} has been reached.
Explanation The destination has a consumer cardinality limit of one consumer. The limit has been reached. Action Try again after the existing consumer has disconnected.
CWSIP0473E: An exception {2} occurred when putting a remote message, on destination {0} localised at messaging engine {1}, into the local Persistent Store.
Explanation An exception occurred when putting a remote message, into the local Persistent Store. The consumer should disconnect if it wants to prevent a message ordering violation. Action The consumer should disconnect if it wants to prevent an message ordering violation. The exception should explain the cause of the problem. Try again after fixing the cause.
CWSIP0481E: A stream to communicate with the localisation messaging engine {1} for destination {0} is not available.
Explanation A stream to communicate with the localisation messaging engine for the destination is not available. This may be because the stream is still being initialized, or due to a network partition. Action Verify that it is possible to communicate with the localisation messaging engine, and then try again.
CWSIP0512E: A stream to communicate with the localisation messaging engine {1} for destination {0} is not available.
Explanation A stream to communicate with the localisation messaging engine for the destination is not available because a new stream needs to be created but the previous stream has not yet been flushed. This may be caused by a network partition. Action Verify that it is possible to communicate with the localisation messaging engine, and then try again.
CWSIP0514E: The consumer attach is not being permitted or it is being detached because the consumer cardinality limit for destination {0} localised at messaging engine {1} has been reached.
Explanation The destination has a consumer cardinality limit of one consumer. The limit has been reached. Action Try again after the existing consumer has disconnected.
CWSIP0515E: Failed to persist remote queue access state for destination {0}.
Explanation The local state for an attachment to the destination may be corrupt because a local transaction failed to commit after many retries. Action More info at:
CWSIP0517E: Cannot attach to queue point for destination {0} on messaging engine {1}.
Explanation The messaging engine hosting the queue point for the destination is unreachable. Action Verify that the messaging engine has been started and communications are active between messaging engines before retrying the operation.
CWSIP0518E: Cannot attach to queue point for destination {0} on messaging engine {1}..
Explanation The messaging engine hosting the queue point for the destination is unreachable. Action Verify that the messaging engine has been started and communications are active between messaging engines before retrying the operation.
CWSIP0532E: A timeout occurred while remotely browsing destination {0}.
Explanation The messaging engine hosting a message point for the destination failed to reply to a browse request. Action More info at:
CWSIP0533E: A remote browse of destination {0} failed with reason: {1}
Explanation The messaging engine hosting a message point for the destination returned an error code during a browse request. Action More info at:
CWSIP0550E: The destination {0}, UUID {1} has been deleted and the message cannot be put to the exception destination.
Explanation An attempt to clean up the messages on the specified destination resulted in an error. Action The clean-up will be retried at a later time.
CWSIP0551I: The send allowed state of destination {0}, with UUID {1} has changed to {2}.
Explanation The behaviour of the message points associated with the destination has been altered. Action None.
CWSIP0552I: The receive allowed state of destination {0}, with UUID {1} has changed to {2}.
Explanation The behaviour of the message points associated with the destination has been altered. Action None.
CWSIP0553W: The destination {0}, localized at {1} has reached its message depth high threshold.
Explanation The number of messages stored at a message point has made a depth change that takes the number stored over the depth high threshold. Action None.
CWSIP0554W: The destination {0}, localized at {1} has reached its message depth low threshold.
Explanation The number of messages stored at a message point has made a depth change that takes the number stored below the depth low threshold. Action None.
CWSIP0555W: The Remote Message Point on ME {0} for destination {1}, localized at {2} has reached its message depth high threshold.
Explanation The number of messages stored at a message point has made a depth change that takes the number stored over the depth high threshold. Action None.
CWSIP0556W: The Remote Message Point on ME {0} for destination {1}, localized at {2} has reached its message depth low threshold.
Explanation The number of messages stored at a message point has made a depth change that takes the number stored below the depth low threshold. Action None.
CWSIP0557W: The WebSphere MQ link {0}, localized at {2} has reached its message depth high threshold.
Explanation The number of messages stored at an MQ Link has made a depth change that takes the number stored over the depth high threshold. Action None.
CWSIP0558W: The WebSphere MQ link {0}, localized at {1} has reached its message depth low threshold.
Explanation The number of messages stored at an MQ Link has made a depth change that takes the number stored below the depth low threshold. Action None.
CWSIP0559W: The link {0} for bus {1}, on ME {2} has reached its message depth high threshold.
Explanation The number of messages stored at a Link has made a depth change that takes the number stored over the depth high threshold. Action None.
CWSIP0560W: The link {0} for bus {1}, on ME {2} has reached its message depth low threshold.
Explanation The number of messages stored at a Link has made a depth change that takes the number stored below the depth low threshold. Action None.
CWSIP0571E: The connection object no longer exists.
Explanation An Attempt to access a Connection failed as the Connection no longer exists. This could be due to an application closing the connection. Action None
CWSIP0572E: The message with id {0} no longer exists on destination {1}.
Explanation An Attempt to access a message with the specified id has failed. This is probably because the message has either expired, or an Application has removed it. Action None
CWSIP0601E: There are no more elements in the Iterator.
Explanation None. Action None
CWSIP0602E: There are no removable elements in the Iterator.
Explanation None. Action None
CWSIP0621E: An error occurred while resolving the alias destination {0} due to the following circular dependency {1} on messaging engine bus {2}
Explanation The alias destination could not be resolved due to a circular dependency Action Break the circular dependency by changing aliases in the resolution path in the administrative console.
CWSIP0631E: The remote durable operation {0} for subscription {1} timed out while waiting for messaging engine {2}.
Explanation The remote durable request timed out while waiting for a remote messaging engine. Action Verify that DURABLE_HOME is set properly, and that the target messaging engine is active.
CWSIP0641E: The local mediation point for destination {0} has been deleted and the message cannot be put to the exception destination.
Explanation An attempt to move the messages from the deleted local mediation point of the destination resulted in an error. Action The clean-up will be retried at a later time.
CWSIP0651E: The local mediation point for destination {0} has been told to start mediating messages, but cannot because a configuration change has occurred to remove that mediation from the destination.
Explanation A mediation is no longer defined on the destination, so the request to start the mediation point has resulted in an error. Action No user action is required. The mediation point will be removed shortly.
CWSIP0652I: The local mediation point for destination {0} stopped because the messaging engine is stopping.
Explanation The mediation point can no longer function because the messaging engine is stopping. The mediation point is being stopped. Action No user action is required. The mediation point will resume when the messaging engine is restarted at a later time if configured to do so.
CWSIP0654E: The local mediation point for destination {0} failed to start because an error occurred. The mediation definition is incorrect. The error is {1}.
Explanation The mediation point remains in the stopped state. Action The mediation point can be restarted once the conditions for the error have been changed.
CWSIP0655E: The local mediation point for destination {0} failed to start because an error occurred. Mediation {1} was not found. The error is {2}.
Explanation The mediation point remains in the stopped state. Action The mediation point can be restarted once the conditions for the error have been changed.
CWSIP0656W: A mediation point is unable to flow messages for destination {0} because of an error {1}
Explanation The mediation point attempted to start flowing messages to the mediation and the destination end-point. It failed to start the flow of messages. Action The mediation point can be restarted once the conditions for the error have been changed.
CWSIP0657I: The local mediation point for destination {0} and mediation {1} has moved to state {2}.
Explanation The mediation point has moved to a new state. Action none.
CWSIP0661E: The mediation for destination {0} attempted to put a message to the exception destination after the mediation had been stopped.
Explanation The message was not put to the exception destination. Action The mediation can retry putting the message when it has been restarted.
CWSIP0662E: The mediation point for destination {0} attempted to move a message to the post-mediated side of the destination. This operation failed.
Explanation The message was not put to the post-mediated side of the destination. The mediation point has been stopped. Action The mediation can retry moving the message when it has been restarted.
CWSIP0663E: The mediation point for destination {0} failed to start because the selector is incorrect. The selector was set to {1}. The error is {2}.
Explanation The selector specified in the configuration of the mediation is incorrect. Action Refer to the documentation to discover what constitutes a valid selector. Change the configuration of the mediation to set a valid selector. Re-start the mediation point.
CWSIP0664E: The mediation point for destination {0} failed to start because the discriminator is incorrect. The discriminator was set to {1}. The error is {2}.
Explanation The discriminator specified in the configuration of the mediation is incorrect. Action Refer to the documentation to discover what constitutes a valid discriminator. Change the configuration of the mediation to set a valid discriminator. Re-start the mediation point.
CWSIP0665E: The mediation point for destination {0} cannot start because the mediation is disabled for that destination.
Explanation The configuration information indicates that all mediation activity on this destination is disabled. Action When mediations are to work, the destination must indicate that mediations are enabled.
CWSIP0666W: The mediation point for destination {0} on bus {1} failed to create a Producer due to error {2}
Explanation To deliver messages to a mediation a Producer is required. Whilst creating a Producer an error occured. Action Examine the related exception and correct any problems.
CWSIP0671E: The destination {0} on messaging engine {1} failed to be inititialised for maintaining order.
Explanation An attempt was made to initialise an ordered destination but the destination had multiple outstanding transactions. Action Complete all transactions on the destination before ordering can be activated.
CWSIP0680E: Unable to create a bifurcated consumer from consumer {0}, consumer {0} is not bifurcatable.
Explanation Bifurcated consumers can only be created from consumers that were initially created as bifurcatable. Action Change the application that create the consumer to allow bifuracted consumers to be created.
CWSIP0771I: Administrator action.
Explanation The mediation point entered a state as a result of an action by the administrator. Action Refer to the documentation to discover how to change the state of the mediation point if required.
CWSIP0772I: Mediation action.
Explanation The mediation point entered a state as a result of an action by the mediation. Action Refer to the documentation to discover how to change the state of the mediation point if required.
CWSIP0773I: Using configured initial state.
Explanation The mediation point entered a state while trying to reach the configured start-state. Action Refer to the documentation to discover how to change the state of the mediation point if required.
CWSIP0774I: Waiting for WebSphere server to start
Explanation The mediation point entered a state while waiting for the Websphere Server to start. Action Refer to the documentation to discover how to change the state of the mediation point if required.
CWSIP0775I: Waiting for the deletion of another mediation point on this destination.
Explanation The mediation point has been added to the destination before the previous mediation point instance has been completely removed. The mediation will wait until the removal of the previous mediation is complete before it can continue. Action Refer to the documentation to discover how to change the state of the mediation point if required.
CWSIP0776I: Applying a configuration change.
Explanation The mediation point has entered this state as a result of a change in the configuration. Action Refer to the documentation to discover how to change the state of the mediation point if required.
CWSIP0777E: The transaction used for receive on the destination: {0} has already been completed.
Explanation An attempt was made to use a transaction that has already been completed. Action Make sure that the transaction used is a new transaction.
CWSIP0778E: The transaction used for delete on the destination: {0} has already been completed.
Explanation An attempt was made to use a transaction that has already been completed. Action Make sure that the transaction used is a new transaction.
CWSIP0780I: Messaging engine: {0} started, flush of all delivery streams requested.
Explanation The messaging engine has recognised that a flush of its delivery streams has been requested. Action None.
CWSIP0781I: Messaging engine: {0} started, flush initiated for stream: {1} and destination: {2}.
Explanation The messaging engine has begun its flushing of the stream. Action None.
CWSIP0782E: Messaging engine: {0} started, flush of stream: {1} and destination: {2} failed with the exception: {3}.
Explanation An error has occurred while flushing the streams. Action If the problem persists, contact your IBM Support representative.
CWSIP0783I: Messaging engine: {0} started, flush of all delivery streams completed.
Explanation The messaging engine has flushed all of its delivery streams. Action None.
CWSIP0784W: A remote message request (with id {2}) on a destination (with id {1}) from messaging engine {3} to {1} is no longer valid. Cleanup may be required.
Explanation The remote message request state shared between the two messaging engines is inconsistent, possibly due to one of the messaging engine's message store being restored/deleted, but not the other. Action Make the state between the two messaging engines consistent. Either by recovering the two message stores to the same point in time or cancelling this request on the receiving messaging engine.
CWSIP0785W: A message held on messaging engine {1} for transmission to a remote destination or foreign bus {0} has remained in committing state for {2} seconds under transaction {3}. Further messages may not flow until this transaction completes.
Explanation Any messages for the remote destination or foreign bus sent after the blocked message will not be transmitted until the transaction is resolved. Action Resolve the transaction identified as blocking the message
CWSIP0786I: Messages being sent to the remote destination or foreign bus {0} from messaging engine {1} are no longer blocked by transaction {2}.
Explanation The previously reported unresolved transaction has now been resolved and message transmission has been resumed. Action No action to be taken.
CWSIP0787I: Destination {0} on messaging engine {1} has reached a depth of {2} messages.
Explanation The message point for the destination has reached the stated message depth Action No action to be taken.
CWSIP0788I: {0} messages queued on messaging engine {1} for transmission to destination {2} on messaging engine {3}.
Explanation The remote message point for the destination has reached the stated message depth Action No action to be taken.
CWSIP0789I: {0} messages queued on messaging engine {1} for transmission to foreign bus {2} on link {3}.
Explanation The link to the foreign bus has reached the stated message depth Action No action to be taken.
CWSIP0790W: Messaging engine {3} has detected a gap in the stream of messages received from bus {1} on link {2}. Requests made to fill this gap have yet to be satisfied. The gap starts at sequence id {0}.
Explanation The messaging engine receiving messages over the inter-bus link has detected a gap in the sequence ids of messages received. Requests for re-delivery of one or more messages have been made to the sending messaging engine but the gap has not yet been filled. If the inter-bus link is not currently running, the gap will not be resolved until the inter-bus link is restarted. Action Restart the link if it is stopped.
CWSIP0791I: The gap starting at sequence id {0} in the message stream from bus {1} on link {2} has been resolved on messaging engine {3}.
Explanation A previously reported gap in the sequence of messages has now been resolved, subsequent messages will now be processed. Action No action to be taken.
CWSIP0792W: Messaging engine {3} has detected a gap in the stream of messages received from messaging engine {2} for destination {1}. Requests made to fill this gap have yet to be satisfied. The gap starts at sequence id {0}.
Explanation The messaging engine receiving messages for the destination has detected a gap in the sequence ids of messages received. Requests for re-delivery of one or more messages have been made to the sending messaging engine but the gap has not yet been filled. If the messaging engines are unable to communicate the gap will not be resolved until this is resolved. Action Restart the sending messaging engine if it is stopped and ensure the connection between the two messaging engines is active.
CWSIP0793I: The gap starting at sequence id {0} in the message stream for destination {1} from messaging engine {2} has been resolved on messaging engine {3}.
Explanation A previously reported gap in the sequence of messages has now been resolved, subsequent messages will now be processed. Action No action to be taken.
CWSIP0794W: {0} percent of the messages received by messaging engine {3} from bus {1} over inter-bus link {2} have repeatedly been transmitted over the inter-bus link.
Explanation A high percentage of messages sent from the foreign bus have previously been received by this messaging engine, messages will not be duplicated but the performance of the messaging system may be reduce. This message can occur when a sudden burst of messages is sent over the link, repeated occurrences of this message may indicate the throughput of the link is being exceeded on a sustained basis. Action Investigate whether the rate of production of messages for transfer over this link is too high.
CWSIP0795W: {0} percent of the messages received by messaging engine {2} for destination {3} transmitted from messaging engine {1} have repeatedly been transmitted to the messaging engine.
Explanation A high percentage of messages sent from the remote messaging engine have previously been received by this messaging engine, messages will not be duplicated but the performance of the messaging system may be reduce. This message can occur when a sudden burst of messages is transmitted to a messaging engine. Repeated occurrences of this message may indicate the maximum message throughput is being exceeded on a sustained basis. Action Investigate whether the rate of production of messages to this messaging engine is too high.
CWSIP0801E: The command invocation failed because the key was invalid {0}
Explanation The command could not be invoked because the key was not valid Action Check the key supplied on invokeCommand
CWSIP0802E: The command invocation failed because the following parameter was null {0}
Explanation The command could not be invoked because one of the parameters was null Action Set the specified parameter to a valid value and try again
CWSIP0803E: The addDestinationListener command failed because no DestinationListener was specified
Explanation The command could not be invoked because the DestinationListener parameters was null Action Specify a valid DestinationListener value and try again
CWSIP0811W: A message could not be sent to destination {0} assigned to WebSphere MQ Server bus member {1}. The WebSphere MQ completion code was {2}. The WebSphere MQ reason code was {3}.
Explanation A message could not be sent to the specified destination, assigned to the specified WebSphere MQ Server bus member. The WebSphere MQ completion and reason codes specified can be used to determine why the message could not be sent. Action Consult the WebSphere MQ documentation to determine the meaning of the completion and reason codes. Perform the appropriate corrective action.
CWSIP0812W: A message could not be sent to the mediation point associated with destination {0} associated with the WebSphere MQ Server bus member {1}. The WebSphere MQ completion code was {2}. The WebSphere MQ reason code was {3}.
Explanation A message could not be sent to the specified mediation execution point associated with the specified WebSphere MQ Server bus member. The WebSphere MQ completion and reason codes specified can be used to determine why the message could not be sent. Action Consult the WebSphere MQ documentation to determine the meaning of the completion and reason codes. Perform the appropriate corrective action.
CWSIP0813W: An exception {0} occurred when attempting to send a message to destination {1} assigned to WebSphere MQ Server bus member {2}.
Explanation A message could not be sent to the specified destination, assigned to the specified WebSphere MQ Server bus member. The WebSphere exception specified may be used to determine why the message could not be sent. Action Consult the WebSphere MQ documentation to determine the meaning of the exception. Perform the appropriate corrective action.
CWSIP0814W: An exception {0} occurred when attempting to send a message to the mediation point associated with destination {1} associated with the WebSphere MQ Server bus member {2}.
Explanation A message could not be sent to the mediation point for the specified destination, assigned to the specified WebSphere MQ Server bus member. The WebSphere exception specified may be used to determine why the message could not be sent. Action Consult the WebSphere MQ documentation to determine the meaning of the exception. Perform the appropriate corrective action.
CWSIP0815W: A message could not be received from destination {0} assigned to WebSphere MQ Server bus member {1}. The WebSphere MQ completion code was {2}. The WebSphere MQ reason code was {3}.
Explanation A message could not be received from the specified destination, assigned to the specified WebSphere MQ Server bus member. The WebSphere MQ completion and reason codes specified can be used to determine why the message could not be received. Action Consult the WebSphere MQ documentation to determine the meaning of the completion and reason codes. Perform the appropriate corrective action.
CWSIP0816W: A message could not be received from the mediation point associated with destination {0} assigned to WebSphere MQ Server bus member {1}. The WebSphere MQ completion code was {2}. The WebSphere MQ reason code was {3}.
Explanation A message could not be received from the mediation point associated with the specified destination, assigned to the specified WebSphere MQ Server bus member. The WebSphere MQ completion and reason codes specified can be used to determine why the message could not be received. Action Consult the WebSphere MQ documentation to determine the meaning of the completion and reason codes. Perform the appropriate corrective action.
CWSIP0817W: An exception {0} occurred when attempting to receive a message from destination {1} assigned to WebSphere MQ Server bus member {2}.
Explanation A message could not be received from the specified destination, assigned to the specified WebSphere MQ Server bus member. The WebSphere exception specified may be used to determine why the message could not be received. Action Consult the WebSphere MQ documentation to determine the meaning of the exception. Perform the appropriate corrective action.
CWSIP0818W: An exception {0} occurred when attempting to receive a message from the mediation point associated with destination {1} assigned to WebSphere MQ Server bus member {2}.
Explanation A message could not be received from the mediation point associated with the specified destination, assigned to the specified WebSphere MQ Server. The WebSphere exception specified may be used to determine why the message could not be received. Action Consult the WebSphere MQ documentation to determine the meaning of the exception. Perform the appropriate corrective action.
CWSIP0819W: A connection could not be established to the Websphere MQ Server bus member {0} as Websphere MQ messaging has been disabled.
Explanation Websphere MQ messaging is unavailable due to an error during the startup of the messaging engine. Action Ensure an appropriate Websphere MQ client has been setup on the messaging engine. Review the messaging engine startup logs to determine the startup error and perform the appropriate corrective action.
CWSIP0820W: An internal messaging error occurred when using the Websphere MQ Server bus member {0} : {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0821W: Failed to create a connection from resource manager, {0}, to Messaging Engine {1} on bus {2} when retrieving a transaction.
Explanation An internal connection to a messaging engine could not be created and will be retried at a later time. Action none
CWSIP0822E: Failed to find a link resource when creating a controllable adapter for a publication point on topicspace {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0851E: The setFlowProperties command failed on Consumer Set {0} because no Message Classification Flows were specified
Explanation The Message Flow properties could not be configured because the Flows parameter was null Action Specify a valid Flows value and try again
CWSIP0852E: The setFlowProperties command failed on Consumer Set {0} because invalid Message Classification Flows were specified
Explanation The Message Flow properties could not be configured because the Flows parameter were not valid Action Check that the classifications specified in the Flows are unique and try again
CWSIP0853W: Found {0} registered MessagingEngineControlListeners but there should be only one. The listeners found were {1}
Explanation Only one listener may be registered. The system will utilise only the first MessagingEngineControlListener in the list. Action Specify only one MessagingEngineControlListener
CWSIP0854E: Found but failed to register a MessagingEngineControlListener, caught exception {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0855E: A publication on topicspace, {0} could not be sent to bus {1} due to exception {2}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIP0856E: Cannot attach to queue point for destination {0} on messaging engine {1} for message gathering as the messaging engine is the wrong version.
Explanation The messaging engine hosting the queue point for the destination is an older version and does not support message gathering. Action Either use a non-gathering consumer or migrate the hosting messaging engine to a new product version.
CWSIP0905W: No connection established
Explanation The connection between this messaging engine and the foreign bus is not currently available, possibly due to the link not being started or the messaging engine unable to communicate with the messaging engine in the foreign bus Action Ensure the link is started and the messaging engines that host the link are active and have a working network connection between them.
CWSIP0908E: Error detected ({0})
Explanation One or more errors have been detected that may prevent further messages from being transmitted or received. Check the system logs for errors. Action More info at:
CWSIP0911W: No response from receiver, acknowledgement of sent messages are overdue
Explanation Messages have been sent to a remote messaging engine but no acknowledgment has been received for those messages for an unexpectedly long period of time. Action Ensure that the receiving messaging engine is started and able to communicate with the sending messaging engine. If it is then the system may be overloaded at this time and a reduction of message traffic will cure the problem.
CWSIP0912W: Blocked transmitter, the lead message has been held under an in-doubt transaction for an unexpectedly long period
Explanation The message at the front of the transmission stream is partially committed, the transaction is potentially in-doubt. The remaining messages will be blocked until the transaction is resolved. Action Locate the blocked message and diagnose the reason for the identified transaction being in this state. Resolving the transaction will unblock the messages
CWSIP0913W: Full message transmitter
Explanation The message transmitter has reached the messaging engine's high message threshold. The message backlog may be due to the receiving messaging engine not currently accepting messages or the rate of message production exceeding the capability to transmit the messages. Action Ensure the messaging engines that are communicating are active and have a network connection between them. If this state persists reduce the rate of message production if appropriate or check the system logs for errors.
CWSIP0914W: Inefficient message delivery has been observed, due to re-delivering messages.
Explanation One or more messages have required re-delivery to the receiving messaging engine, this is acceptable but not efficient. Possible reasons for requiring re-delivery are when the connection with the target messaging engine is lost or intermittent, or the rate of message production is exceeding the capability to transmit them. Action Ensure the messaging engines that are communicating are active and have a network connection between them. If this state persists reduce the rate of message production if appropriate or check the system logs for errors.
CWSIP0916W: Inefficient message delivery has been observed, due to re-delivering messages.
Explanation Re-delivery of messages is acceptable but not efficient. Possible reasons for requiring re-delivery are that the connection with the source messaging engine is lost or intermittent, or the rate of message production is exceeding the capability to receive them. Action Ensure the messaging engines that are communicating are active and have a network connection between them. If this state persists reduce the rate of message production if appropriate or check the system logs for errors.
CWSIP0917W: Re-establishing message delivery
Explanation A break in message transmission has been observed and is being resolved, possibly due to a break in communication or the rate of message production has exceeded the capability to receive them. Action Ensure the messaging engines that are communicating are active and have a network connection between them. If this state persists reduce the rate of message production if appropriate or check the system logs for errors.
CWSIP0919W: Blocked receiver, the receiver cannot deliver the current inbound message for reason {0} on destination {1}
Explanation The reciever is unable to deliver a message to the target destination for the given reason, until this problem is resolved delivery of subsequent messages will be blocked. Action If this state persists take appropriate action to resolve the problem with the message.
CWSIP0920I: Status OK
Explanation No problems have been detected with message transmission Action none
CWSIP9999E: {0}
Explanation If the message does not give sufficient information, check previous messages for further help. Action See previous messages for further information.