Explanation | An item was added to the data store but it did not have an appropriate constructor. |
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 | If the message does not give sufficient information, check previous messages for further help. |
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 was made to add a reference to a reference stream, which breaks consistency constraints. |
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 was made to add an item to a stream that is not in a data store. |
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 was made to add an item to a stream when the item was already in another stream. |
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 was made to add to a stream that was in an incorrect state. |
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 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt was made to delete a stream that was not empty. |
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 restore an item failed. |
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 data store did not receive its configuration. |
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 root persistable object was not created. |
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 data store is not in the correct state to perform the requested 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 | An internal error has occurred. The XA transaction protocol has not been followed correctly. |
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 internal error has occurred. The resource manager's transaction protocol has not been followed correctly. |
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 internal error has occurred. Transaction processing failed when the resource manager was asked to complete its work. |
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 was made to use WebSphere-specific function whilst not in the WebSphere run-time environment. |
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 was made to commit a transaction that has already been completed or is in the process of completing. |
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 was made to roll back a transaction that has already been completed or is in the process of completing. |
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 internal error has occurred. The included exception information can be used for diagnosis. |
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 internal error has occurred. |
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 dispatcher cannot accept more work due to an earlier data store error. |
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 data source that was configured for use as a data store has produced an exception. |
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 internal error has occurred. |
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 specified database is not recognized as a supported database. |
Action | Rerun the command and specify a supported database. |
Explanation | An exception from the data source caused the messaging engine to stop in order to avoid data corruption. |
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 incorrect operation has occurred on the internal message representation. |
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 maximum of 32 item tables can be used, with identifiers in the range 0 - 31. |
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 | There must be only one stream table. |
Action | Correct the problem and try again. |
Explanation | There must be at least one permanent table. |
Action | Correct the problem and try again. |
Explanation | There must be at least one temporary table. |
Action | Correct the problem and try again. |
Explanation | An attempt was made to set the state of an autocommit connection to 'rollback only' |
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 JNDI name is needed in order to identify the data source to use as a data store. |
Action | Correct the problem and try again. |
Explanation | An internal error has occurred. |
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 internal error has occurred. |
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 earlier exception prevented the writing of reliable persistent data to the data store for messaging engine {0}. The data cannot be recovered. |
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 maximum data size for the data store for messaging engine {0} is {1} bytes. |
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 data store lock is already held, probably by another active or recently failed messaging engine. |
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 transaction must be in a valid state in order to perform the task. |
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 connection pool for the data source used by the messaging engine's data source is too small. |
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 | Database tables required by the data store cannot be created dynamically. |
Action | Use the sibDDLGenerator to generate the DDL statements for the data store tables. |
Explanation | The look up of the specified JNDI name has failed to locate the data source. |
Action | Verify that the JNDI name is valid and try again. |
Explanation | An item table type has not been recognized as valid. |
Action | Correct the problem and try again. |
Explanation | The item table cannot perform the requested operation because it is not of the correct type. |
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 persistable is in an incorrect state because the completed count exceeded the begun count. |
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 data store persistence layer has been stopped so no more connections will be provided. |
Action | Restart the messaging engine and try again. |
Explanation | The messaging engine expected to find the column in the relevant table. |
Action | Correct the problem and try again. |
Explanation | The messaging engine expects certain data types to be used for the columns in the data store tables. |
Action | Correct the problem and try again. |
Explanation | The maximum data size that can be stored in the data store tables has been exceeded. |
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 was unable to find the table in the DBMS, and the option to have the messaging engine automatically create it was not selected. |
Action | Correct the problem and try again. |
Explanation | The messaging engine was unable to locate the schema in the DBMS. |
Action | Correct the problem and try again. |
Explanation | The messaging engine failed to find a class name that corresponds to the reference. |
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 unique id of your messaging engine does not match that in the data store. |
Action | You are trying to connect to an existing set of database tables that are owned by a different messaging engine. Either point your messaging engine's datasource to a separate set of tables or remove the existing ones. |
Explanation | The version of your messaging engine does not match that in the data store. |
Action | You are trying to connect to an existing set of database tables that are owned by a different messaging engine. Either point your messaging engine's datasource to a separate set of tables or remove the existing ones. |
Explanation | The messaging engine, identified by the UUIDs, has established ownership of the data store. |
Action | No user action is required. |
Explanation | The messaging engine, identified by the UUIDs, is attempting to establish ownership of the data store. |
Action | No user action is required. |
Explanation | DDLGenerator usage information. |
Action | Rerun the command using the correct syntax. |
Explanation | The specified number of tables must be a positive integer. |
Action | Correct the error and rerun the command. |
Explanation | The total number of stream (there is always one stream table), permanent and temporary tables should not exceed the maximum. |
Action | Reduce the number of permanent or temporary tables specified, and restart the server. |
Explanation | The specified number of permanent or temporary tables can only be increased. Reducing these values can lead to problems, and is not allowed. |
Action | Restore the original values for the number of permanent and temporary tables, and restart the server. |
Explanation | The data store has not been used by another messaging engine. |
Action | No user action required. |
Explanation | The data store has identified more than one messagine engine as it's owner. |
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 identified has previously used the data store. |
Action | No user action required. |
Explanation | The messaging engine's data store lock has been temporarily lost. |
Action | No user action required. Further messages will identify the course of action taken by the messaging engine to rectify the problem. |
Explanation | An attempt was made to add a non-unique object to the expiry index. |
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 expiry daemon thread was interrupted and has stopped. |
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 cache loader daemon thread was interrupted and has stopped. |
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 was made to start the expiry daemon thread but it is already running. |
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 | If the message does not give sufficient information, check previous messages for further help. |
Action | See previous messages for further information. |