Problem | An item was added to the data store but it did not have an appropriate constructor. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | If the message does not give sufficient information, check previous messages for further help. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to add a reference to a reference stream, which breaks consistency constraints. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to add an item to a stream that is not in a data store. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to add an item to a stream when the item was already in another stream. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to add to a stream that was in an incorrect state. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to add an item to a stream where the item had a higher storage strategy than the stream. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to delete a stream that was not empty. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt to restore an item failed. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The data store did not receive its configuration. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The root persistable object was not created. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The data store is not in the correct state to perform the requested operation. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The authentication data provided cannot be used to access the database containing the data store. |
User response | Provide an alternate authentication alias and try again. |
Problem | An internal error has occurred. The XA transaction protocol has not been followed correctly. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An internal error has occurred. The resource manager's transaction protocol has not been followed correctly. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An internal error has occurred. Transaction processing failed when the resource manager was asked to complete its work. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to use WebSphere-specific function whilst not in the WebSphere run-time environment. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to commit a transaction that has already been completed or is in the process of completing. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to roll back a transaction that has already been completed or is in the process of completing. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | A heuristic hazard has been detected. The messaging engine needs to restart to determine whether the changes to its message store succeeded. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An internal error has occurred. The included exception information can be used for diagnosis. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An internal error has occurred. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The dispatcher cannot accept more work due to an earlier data store error. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The data source that was configured for use as a data store has produced an exception. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An internal error has occurred. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The specified database is not recognized as a supported database. |
User response | Rerun the command and specify a supported database. |
Problem | An exception from the data source caused the messaging engine to stop in order to avoid data corruption. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An incorrect operation has occurred on the internal message representation. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | A maximum of 32 item tables can be used, with identifiers in the range 0 - 31. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | There must be only one stream table. |
User response | Correct the problem and try again. |
Problem | There must be at least one permanent table. |
User response | Correct the problem and try again. |
Problem | There must be at least one temporary table. |
User response | Correct the problem and try again. |
Problem | An attempt was made to set the state of an autocommit connection to 'rollback only' |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | A JNDI name is needed in order to identify the data source to use as a data store. |
User response | Correct the problem and try again. |
Problem | An internal error has occurred. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An internal error has occurred. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An earlier exception prevented the writing of reliable persistent data to the data store for messaging engine {0}. The data cannot be recovered. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The maximum data size for the data store for messaging engine {0} is {1} bytes. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The data store lock is already held, probably by another active or recently failed messaging engine. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The transaction must be in a valid state in order to perform the task. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The connection pool for the data source used by the messaging engine's data source is too small. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | Database tables required by the data store cannot be created dynamically. |
User response | Use the sibDDLGenerator to generate the DDL statements for the data store tables. |
Problem | The look up of the specified JNDI name has failed to locate the data source. |
User response | Verify that the JNDI name is valid and try again. |
Problem | An item table type has not been recognized as valid. |
User response | Correct the problem and try again. |
Problem | The item table cannot perform the requested operation because it is not of the correct type. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The persistable is in an incorrect state because the completed count exceeded the begun count. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The data store persistence layer has been stopped so no more connections will be provided. |
User response | Restart the messaging engine and try again. |
Problem | The messaging engine expected to find the column in the relevant table. |
User response | Correct the problem and try again. |
Problem | The messaging engine expects certain data types to be used for the columns in the data store tables. |
User response | Correct the problem and try again. |
Problem | The maximum data size that can be stored in the data store tables has been exceeded. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | 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. |
User response | Correct the problem and try again. |
Problem | The messaging engine was unable to locate the schema in the DBMS. |
User response | Correct the problem and try again. |
Problem | The messaging engine failed to find a class name that corresponds to the reference. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The unique id of your messaging engine does not match that in the data store. |
User response | 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. |
Problem | The version of your messaging engine does not match that in the data store. |
User response | 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. |
Problem | The messaging engine, identified by the UUIDs, has established ownership of the data store. |
User response | No user action is required. |
Problem | The messaging engine, identified by the UUIDs, is attempting to establish ownership of the data store. |
User response | No user action is required. |
Problem | DDLGenerator usage information. |
User response | Rerun the command using the correct syntax. |
Problem | The specified number of tables must be a positive integer. |
User response | Correct the error and try again. |
Problem | The total number of stream (there is always one stream table), permanent and temporary tables should not exceed the maximum. |
User response | Reduce the number of permanent or temporary tables specified, and restart the server. |
Problem | The number of permanent or temporary tables cannot be decreased. |
User response | Restore the original values for the number of permanent and temporary tables, and restart the server. |
Problem | The data store has not been used by another messaging engine. |
User response | No user action required. |
Problem | The data store has identified more than one messagine engine as its owner. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The messaging engine identified has previously used the data store. |
User response | No user action required. |
Problem | The messaging engine's data store lock has been temporarily lost. |
User response | No user action required. Further messages will identify the course of action taken by the messaging engine to rectify the problem. |
Problem | The schema name was not defined explicitly for the data store, and the database user id was not provided. |
User response | Provide a schema name and try again. |
Problem | The existing contents of the file store prevent the value in the configuration taking effect. |
User response | No user action required. The messaging engine will try to apply the configuration change again next time it starts. |
Problem | The existing contents of the file store prevent the value in the configuration taking effect. |
User response | No user action required. The messaging engine will try to apply the configuration change again next time it starts. |
Problem | This is part of the configuration information of the file store. |
User response | No user action required. |
Problem | This is part of the configuration information of the file store. |
User response | No user action required. |
Problem | This is part of the configuration information of the file store. |
User response | No user action required. |
Problem | This is part of the configuration information of the file store. |
User response | No user action required. |
Problem | This is part of the configuration information of the file store. |
User response | No user action required. |
Problem | This is part of the configuration information of the file store. |
User response | No user action required. |
Problem | This is part of the configuration information of the file store. |
User response | No user action required. |
Problem | This is part of the configuration information of the file store. |
User response | No user action required. |
Problem | This is part of the configuration information of the file store. |
User response | No user action required. |
Problem | 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. |
User response | No user action required. |
Problem | 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. |
User response | No user action required. |
Problem | The unique id of your messaging engine does not match that in the file store. |
User response | 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. |
Problem | The version of your messaging engine does not match that in the file store. |
User response | 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. |
Problem | The messaging engine, identified by the UUIDs, has established ownership of the file store. |
User response | No user action is required. |
Problem | The messaging engine, identified by the UUIDs, is attempting to establish ownership of the file store. |
User response | No user action is required. |
Problem | The file store has not been used by another messaging engine. |
User response | No user action required. |
Problem | The messaging engine identified has previously used the file store. |
User response | No user action required. |
Problem | The file store lock is already held, probably by another active or recently failed messaging engine. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The message store for the messaging engine is a data store. |
User response | No user action required. |
Problem | The message store for the messaging engine is a file store. |
User response | No user action required. |
Problem | If the message does not give sufficient information, check previous messages for further help. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The data store is using these permanent and temporary tables. |
User response | No user action required. |
Problem | The data store was using these permanent and temporary tables before the configuration was changed. |
User response | No user action required. |
Problem | 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. |
User response | Clean up any excess messages or if necessary increase the size of the log file. |
Problem | 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. |
User response | Clean up any excess messages or if necessary increase the size of the permanent store file. |
Problem | 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. |
User response | Clean up any excess messages or if necessary increase the size of the temporary store file. |
Problem | The 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. |
User response | 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. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | Check the path supplied to see if it refers to an available disk and directory. |
Problem | The file store is starting up and attempting to read the contents of its log file. |
User response | No action is required. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | The messages output previously should help in determining a reason for the failure of file store initialisation. |
Problem | The file store has successfully opened and initialised its log file. |
User response | No action is required. |
Problem | 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. |
User response | No action is required. |
Problem | The file store has successfully opened and checked the contents of its permanent store file. |
User response | No action is required. |
Problem | The file store has successfully opened and checked the contents of its temporary store file. |
User response | No action is required. |
Problem | The file store successfully opened and read all of its files and is now ready to accept new work. |
User response | No action is required. |
Problem | The file store has stopped as part of a controlled shutdown. |
User response | No action is required. |
Problem | The file store has stopped due to an unexpected error. Previous messages in the log should describe the error. |
User response | Look at all messages in the log to determine the root cause of the unexpected shutdown. |
Problem | An unexpected exception has been caught during file store initialisation that has stopped the messaging engine from starting. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An unexpected io exception has been caught during file store initialisation. Another attempt to initialise may be made. |
User response | Check the server logs to see if the problem is resolved when a retry of the file store initialisation is attempted. |
Problem | The combination of parameters used was unrecognized by the sibDDLGenerator. |
User response | Refer to the documentation for a valid combination of parameters to use for your database. Rerun the command with a valid combination of parameters. |
Problem | The data store exclusive lock ensures integrity of the data within the data store and cannot be disabled for this messaging engine. |
User response | If you have identified a need to disable the data store exclusive lock contact IBM Support. |
Problem | 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. |
User response | No action is required. |
Problem | The messaging engines data store has re-enabled its exclusive lock after the requested time period. |
User response | No action is required. |
Problem | An attempt was made to add a non-unique object to the expiry index. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The expiry daemon thread was interrupted and has stopped. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The cache loader daemon thread was interrupted and has stopped. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An attempt was made to start the expiry daemon thread but it is already running. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | If the message does not give sufficient information, check previous messages for further help. |
User response | See previous messages for further information. |