Explanation | An item was added to the data store which 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, see the accompanying error messages for further information. |
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 | The authentication data provided cannot be used to access the database containing the data store. |
Action | Provide an alternate authentication alias and try again. |
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, 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 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 a 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 | 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The requested action cannot be carried out because the messaging engine does not recognise the XID supplied. This could be because the messaging engine has not seen the XID before or the XID is in the wrong 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 | The requested action cannot be carried out because the messaging engine is still associated with the supplied XID. Dissasociate the XID from the messaging engine by calling the XA end method before attempting to complete the transaction branch. |
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 requested action cannot be carried out because the messaging engine is already associated with the supplied XID. |
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. Use the exception information to determine the cause of the 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 | 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 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 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 tool 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 object 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 data source 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 data source to a separate set of tables or remove the existing ones. |
Explanation | The messaging engine, identified by the UUIDs in the message, has established ownership of the data store. |
Action | No action is required. |
Explanation | The messaging engine, identified by the UUIDs in the message, is attempting to establish ownership of the data store. |
Action | No 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 try again. |
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 number of permanent or temporary tables cannot be decreased. |
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 action is required. |
Explanation | The data store has identified more than one messagine engine as its 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 action is required. |
Explanation | The schema name was not defined explicitly for the data store, and the database user id was not provided. |
Action | Provide a schema name and try again. |
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The message store for the messaging engine is a data store. |
Action | No action is required. |
Explanation | The message store for the messaging engine is a file store. |
Action | No action is required. |
Explanation | If the message does not give sufficient information, see the accompanying error messages for further information. |
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 using these permanent and temporary tables. |
Action | No action is required. |
Explanation | The data store was using these permanent and temporary tables before the configuration was changed. |
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The spill dispatcher cannot accept more work due to an earlier 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 | 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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 | The messaging engine, identified by the UUIDs in the message, has been unable to get an exclusive lock on the database tables that hold its data. This could be due to another instance of the messaging engine running against the same set of tables. It could also be the result of a lock from a previously running instance being held for longer than expected in the database. The messaging engine will retry for a period during startup to see if it is able to acquire the lock. |
Action | If the messaging engine does not succeed in acquiring the lock during the startup retry period then check that no other instance of the messaging engine is running and that there are no outstanding locks on the tables for this messaging engine being held on your database server. |
Explanation | The messaging engine, identified by the UUIDs in the message, has lost an existing lock on the tables that hold its data. This may be due to a connectivity problem between the messaging engine and the database server or that another instance of the messaging engine has started and taken control of the tables. |
Action | Check that a network connection between your messaging engine and database server is available and that there is only one instance of the messaging engine running. |
Explanation | The combination of parameters used was unrecognized by the sibDDLGenerator. |
Action | Refer to the documentation for a valid combination of parameters to use for your database. Rerun the command with a valid combination of parameters. |
Explanation | The data store exclusive lock ensures integrity of the data within the data store and cannot be disabled for this messaging engine. |
Action | If you have identified a need to disable the data store exclusive lock contact IBM Support. |
Explanation | A request was made to disable the data store exclusive lock. The lock will remain disabled for the length of time stated in the message at which point it will re-enable automatically. |
Action | No action is required. |
Explanation | The messaging engines data store has re-enabled its exclusive lock after the requested time period. |
Action | No action is required. |
Explanation | The messaging engine, identified by the UUIDs in the message, is attempting to establish ownership of the data store. |
Action | No action is required. |
Explanation | If the message does not give sufficient information, see the accompanying error messages for further information. |
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 | To use restrict long running locks, the datastore requires modification to the table structure for storing additional data. This is facilitated by the sibDBUpdgrade command. |
Action | Use sibDBUpdgrade command to upgrade the existing table structure. |
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, see the accompanying error messages for further information. |
Action | See the accompanying error messages for further information. |