Express (Distributed operating systems), v8.0 > Reference > Messages
CWSIS
CWSIS0001E: An item does not have an accessible (public) default constructor {0}.
Explanation An item was added to the data store which did not have an appropriate constructor. Action More info at:
CWSIS0002E: The messaging engine encountered an exception while starting. Exception: {0}
Explanation If the message does not give sufficient information, see the accompanying error messages for further information. Action More info at:
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. Action More info at:
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. Action More info at:
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. Action More info at:
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. Action More info at:
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. Action More info at:
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. Action More info at:
CWSIS0502E: There was an exception while restoring an item.
Explanation An attempt to restore an item failed. Action More info at:
CWSIS0503E: Configuration information for the data store is not available.
Explanation The data store did not receive its configuration. Action More info at:
CWSIS0504E: The root persistable object cannot be created.
Explanation The root persistable object was not created. Action More info at:
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. Action More info at:
CWSIS0506E: The authentication data associated with the alias, {0}, is invalid.
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.
CWSIS0507E: It is not possible to delete a stream that is not empty. Items on stream={0}. Stream class={1}
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 More info at:
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. Action More info at:
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 transaction protocol has not been followed correctly. Action More info at:
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. Action More info at:
CWSIS1003E: The WebSphere function cannot be used outside of WebSphere.
Explanation An attempt was made to use a WebSphere specific function whilst not in the WebSphere run-time environment. Action More info at:
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. Action More info at:
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. Action More info at:
CWSIS1006E: The outcome of a transaction used to change the contents of the message store could not be determined. The messaging engine is stopping to avoid the possibility of data loss.
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 More info at:
CWSIS1007E: {0} not possible as the supplied XID is not recognised by the messaging engine. XID: {1}
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 More info at:
CWSIS1008E: {0} not possible as the supplied XID has not yet been called to end it''s association with the messaging engine. XID: {1}
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 More info at:
CWSIS1009E: {0} not possible as the supplied XID is already associated with this messaging engine. XID: {1}
Explanation The requested action cannot be carried out because the messaging engine is already associated with the supplied XID. Action More info at:
CWSIS1099E: An unexpected exception has occurred. Exception: {0}
Explanation An internal error has occurred. Use the exception information to determine the cause of the error. Action More info at:
CWSIS1499E: An unrecoverable error has occurred and the messaging engine cannot continue.
Explanation An internal error has occurred. Action More info at:
CWSIS1500E: The dispatcher cannot accept work.
Explanation The dispatcher cannot accept more work due to an earlier data store error. Action More info at:
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. Action More info at:
CWSIS1502E: The tuple type, {0}, is not recognized as a valid type.
Explanation An internal error has occurred. Action More info at:
CWSIS1503E: Database: {0}, version: {1}, platform: {2}, is not supported
Explanation The specified database is not recognized as a supported database. Action Rerun the command and specify a supported database.
CWSIS1504E: The messaging engine is stopping due to an exception from the data source.
Explanation An exception from the data source caused the messaging engine to stop in order to avoid data corruption. Action More info at:
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. Action More info at:
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. Action More info at:
CWSIS1509E: An incorrect number of stream tables, {0}, were found.
Explanation There must be only one stream table. Action 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. Action 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. Action 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' Action More info at:
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. Action Correct the problem and try again.
CWSIS1515E: The database, {0}, is not recognized as a valid database.
Explanation An internal error has occurred. Action More info at:
CWSIS1516E: Both data columns of table, {0}, were non-null.
Explanation An internal error has occurred. Action More info at:
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 the messaging engine. The data cannot be recovered. Action More info at:
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. Action More info at:
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. Action More info at:
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 is too small. Action More info at:
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. Action Use the sibDDLGenerator tool 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. Action 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. Action 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. Action More info at:
CWSIS1527E: A persistable object is in an incorrect state: operations begun count: {0}, operations completed count: {1}.
Explanation The persistable object is in an incorrect state because the completed count exceeded the begun count. Action More info at:
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. Action 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. Action 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. Action 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. Action More info at:
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. Action 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. Action 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. Action More info at:
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. 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.
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. 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.
CWSIS1537I: The messaging engine, ME_UUID={0}, INC_UUID={1}, has acquired an exclusive lock on the data store.
Explanation The messaging engine, identified by the UUIDs in the message, has established ownership of the data store. Action No action is required.
CWSIS1538I: The messaging engine, ME_UUID={0}, INC_UUID={1}, is attempting to obtain an exclusive lock on the data store.
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.
CWSIS1539I: sibDDLGenerator [{0} <DBMS name>] [{1} <DBMS version>] [{2} <DBMS platform>] [{3} <schema>] [{4} <user>] [{5}|{6}] [{7} <database> (z/OS only)] [{8} <storage group> [{9} <high-level qualifier>] (z/OS only)] [{10} <buffer pool> (z/OS only)] [{11} <terminator>] [{12}] [{13}] [{14} <statements>] [{15} <statements>] [{16} <number of permanent tables>] [{17} <number of temporary tables>]
Explanation DDLGenerator usage information. Action Rerun the command using the correct syntax.
CWSIS1540E: An invalid number of tables has been specified, {0}.
Explanation The specified number of tables must be a positive integer. Action Correct the error and try again.
CWSIS1541E: The maximum number of SIBnnn tables that can be used by a messaging engine, {0}, has been exceeded.
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.
CWSIS1542E: The configured number of permanent or temporary tables, {1}, is less than the number currently in use, {0}.
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.
CWSIS1543I: No previous owner was found in the messaging engine's data store.
Explanation The data store has not been used by another messaging engine. Action No action is required.
CWSIS1544E: Multiple previous owner id's found in the messaging engine's data store.
Explanation The data store has identified more than one messagine engine as its owner. Action More info at:
CWSIS1545I: A single previous owner was found in the messaging engine''s data store, ME_UUID={0}, INC_UUID={1}
Explanation The messaging engine identified has previously used the data store. Action No action is required.
CWSIS1547E: Unable to determine the schema name for the messaging engine.
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.
CWSIS1548W: The log file size cannot be changed to the value in the messaging engine's file store configuration at this time.
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.
CWSIS1549W: The store file size cannot be changed to the value in the messaging engine's file store configuration at this time.
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.
CWSIS1550I: The current size of the log file is {0} bytes. The size in the configuration information of the log file is {1} bytes.
Explanation This is part of the configuration information of the file store. Action No action is required.
CWSIS1551I: The current minimum reserved size of the permanent store file is {0} bytes. The current maximum size is {1} bytes.
Explanation This is part of the configuration information of the file store. Action No action is required.
CWSIS1552I: The current minimum reserved size of the permanent store file is {0} bytes. The current maximum size is unlimited.
Explanation This is part of the configuration information of the file store. Action No action is required.
CWSIS1553I: The minimum reserved size in the configuration information of the permanent store file is {0} bytes. The maximum size is {1} bytes.
Explanation This is part of the configuration information of the file store. Action No action is required.
CWSIS1554I: The minimum reserved size in the configuration information of the permanent store file is {0} bytes. The maximum size is unlimited.
Explanation This is part of the configuration information of the file store. Action No action is required.
CWSIS1555I: The current minimum reserved size of the temporary store file is {0} bytes. The current maximum size is {1} bytes.
Explanation This is part of the configuration information of the file store. Action No action is required.
CWSIS1556I: The current minimum reserved size of the temporary store file is {0} bytes. The current maximum size is unlimited.
Explanation This is part of the configuration information of the file store. Action No action is required.
CWSIS1557I: The minimum reserved size in the configuration information of the temporary store file is {0} bytes. The maximum size is {1} bytes.
Explanation This is part of the configuration information of the file store. Action No action is required.
CWSIS1558I: The minimum reserved size in the configuration information of the temporary store file is {0} bytes. The maximum size is unlimited.
Explanation This is part of the configuration information of the file store. Action No action is required.
CWSIS1559I: The data in the permanent store file occupies {0} bytes.
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.
CWSIS1560I: The data in the temporary store file occupies {0} bytes.
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.
CWSIS1561E: The messaging engine''s unique id does not match that found in the file store. ME_UUID={0}, ME_UUID(FS)={1}
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.
CWSIS1562E: The messaging engine''s version does not match that found in the file store. VERSION={0}, VERSION(FS)={1}
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.
CWSIS1563I: The messaging engine, ME_UUID={0}, INC_UUID={1}, has acquired an exclusive lock on the file store.
Explanation The messaging engine, identified by the UUIDs, has established ownership of the file store. Action No action is required.
CWSIS1564I: The messaging engine, ME_UUID={0}, INC_UUID={1}, is attempting to obtain an exclusive lock on the file store.
Explanation The messaging engine, identified by the UUIDs, is attempting to establish ownership of the file store. Action No action is required.
CWSIS1565I: No previous owner was found in the messaging engine's file store.
Explanation The file store has not been used by another messaging engine. Action No action is required.
CWSIS1566I: A single previous owner was found in the messaging engine''s file store, ME_UUID={0}, INC_UUID={1}
Explanation The messaging engine identified has previously used the file store. Action No action is required.
CWSIS1567E: Messaging engine {0} cannot obtain the lock on its file store, which ensures it has exclusive access to the data.
Explanation The file store lock is already held, probably by another active or recently failed messaging engine. Action More info at:
CWSIS1568I: Messaging engine {0} is using a data store.
Explanation The message store for the messaging engine is a data store. Action No action is required.
CWSIS1569I: Messaging engine {0} is using a file store.
Explanation The message store for the messaging engine is a file store. Action No action is required.
CWSIS1570E: The messaging engine encountered an exception while locking the data store. Exception: {0}
Explanation If the message does not give sufficient information, see the accompanying error messages for further information. Action More info at:
CWSIS1571I: Data store table summary: Permanent {0}, temporary {1}.
Explanation The data store is using these permanent and temporary tables. Action No action is required.
CWSIS1572I: Data store table summary before configuration change: Permanent {0}, temporary {1}.
Explanation The data store was using these permanent and temporary tables before the configuration was changed. Action No action is required.
CWSIS1573E: The file store's log file is full.
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.
CWSIS1574E: The file store's permanent store file is full.
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.
CWSIS1575E: The file store's temporary store file is full.
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.
CWSIS1576E: The spill dispatcher is full.
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.
CWSIS1577E: The persistent dispatcher cannot accept work.
Explanation The persistent dispatcher cannot accept more work due to an earlier error. Action More info at:
CWSIS1578E: The spill dispatcher cannot accept work.
Explanation The spill dispatcher cannot accept more work due to an earlier error. Action More info at:
CWSIS1579E: The file store's log file is locked by another process.
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.
CWSIS1580E: The file store''s log file cannot be found in the provided location: {0}.
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.
CWSIS1581I: The file store is attempting to initalise its log file: {0}
Explanation The file store is starting up and attempting to read the contents of its log file. Action No action is required.
CWSIS1582I: The file store had a problem initialising its log file but will attempt to retry.
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.
CWSIS1583E: The file store has exceeded the initialisation retry limit and will now stop.
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.
CWSIS1584I: The file store has initialised successfully.
Explanation The file store has successfully opened and initialised its log file. Action No action is required.
CWSIS1585I: The file store is attempting to start its permanent store ({0}) and temporary store ({1}).
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.
CWSIS1586I: The file store's permanent store has been started successfully.
Explanation The file store has successfully opened and checked the contents of its permanent store file. Action No action is required.
CWSIS1587I: The file store's temporary store has been started successfully.
Explanation The file store has successfully opened and checked the contents of its temporary store file. Action No action is required.
CWSIS1588I: The file store has started successfully.
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.
CWSIS1589I: The file store has stopped successfully.
Explanation The file store has stopped as part of a controlled shutdown. Action No action is required.
CWSIS1590E: The file store has stopped unexpectedly.
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.
CWSIS1591E: The file store has caught an unexpected exception during initialisation.
Explanation An unexpected exception has been caught during file store initialisation that has stopped the messaging engine from starting. Action More info at:
CWSIS1592E: The file store has caught an unexpected io exception.
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.
CWSIS1593I: The messaging engine, ME_UUID={0}, INC_UUID={1}, has failed to gain an initial lock on the data store.
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.
CWSIS1594I: The messaging engine, ME_UUID={0}, INC_UUID={1}, has lost the lock on the data store.
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.
CWSIS1595E: An invalid combination of parameters has been specified, Database: {0}, version: {1}, platform: {2} . Refer to the documentation for the correct parameters for your database.
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.
CWSIS1596I: The data store exclusive lock cannot be disabled.
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 we have identified a need to disable the data store exclusive lock contact IBM Support.
CWSIS1597I: The data store exclusive lock has been disabled for {0} milliseconds.
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.
CWSIS1598I: The data store exclusive lock has been automatically re-enabled.
Explanation The messaging engines data store has re-enabled its exclusive lock after the requested time period. Action No action is required.
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. Action More info at:
CWSIS2001E: The expiry daemon ended abnormally due to an unexpected exception: {0}
Explanation The expiry daemon thread was interrupted and has stopped. Action More info at:
CWSIS2003E: The cache loader daemon ended abnormally due to an unexpected exception: {0}
Explanation The cache loader daemon thread was interrupted and has stopped. Action More info at:
CWSIS2004E: The expiry daemon is already running.
Explanation An attempt was made to start the expiry daemon thread but it is already running. Action More info at:
CWSIS9999E: {0}
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.