S MessageStore messages

CWSIS0001E: An item does not have an accessible (public) default constructor {0}.
Explanation: 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/.

CWSIS0002E: The messaging engine encountered an exception while starting. Exception: {0}
Explanation: 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/.

CWSIS0003E: Reference {0} has no referred item and cannot be added to {1}.
Explanation: 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/.

CWSIS0004E: It is not possible to add {0} to {1} because it is not in a data store.
Explanation: 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/.

CWSIS0005E: It is not possible to add {0} to second stream {1}.
Explanation: 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/.

CWSIS0006E: It is not possible to add to stream {0} that is {1}.
Explanation: 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/.

CWSIS0500E: The item storage strategy {0} exceeds the owning stream storage strategy {1}.
Explanation: 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/.

CWSIS0501E: It is not possible to delete a stream that is not empty.
Explanation: 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/.

CWSIS0502E: There was an exception while restoring an item.
Explanation: 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/.

CWSIS0503E: Configuration information for the data store is not available.
Explanation: 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/.

CWSIS0504E: The root persistable object cannot be created.
Explanation: 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/.

CWSIS0505E: The data store is in an incorrect state, {0}.
Explanation: 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/.

CWSIS1000E: The requested action could not be carried out as it does not comply with the XA transaction protocol.
Explanation: 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/.

CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager''s internal transaction protocol.
Explanation: 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/.

CWSIS1002E: An unexpected exception was caught during transaction completion. Exception: {0}
Explanation: 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/.

CWSIS1003E: The WebSphere function cannot be used outside of WebSphere.
Explanation: 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/.

CWSIS1004E: The transaction cannot be committed. The transaction is complete or completing.
Explanation: 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/.

CWSIS1005E: The transaction cannot be rolled back. The transaction is complete or completing.
Explanation: 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/.

CWSIS1099E: An unexpected exception has occurred. Exception: {0}
Explanation: 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/.

CWSIS1499E: An unrecoverable error has occurred and the messaging engine cannot continue.
Explanation: 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/.

CWSIS1500E: The dispatcher cannot accept work.
Explanation: 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/.

CWSIS1501E: The data source has produced an unexpected exception: {0}
Explanation: 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/.

CWSIS1502E: The tuple type, {0}, is not recognized as a valid type.
Explanation: 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/.

CWSIS1503E: Database: {0}, version: {1}, platform: {2}, is not supported
Explanation: The specified database is not recognized as a supported database.
User Response: Rerun the command and specify a supported database.

CWSIS1505E: Update failed for key generator: {0}.
Explanation: An attempt was made to update the maximum key value for the key generator.
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/.

CWSIS1507E: The item, {0}, cannot contain other items because it is of type, {1}
Explanation: 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/.

CWSIS1508E: The item table identifier, {0}, is outside of the allowed range.
Explanation: 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/.

CWSIS1509E: An incorrect number of stream tables, {0}, were found.
Explanation: There must be only one stream table.
User Response: Correct the problem and try again.

CWSIS1510E: An incorrect number of permanent tables, {0}, were found.
Explanation: There must be at least one permanent table.
User Response: Correct the problem and try again.

CWSIS1511E: An incorrect number of temporary tables, {0}, were found.
Explanation: There must be at least one temporary table.
User Response: Correct the problem and try again.

CWSIS1513E: The rollback only state cannot be set on an autocommit connection
Explanation: 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/.

CWSIS1514E: A data source JNDI name has not been specified.
Explanation: 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.

CWSIS1515E: The database, {0}, is not recognized as a valid database.
Explanation: 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/.

CWSIS1516E: Both data columns of table, {0}, were non-null.
Explanation: 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/.

CWSIS1517W: Reliable persistent data could not be written to the data store by messaging engine {0}.
Explanation: 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/.

CWSIS1518I: Maximum data size for messaging engine {0} is {1} bytes.
Explanation: 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/.

CWSIS1519E: Messaging engine {0} cannot obtain the lock on its data store, which ensures it has exclusive access to the data.
Explanation: 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/.

CWSIS1520E: The transaction is not in a legitimate state to perform the operation. It is in state: {0}
Explanation: 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/.

CWSIS1522E: The messaging engine''s request for a database connection timed out.
Explanation: 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/.

CWSIS1523E: Dynamic allocation of database objects in DB2 for z/OS is not allowed.
Explanation: 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.

CWSIS1524E: Data source, {0}, not found.
Explanation: 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.

CWSIS1525E: Incorrect item table type, {0}.
Explanation: An item table type has not been recognized as valid.
User Response: Correct the problem and try again.

CWSIS1526E: The item table, {0}, is not able to perform the operation. It is of type, {1}.
Explanation: 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/.

CWSIS1527E: A persistable object is in an incorrect state: operations begun count: {0}, operations completed count: {1}.
Explanation: 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/.

CWSIS1528E: New connections cannot be provided because the persistence layer is stopped.
Explanation: The data store persistence layer has been stopped so no more connections will be provided.
User Response: Restart the messaging engine and try again.

CWSIS1529E: The column, {0}, was not found in the table, {1}, as expected.
Explanation: The messaging engine expected to find the column in the relevant table.
User Response: Correct the problem and try again.

CWSIS1530E: The data type, {0}, was found instead of the expected type, {1}, for column, {2}, in table, {3}.
Explanation: 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.

CWSIS1531E: The maximum data size, {0} bytes, of the data store has been exceeded. The data size was, {1} bytes.
Explanation: 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/.

CWSIS1532E: The table, {0}, is missing.
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.
User Response: Correct the problem and try again.

CWSIS1533E: The schema, {0}, does not exist.
Explanation: The messaging engine was unable to locate the schema in the DBMS.
User Response: Correct the problem and try again.

CWSIS1534E: The class reference, {0}, was not resolved.
Explanation: 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/.

CWSIS1535E: The messaging engine''s unique id does not match that found in the data store. ME_UUID={0}, ME_UUID(DB)={1}
Explanation: 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.

CWSIS1536E: The messaging engine''s version does not match that found in the data store. VERSION={0}, VERSION(DB)={1}
Explanation: 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.

CWSIS1537I: The messaging engine has acquired an exclusive lock on the data store.
Explanation: The messaging engine has established ownership of the data store.
User Response: No user action is required.

CWSIS1538I: The messaging engine is attempting to obtain an exclusive lock on the data store.
Explanation: The messaging engine is attempting to establish ownership of the data store.
User Response: No user action is required.

CWSIS1539I: sibDDLGenerator [{0} ] [{1} ] [{2} ] [{3} ] [{4} ] [{5}|{6}] [{7} (z/OS only)] [{8} (z/OS only)] [{9} (z/OS only)] [{10} ] [{11}] [{12}] [{13} ] [{14} ]
Explanation: DDLGenerator usage information.
User Response: Rerun the command using the correct syntax.

CWSIS2000E: The item does not have a unique key: {0}
Explanation: 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/.

CWSIS2001E: The expiry daemon ended abnormally due to an unexpected exception: {0}
Explanation: 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/.

CWSIS2003E: The cache loader daemon ended abnormally due to an unexpected exception: {0}
Explanation: 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/.

CWSIS2004E: The expiry daemon is already running.
Explanation: 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/.

CWSIS9999E: {0}
Explanation: If the message does not give sufficient information, check previous messages for further help.
User Response: See previous messages for further information.