P Jetstream Message Processor messages |
CWSIP0001E: An internal messaging error occurred in {0}, {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIP0002E: An internal messaging error occurred in {0}, {1}, {2}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIP0003E: An internal messaging error occurred {3} in {0}, {1}, {2}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIP0004E: A fatal messaging error occurred during startup processing in {0}, {1}, {2}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIP0005E: An internal messaging error occurred {2} in {0}, {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIP0006E: An internal destination configuration error occurred to destination {2} in {0}, {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIP0008E: An internal messaging error occurred {2} in {0}, {1}, {3}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIP0009E: A resource error has been encountered.
Explanation:
A resource error was encountered during command processing.
User Response:
Check the linked exception for details.
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 thrown for any attempt to create a consumer session to a Service destination
User Response:
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 thrown for any attempt to create a Browser session to a Service destination
User Response:
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 %.
User Response:
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
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.
User Response:
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.
User Response:
Define the MQ Link in the Administrative Console and restart your Server.
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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
User Response:
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
User Response:
Increase the Cache size for the data store using the administrative console
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 %.
User Response:
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.
User Response:
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.
User Response:
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.
CWSIP0048E: The destination {0} cannot be recovered from data store.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIP0049E: The Link {0} cannot be recovered from data store.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
None
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.
User Response:
Close any active consumers for the named temporary destination and try again.
CWSIP0053E: Another update has already occurred for destination {0}
Explanation:
The named destination has already been altered, but the update is not complete. This update is working against stale information.
User Response:
Restart the server to allow destination configuration to be refreshed
CWSIP0054E: The WebSphere MQ link with name {0} and UUID {1} is corrupt
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
Make sure that the originating consumer and the BifurcatedConsumer are using the same security context or Connection and retry the command.
CWSIP0095E: A subscription name for a durable subscription cannot be null.
Explanation:
An attempt to create or use a durable subscription was made with a null subscription name.
User Response:
Set the subscription name to a valid value and try again.
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.
User Response:
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.
User Response:
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.
User Response:
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
User Response:
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.
User Response:
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.
User Response:
A destination cannot be deleted while there are consuming applications attached to it. Remove all consuming applications from the destination and try again.
CWSIP0113E: The destination with name {0} on messaging engine {1} is receive disallowed.
Explanation:
An attempt has been made to create a consumer session to a destination and a check has been made to ensure that messages can be received from this destination. This check failed as the destination is receive disallowed.
User Response:
Update the destination so it is receive allowed and retry the operation.
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.
User Response:
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.
CWSIP0121E: The operation attempted is incorrect on the destination {0} on messaging engine {1}.
Explanation:
The destination does not support this operation.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
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 which is defined to be a queue. Subscriptions can only be created against topic spaces
User Response:
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.
User Response:
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.
User Response:
The subscription may have been deleted or not yet created. Check that the subscription exists and retry the command.
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
Allow the original receive operation to complete and try again.
CWSIP0179E: The destination with name {0} on messaging engine {1} is receive disallowed.
Explanation:
An attempt has been made to receive messages from a destination when it is configured with receive disallowed.
User Response:
Update the destination so it is receive allowed and retry the operation.
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.
User Response:
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.
User Response:
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.
User Response:
When a lock expires the message is made reavailable for another Consumer to process.
CWSIP0201E: This operation is not available
Explanation:
This message handler is corrupt or is in reset state.
User Response:
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
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
none
CWSIP0223E: 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.
User Response:
none
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.
User Response:
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.
User Response:
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 {1} 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.
User Response:
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.
User Response:
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.
User Response:
Restore the Messaging Engine state from a backup and consult the Info Center for information on doing this.
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.
User Response:
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
User Response:
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}
Explanation:
A message that is bound for a remote Messaging Engine failed to be encoded and could not be sent
User Response:
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 using the wsadmin command.
CWSIP0291W: An attempt to send a message to exception destination {0} on messaging engine {1} failed.
Explanation:
An attempt to send a message to the specified exception destination failed. This will be retried using the default exception destination.
User Response:
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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
CWSIP0371E: The selector syntax {0} is not valid.
Explanation:
The selector syntax supplied is not valid.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
Check and correct the related exception to enable the access control list to load correctly.
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.
User Response:
Make sure that the remote messaging engine listed is started. If the problem persists, please 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.
User Response:
none
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
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.
User Response:
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
User Response:
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
User Response:
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSIP0471E: A stream to communicate with the localisation ME {1} for destination {0} is not available.
Explanation:
A stream to communicate with the localisation ME for the destination is not available. This may be because the stream is still being initialized, or due to a network partition.
User Response:
Verify that it is possible to communicate with the localisation ME, 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.
User Response:
Try again after the existing consumer has disconnected.
CWSIP0473E: An Exception {2} occurred when putting a remote message, on destination {0} localised at ME {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.
User Response:
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 ME {1} for destination {0} is not available.
Explanation:
A stream to communicate with the localisation ME for the destination is not available. This may be because the stream is still being initialized, or due to a network partition.
User Response:
Verify that it is possible to communicate with the localisation ME, and then try again.
CWSIP0512E: A stream to communicate with the localisation ME {1} for destination {0} is not available.
Explanation:
A stream to communicate with the localisation ME 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.
User Response:
Verify that it is possible to communicate with the localisation ME, 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 ME {1} has been reached.
Explanation:
The destination has a consumer cardinality limit of one consumer. The limit has been reached.
User Response:
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
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.
User Response:
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
User Response:
The clean-up will be retried at a later time.
CWSIP0561E: The exception {0} occurred on an asynchronous consumer session attached to the messaging engine {1}
Explanation:
A Connection listener detected that an exception occurred on an asynchronous consumer session
User Response:
The application that registered the connection listener should take appropriate action
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.
User Response:
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.
User Response:
None
CWSIP0601E: There are no more elements in the Iterator.
Explanation:
None.
User Response:
None
CWSIP0602E: There are no removable elements in the Iterator.
Explanation:
None.
User Response:
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
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
CWSIP0653I: The local mediation point for destination {0} stopped because the systems operator instructed it to stop.
Explanation:
The mediation point stopped as a result of a user action.
User Response:
No user action is required. The mediation point can be restarted by the systems operator at a later time.
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.
User Response:
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.
User Response:
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.
User Response:
The mediation point can be restarted once the conditions for the error have been changed.
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
Examine the related exception and correct any problems.
CWSIP0771I: Administrator action.
Explanation:
The mediation point entered a state as a result of an action by the administrator.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
Make sure that the transaction used is a new transaction.
CWSIP0780E: 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.
User Response:
None.
CWSIP0781E: Messaging engine: {0} started, flush initiated for stream: {1} and destination: {2}.
Explanation:
The messaging engine has begun its flushing of the stream.
User Response:
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.
User Response:
If the problem persists, please contact your IBM Support representative.
CWSIP0783E: Messaging engine: {0} started, flush of all delivery streams completed.
Explanation:
The messaging engine has flushed all of its delivery streams.
User Response:
None.
CWSIP0784E: Messaging engine: {0} received a message from messaging engine: {1} that was not expected.
Explanation:
The messaging engine has received a message that contained a sequence number greater than any sent.
User Response:
If a backup has been used consider restarting the messaging engine with "flush at startup".
CWSIP9999E: {0}
Explanation:
If the message does not give sufficient information, check previous messages for further help.
User Response:
See previous messages for further information.