Explanation | An item was added to the data store which did not have an appropriate constructor. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | If the message does not give sufficient information, see the accompanying error messages for further information. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to add a reference to a reference stream, which breaks consistency constraints. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to add an item to a stream when the item was already in another stream. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to add to a stream that was in an incorrect state. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to add an item to a stream where the item had a higher storage strategy than the stream. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to delete a stream that was not empty. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt to restore an item failed. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The root persistable object was not created. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The data store is not in the correct state to perform the requested operation. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to delete a stream that was not empty. The number of items remaining on the stream and it's type are supplied in the message to help determine the reason this operation was attempted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An internal error has occurred. The XA transaction protocol has not been followed correctly. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An internal error has occurred. The resource manager transaction protocol has not been followed correctly. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An internal error has occurred. Transaction processing failed when the resource manager was asked to complete its work. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to use a WebSphere specific function whilst not in the WebSphere run-time environment. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to commit a transaction that has already been completed or is in the process of completing. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to roll back a transaction that has already been completed or is in the process of completing. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A heuristic hazard has been detected. The messaging engine may be out of synchronization and needs to restart to determine whether the changes to its message store succeeded. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The requested action cannot be completed because the messaging engine does not recognize the supplied XID value. This can result if the the messaging engine has not seen the XID before or if the XID is in the wrong state. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The requested action cannot be completed because the messaging engine is still associated with the supplied XID. Dissociate the XID from the messaging engine by calling the XA end method before attempting to complete the transaction branch. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The requested action cannot be completed because the messaging engine is already associated with the supplied XID. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The commit or rollback operation could not be performed using the specified XID string. |
Action | Specify a valid XID string |
Explanation | An internal error has occurred. Use the exception information to determine the cause of the error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An internal error has occurred. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The dispatcher cannot accept more work due to an earlier data store error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The data source that was configured for use as a data store has produced an exception. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An internal error has occurred. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An incorrect operation has occurred on the internal message representation. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to set the state of an autocommit connection to 'rollback only' |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The transaction must be in a valid state in order to perform the task. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The persistable object is in an incorrect state because the completed count exceeded the begun count. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The messaging engine failed to find a class name that corresponds to the reference. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The existing contents of the file store prevent the value in the configuration taking effect. |
Action | No action is required. The messaging engine will try to apply the configuration change again next time it starts. |
Explanation | The existing contents of the file store prevent the value in the configuration taking effect. |
Action | No action is required. The messaging engine will try to apply the configuration change again next time it starts. |
Explanation | This is part of the configuration information of the file store. |
Action | No action is required. |
Explanation | This is part of the configuration information of the file store. |
Action | No action is required. |
Explanation | This is part of the configuration information of the file store. |
Action | No action is required. |
Explanation | This is part of the configuration information of the file store. |
Action | No action is required. |
Explanation | This is part of the configuration information of the file store. |
Action | No action is required. |
Explanation | This is part of the configuration information of the file store. |
Action | No action is required. |
Explanation | This is part of the configuration information of the file store. |
Action | No action is required. |
Explanation | This is part of the configuration information of the file store. |
Action | No action is required. |
Explanation | This is part of the configuration information of the file store. |
Action | No action is required. |
Explanation | This is the number of bytes of space consumed by the contents of the permanent store file. It is not possible to reduce the minimum reserved size below this value. |
Action | No action is required. |
Explanation | This is the number of bytes of space consumed by the contents of the temporary store file. It is not possible to reduce the minimum reserved size below this value. |
Action | No action is required. |
Explanation | The unique id of your messaging engine does not match that in the file store. |
Action | You are trying to connect to an existing set of files that are owned by a different messaging engine. Either point your messaging engine's file store to a separate set of files or remove the existing ones. |
Explanation | The version of your messaging engine does not match that in the file store. |
Action | You are trying to connect to an existing set of files that are owned by a different messaging engine. Either point your messaging engine's file store to a separate set of files or remove the existing ones. |
Explanation | The messaging engine, identified by the UUIDs, has established ownership of the file store. |
Action | No action is required. |
Explanation | The messaging engine, identified by the UUIDs, is attempting to establish ownership of the file store. |
Action | No action is required. |
Explanation | The file store has not been used by another messaging engine. |
Action | No action is required. |
Explanation | The messaging engine identified has previously used the file store. |
Action | No action is required. |
Explanation | The file store lock is already held, probably by another active or recently failed messaging engine. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The message store for the messaging engine is a file store. |
Action | No action is required. |
Explanation | The file store has no more space in the log file to store messages. This could be due to an unexpected build up of messages or the file size being too small. |
Action | Clean up any excess messages or if necessary increase the size of the log file. |
Explanation | The file store has no more space in the permanent store file to store messages. This could be due to an unexpected build up of messages or the file size being too small. |
Action | Clean up any excess messages or if necessary increase the size of the permanent store file. |
Explanation | The file store has no more space in the temporary store file to store messages. This could be due to an unexpected build up of messages or the file size being too small. |
Action | Clean up any excess messages or if necessary increase the size of the temporary store file. |
Explanation | The spill dispatcher is full and cannot accept any new messages until some space has been made available. Removal of existing messages will be allowed to help the dispatcher free up space. |
Action | No action should be required to return the dispatcher to normal. However This may be a symptom of your temporary store file size being too small. |
Explanation | The persistent dispatcher cannot accept more work due to an earlier error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The spill dispatcher cannot accept more work due to an earlier error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | When the file store attempted to lock its log file, it could not do so because another process already holds the file lock. This process could be another active messaging engine or some other application process. |
Action | Check that your file store refers to a log file solely for use by that file store. If a second messaging engine is using the same file this could be due to incorrect configuration or an incorrect failover attempt. To allow this messaging engine to start determine which messaging engine is using the log file and stop that message engine. |
Explanation | When the file store attempted to open or create its log file it was unable to do so. A common cause of this problem is a disk mount not being present or the provided path being entered incorrectly. |
Action | Check the path supplied to see if it refers to an available disk and directory. |
Explanation | The file store is starting up and attempting to read the contents of its log file. |
Action | No action is required. |
Explanation | The file store has failed to initialise on this attempt. A previous message will be output detailing the reason for the failure. The file store will attempt to retry initialisation to see if the failure is recoverable. |
Action | If the file store does not successfully initialise after several attempts then check the log for messages describing the failure to see if there is a configuration or connectivity problem. |
Explanation | The messaging engines file store has reached the time limit for retrying initialisation and will now stop. Previous messages should describe the reason for the repeated failures to initialise. After stopping the messaging engine will be elligble for failover if your server configuration supports it. |
Action | The messages output previously should help in determining a reason for the failure of file store initialisation. |
Explanation | The file store has successfully opened and initialised its log file. |
Action | No action is required. |
Explanation | The file store is going to attempt to open and read the contents of its store files. If this is the first time the messaging engine has been started the files will also be created. |
Action | No action is required. |
Explanation | The file store has successfully opened and checked the contents of its permanent store file. |
Action | No action is required. |
Explanation | The file store has successfully opened and checked the contents of its temporary store file. |
Action | No action is required. |
Explanation | The file store successfully opened and read all of its files and is now ready to accept new work. |
Action | No action is required. |
Explanation | The file store has stopped as part of a controlled shutdown. |
Action | No action is required. |
Explanation | The file store has stopped due to an unexpected error. Previous messages in the log should describe the error. |
Action | Look at all messages in the log to determine the root cause of the unexpected shutdown. |
Explanation | An unexpected exception has been caught during file store initialisation that has stopped the messaging engine from starting. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An unexpected io exception has been caught during file store initialisation. Another attempt to initialise may be made. |
Action | Check the server logs to see if the problem is resolved when a retry of the file store initialisation is attempted. |
Explanation | An attempt was made to add a non-unique object to the expiry index. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The expiry daemon thread was interrupted and has stopped. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The cache loader daemon thread was interrupted and has stopped. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to start the expiry daemon thread but it is already running. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to add a non-unique object to the delivery delay index. |
Action | Restart the messaging engine. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The delivery delay manager daemon thread was interrupted and has stopped. |
Action | Restart the messaging engine. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An attempt was made to start the delivery delay manager daemon thread but it is already running. |
Action | Restart the messaging engine. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | If the message does not give sufficient information, see the accompanying error messages for further information. |
Action | See the accompanying error messages for further information. |