Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | A resource error was encountered during command processing. |
Action | Check the linked exception for details. |
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 |
Action | Create a destination which is not a Service destination and create a Consumer against this destination. |
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 |
Action | Create a destination which is not a Service destination and create a browser against this 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 %. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
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. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
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 |
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 |
Explanation | A durable subscription can only live on one messaging engine. A subscription with the name {0} is currently homed on the local ME, so it cannot be homed on the remote ME {1} |
Action | Change the durable subscription home property of the durable subscription or delete the local subscription. |
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 %. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
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 |
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. |
Explanation | The named destination has already been altered, but the update is not complete. This update is working against stale information. |
Action | Restart the server to allow destination configuration to be refreshed |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
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. |
Explanation | The WCCM configuration for this destination on this messaging engine has been removed, so its resources will be scheduled for deletion. |
Action | none |
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 |
Explanation | The WCCM configuration for this link on this messaging engine has been removed, so its resources will be scheduled for deletion. |
Action | none |
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 |
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 |
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. |
Explanation | The browser has been closed and cannot be used on the specified destination. |
Action | Create a new browser session to the specified destination. |
Explanation | Destinations are locked during some administrative actions, for example, deletion. |
Action | Attempt to connect to the destination again. |
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. |
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. |
Explanation | An attempt to create or use a durable subscription was made with a null subscription name. |
Action | Set the subscription name to a valid value and try again. |
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. |
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. |
Explanation | Temporary destinations can be accessed from the same connection only. |
Action | Verify that the destination being used was created on the current connection. |
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. |
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. |
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. |
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. |
Action | Update the destination so it is receive allowed and retry the operation. |
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. |
Explanation | The destination does not support this operation. |
Action | 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/. |
Explanation | Destinations are locked during some administrative actions, for example, deletion. |
Action | Try again. |
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 |
Action | Redefine the destination to be a topic space destination, or create a new destination of type Topicspace. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | An attempt has been made to receive messages from a destination when it is configured with receive disallowed. |
Action | Update the destination so it is receive allowed and retry the operation. |
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. |
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. |
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. |
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. |
Explanation | A request was made to access the named messaging engine, but it has not been started |
Action | Start the named messaging engine . |
Explanation | The WCCM destination and link configuration is being reconciled with the configuration stored by the messaging engine when it was stopped. |
Action | none |
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 |
Explanation | An application that was connected to the specified destination has been disconnected as the destination has been deleted. |
Action | none |
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 |
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 |
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. |
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. |
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. |
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. |
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 Info Center for information on doing this. |
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 |
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 |
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. |
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 using the wsadmin command. |
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. |
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 | 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/. |
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 |
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. |
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 |
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 |
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. |
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 |
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. |
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. |
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. |
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 |
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 can not be deleted. |
Action | Review the Info Center section "Resolving in-doubt transactions" to commit or rollback the transaction. |
Explanation | The selector syntax supplied is not valid. |
Action | Correct the syntax for the selector and try again. |
Explanation | The topic syntax supplied is not valid. |
Action | Correct the syntax for the topic and try again. |
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. |
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. |
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. |
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, please contact your IBM Support representative. |
Explanation | Successful communications have been made between messaging engines and the Publish subscribe Topology is consistent. |
Action | none |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | A problem occurred generating an Expiry report message type. |
Action | Correct any associated errors. If problems persist, contact your IBM Support representative. |
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. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
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 | 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/. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The local state for an attachment to the destination may be corrupt because a local transaction failed to commit after many retries. |
Action | 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/. |
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. |
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. |
Explanation | The messaging engine hosting a message point for the destination failed to reply to a browse request. |
Action | 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/. |
Explanation | The messaging engine hosting a message point for the destination returned an error code during a browse request. |
Action | 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/. |
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. |
Explanation | The behaviour of the message points associated with the destination has been altered. |
Action | None. |
Explanation | The behaviour of the message points associated with the destination has been altered. |
Action | None. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | A Connection listener detected that an exception occurred on an asynchronous consumer session |
Action | The application that registered the connection listener should take appropriate action |
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 |
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 |
Explanation | None. |
Action | None |
Explanation | None. |
Action | None |
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. |
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. |
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. |
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. |
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. |
Explanation | The mediation point stopped as a result of a user action. |
Action | No user action is required. The mediation point can be restarted by the systems operator at a later time. |
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. |
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. |
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. |
Explanation | The mediation point has moved to a new state. |
Action | none. |
Explanation | The message was not put to the exception destination. |
Action | The mediation can retry putting the message when it has been restarted. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The messaging engine has recognised that a flush of its delivery streams has been requested. |
Action | None. |
Explanation | The messaging engine has begun its flushing of the stream. |
Action | None. |
Explanation | An error has occurred while flushing the streams. |
Action | If the problem persists, please contact your IBM Support representative. |
Explanation | The messaging engine has flushed all of its delivery streams. |
Action | None. |
Explanation | The messaging engine has received a message that contained a sequence number greater than any sent. |
Action | If a backup has been used consider restarting the messaging engine with "flush at startup". |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | See previous messages for further information. |