StatisticsNameNotFoundException_info=CWSOM1007E: The statistics named={0}(String) is not recognized. The application requested a set of statistics that is not recognized. Correct the name of the requested statistics set. CheckpointEndNotFoundException_info=CWSOM1029E: No CheckpointEndLogRecord was found in the log file={0}(String). The log file ended before a checkpoint end record was found. The log files should contain at least one checkpoint start and one checkpoint end LogRecord. Determine how the log file became corrupted and restore a backup log file. DuplicateObjectStoreNameException_info=CWSOM1002E: Attempt to construct an ObjectStore using, storeName={0}(String) which has already been used by ObjectStore={1}. ObjectStore names must be unique within an ObjectManager. Choose a different name for the ObjectStore. InvalidTransactionException_info=CWSOM1016E: Attempt to unlock or replace a ManagedObject={0}(ManagedObject) by InternalTransaction={1}(InternalTransaction), when it was locked under transactionLock={2}(TransactionLock). An attempt was made to unlock or replace a ManagedObject under a different transaction to the one that locked it. The attempt is rejected. Examine the logic of the application that uses the ObjectManager Transaction.unlock(ManagedObject) interface and determine why the two transactions are different. GuardBytesException_info=CWSOM1048E: Object={0} discovered potentially corrupted data in Object={1}(Object). For data protected by Guard bytes, the ObjectManager discovered a mismatch in the value of the Guard bytes. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . SimplifiedSerializationSizeExceptionException_info=CWSOM1031E: Simplified serialization size exceeded maximumSize={0}(long) actualSize={1}(long). The size of a serialized ManagedObject exceeded the expected maximum size. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . InvalidLogFileTypeException_info=CWSOM1043E: ObjectManager was passed an invalid log file type={0}(int). The ObjectManager constructor was passed a log file type that was not recognized as one of the LOG_FILE_TYPE_XXXX types. The ObjectManager is not instantiated. Change the constructor invocation to use a recognized log file type. NoRestartableObjectStoresAvailableException_info=CWSOM1038E: ObjectManager={0} found that no restartable ObjectStores were available. The ObjectManager was asked to store a reference to a named ManagedObject. However there are no restartable ObjectStores in which to store it. Determine whether you need to use a named ManagedObject. If you do need to use a named ManagedObject, create a restartable ObjectStore. LogFileInUseException_info=CWSOM1022E: The log file name={0}(String), is already in use. The ObjectManager tried to obtain an exclusive lock on the log file but it was already in use. Determine if another ObjectManager or another program is trying to use the same log file. InvalidObjectStoreNameException_info=CWSOM1006E: ObjectStore={0}(ObjectStore) was pass an invalid name={1}(String). An ObjectStore was constructed using a name that is not valid. The ObjectManager did not create the ObjectStore. Examine the name to determine why it is not valid. NonExistentTransactionException_info=CWSOM1013E: Attempt to deregister a transaction that was not registered, transaction={0}(InternalTransaction). An internal error has been detected inside the ObjectManager. No further actions are allowed on the Transaction. CMG0002 StoreSequenceException_info=CWSOM1009E: ObjectStore={0}(ObjectStore) generated sequenceNumber={1}(Long) which was already used by{2}(ManagedObject). An internal error has occurred in the ObjectStore. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . LogFileFullException_info=CWSOM1027E: Log file was too full to accommodate a total of {0}(long) bytes, the request reserved {1}(long) additional bytes and the space available is {2}(long) bytes. An attempt was made to write more data to the log than the available file space allowed. The attempt is rejected and the transaction state is unchanged. Either, reduce the number of objects you update within your transactions. Reduce the number of transactions that are simultaneously active. Reduce the size of the ManagedObjects you update. Increase the size of your log file. CollectionNotEmptyException_info=CWSOM1033E: Collection {0} is not empty dirty size={1}(long), transaction={2}(Transaction). The ObjectManager was asked to delete a collection ( Map or List ) that was not empty.The collection contained some entries that were not deleted or were deleted by a transaction other than the one trying to delete the collection. Examine the logic of the application and discover why the transaction is tryingto delete the collection while it contains entries. StateErrorException_info=CWSOM1003E: Object {0} is now in error state, its previous invalid state={1}(int) {2}(String). An operation was requested on an object which is in a state, that is not valid for the operation. The operation fails and the object is transitioned to an error state. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . UnexpectedExceptionException_info=CWSOM1015E: ObjectManager unexpectedly caught exception={0}(Exception). An exception was caught by the ObjectManager, the ObjectManager was not able to take a reasonable action in response to the exception. Investigate and resolve the cause of the underlying exception. PermanentNIOException_info=CWSOM1041E: ObjectManager caught Exception={0}(java.nio.XXX Exception). An nio Exception was caught by the ObjectManager, the Input/Output operation could not be safely retried and was abandoned. The nio Exception contains the cause of the underlying problem. Investigate and fix the cause of the underlying nio Exception. StoreFileSizeTooSmallException_info=CWSOM1040E: ObjectStore fileSize too small, requested size={0}(long), existing size={1}(long) used size={2}(long). The ObjectManager was asked to reduce the size of a store file to a length that cannot not contain the existing ManagedObjects in the file. Make a request that is for enough space to contain the existing ManagedObjects. ObjectManagerState_ColdStart=CWSOM0001I: ObjectManager using logFile {0} was cold started. An empty logfile was given to the ObjectManager so it was cold started. None, unless you expected the ObjectManager to warm start. In which case, investigate why the log file was empty. InvalidStateException_info=CWSOM1011E: An invalid operation was attempted on Object={0} while it was in state={1}(int) {2}(String). An operation was attempted on the Object. The operation is not valid when the Object is in its current state. For example, you may have tried to delete a ManagedObject that is already deleted. The operation is rejected and the Object remains unchanged. Investigate the state of the Object and why the operation is being attempted. ThreadNotRunningException_info=CWSOM1051E: Thread={0} was asked to perform request={1} after it had stopped running. The specified thread failed or been requested to stop when the request was made. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . InMemoryObjectNotAvailableException_info=CWSOM1030E: A memory based ObjectStore {0} was asked to retrieve a ManagedObject for Token={0}(Token), that was not already in memory. The ObjectManager was asked to retrieve a ManagedObject which should have been in memory but was not found. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . StoreFileInUseExceptionException_info=CWSOM1036E: ObjectStore={0}(ObjectStore) name={1}(String) is already in use. The ObjectStore found that it was already locked when it tried to take an exclusive lock on its file. Determine if the ObjectStore file is being used by another ObjectManager of if the file is being used by another program. ObjectStore_UnsafeToFlush=CWSOM0200W: The ObjectStore {0} with strategy STRATEGY_SAVE_ONLY_ON_SHUTDOWN could not safely be closed. If there are active transactions at shutdown. ObjectStores with strategy STRATEGY_SAVE_ONLY_ON_SHUTDOWN cannot safely close as active transactions exist. Closing the ObjectStore might lead to it saving inconsistent data. The ObjectStore is left unchanged. Examine why active transactions exist. These active transactions might exist be because you are using an external transaction manager. If you cannot avoid having active transactions at shutdown then use an ObjectStore with a different storage strategy. PermanentIOException_info=CWSOM1004E: ObjectManager caught IOException={0}(java.io.IOException). An IOException was caught by the ObjectManager, the IO operation could not be safely retried and was abandoned. The IOException describes the specific error. Investigate and fix the cause of the underlying IOException. ObjectManagerState_LogTooFull=CWSOM0005W: The ObjectManager found that the logFile was too full and will back out transaction {0}. The ObjectManager was short of log file space after it had completed a checkpoint, it backed out the largest transaction in the log in order to release some space. You are trying to do too much transactional work for the size of log file you have configured. Consider whether your transactions are attempting to do too many updates, or whether you are trying to update too many large objects, or whether you are trying to run too many transactions at the same time, or whether your log file is too small and should be made larger. ObjectSignatureNotFoundException_info=CWSOM1045E: The ObjectManager attempted to deserialize a ManagedObject with signature={0}(int) which it did not recognize. An unrecognized signature was found in a ManagedObject.Thus the deserialization was abandoned. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . InvalidObjectToStoreException_info=CWSOM1008E: ObjectStore={0}(ObjectStore) was requested to store invalid ManagedObject={1} (ManagedObject). An ObjectStore was asked to store a ManagedObject that is not valid. The Objectstore did not store the ManagedObject. Examine the ManagedObject to be stored and determine why it is not valid. For example it might be a null ManagedObject. InvalidLogRecordPartTypeException_info=CWSOM1028E: Invalid Log Record part type={0}(byte). A type flag on log record part was not recognized. Determine how the log file became corrupted and restore a backup log file. XIDTooLongException_info=CWSOM1025E: Attempt to set a transaction XID which is too long XID.length={0}(int). An X/Open transaction identifier XID can have a maximum length as specified by java.lang.Short.MAX_VALUE. Use a shorter XID length. ObjectStoreFullException_info=CWSOM1042E: ObjectStore={0}(ObjectStore) was asked to allocate space for ManagedObject={1}(ManagedObject) when it was full. An ObjectStore was already full when a new allocate request was made. The allocation request is refused. Decide if you should make the ObjectStore larger or determine whether to remove some existing objects. Also you might be trying to store more or larger objects than you had planned. TransactionCapacityExceededException_info=CWSOM1035E: The maximum number of active transactions was temporarily reduced current active transactions={0}(long) current capacity ={1}(long). The ObjectManager was asked to start more transactions than it can support with the resources available to it. The ObjectManager reduces the number of tranactions it will start so that checkpoints can complete before the log file fills.The new transaction did not begin. Either increase the size of the log file or start fewer transactions. ObjectStore_AllocateFileSpaceFailed=CWSOM0201W: The ObjectStore requested {0} bytes of storage when it currently has {1} bytes but received exception{2}. The file system cannot allocate the required space. Attempts to allocate objects in the ObjectStore will fail. Examine the exception and determine why the space cannot be allocated in thefile system. TEMPORARY_SIOM9999=CWSOM9999E: {0} If the message does not give sufficient information.See related messages for further help. See previous messages for further information. LogFileExhaustedException_info=CWSOM1018E: The Object={0}(Object) detected the end of the input log file because of the underlying Exception={1}(Exception). The ObjectManager has detected the end of the input log file. No action is required if this exception has occurred as a result of reading the log to the end at restart of the ObjectManager. SubListEntryNotInListException_info=CWSOM1044E: List={0}(List) was asked to create a sublist delimited by List.Entry={1}(List.Entry) which it did not contain. A list was requested to create a sublist delimited by entries it did not contain. The sublist was not created. Review the application code to determine why the entry was not in the list. For example the entry might have already been removed from the list. ObjectManagerState_ShutdownFast=CWSOM0004I: ObjectManager using logFile {0} has shut down without performing a final checkpoint. The ObjectManager was requested to shutdown without performing a final checkpoint, or shut down because of some previous error. None, unless you did not expect the ObjectManager to shut down without performing a final checkpoint. Examine diagnostic output to determine the cause of a unexpected shutdown. DuplicateKeyExceptionException_info=CWSOM1039E: Duplicate key={0}(Object) conflicts with existing entry={1}(Map.Entry) locked by transaction={3}(InternalTransaction). An attempt was made to add a unique key to a Map when an identical key already exists in the Map.The existing key is already part of another transaction and cannot be replaced with the new key. Either request addition of a duplicate key using the putDuplicate methodor find out why the application is trying to replace an existing key. UnknownObjectStoreException_info=CWSOM1020E: Attempt to locate an ObjectStore that was not registered, storeName={0}(String). The ObjectManager was asked to locate an ObjectStore that was not registered with it. The ObjectStore may have been removed from the ObjectManager. Recreate the ObjectStore. XIDModificationException_info=CWSOM1024E: Attempt to set a transaction XID when it is already set existing XID={0}([]byte) rejectedXID={1}([]byte). A transaction may only have one X/Open transaction identifier XID only. This cannot be modified after it is set. Examine the logic of the application and determine why it is trying to change the XID of a transaction that the application has already set. ObjectManagerState_WarmStart=CWSOM0002I: ObjectManager using logFile {0} was warm started logFileType={1}. A valid logfile was given to the ObjectManager which it was able to restart from. None, unless you expected the ObjectManager to cold start. In which case, investigate why the log file was not empty. InvalidStoreSignatureException_info=CWSOM1049E: ObjectStore name={0} discovered corrupted signature={1}(String) instead of the correct signature={2}(String). The ObjectStore has a corrupted header and cannot be processed. Determine how the file became corrupted and restore a backup. ReplacementException_info=CWSOM1010E: ObjectStore {0} was asked to replace ManagedObject {1} referenced by Token {2} when a different Token {3} which already existed in the store. A Token is identified by an objectStoreIdentifier and a storedObjectIdentifier. Only one token of each identity store may exist, but the new Token and an existing one share the same identity. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . InvalidLogFileSignatureException_info=CWSOM1050E: A corrupted signature={0}(String) was found in the log file instead of the correct signature={1}(String). The log file has a corrupted header and cannot be processed. Determine how the file became corrupted and restore a backup. PrematureEndOfLogFileException_info=CWSOM1037E: Log File name={0}(String), physical size found shorter than expected size={1}(long) trying to access byte={2}(Long). The log file does not end normally, the physical file might be truncated. Determine of the log file is damaged, restore the original undamaged file. InvalidConditionException_info=CWSOM1021E: Invalid condition detected by {0}(Object). Variable={1} contained value={2}. In internal error has occurred and a condition that is not valid has been found. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . InvalidStoreStrategyException_info=CWSOM1046E: ObjectStore={0} was constructed using an invalid store strategy={1}(int). ObjectStores can only be constructed with valid storage strategies. Use a valid storage strategy to construct the ObjectStore. Refer to the ObjectManagerjavadoc for valid strategies. NonExistentObjectStoreFileException_info=CWSOM1052E: ObjectStore={0}(ObjectStore) caught exception={1}(Exception) trying to locate or create file name={2}(String). An exception was caught when the ObjectStore tried to open the named file. The ObjectManager will not start. Verify that the file name is valid, that the file exists, and that the ObjectManager has the appropriate permissions to write it. If necessary provide a mapping of the logical store name to the physical location of the file when the ObjectManager starts. NonExistentLogFileException_info=CWSOM1017E: ObjectManagerState={0}(ObjectManagerState) caught exception={1}(Exception) trying to locate or create log file name={2}(String). An exception was caught when the ObjectManager tried to open the named log file. The ObjectManager will not start. Verify that the log file name is valid, and that the ObjectManager has the appropriate permissions to write it. NonExistentObjectStoreTemporaryIOException_info=CWSOM1014E: Attempt to locate an ObjectStore that was not registered, storeIdentifier={0}(int). A reference was made by a token to an ObjectStore that is not known to the ObjectManager. If the ObjectStore was removed from the ObjectManager this exception will be caught whenever existing Tokens reference the Objectstore. Reinstate the ObjectStore or stop using the Tokens that attempt to access it. InterfaceDisabledExceptionException_info=CWSOM1026E: Attempt to use disabled methodName={1}(String) in source={0}(Object). An attempt was made to use an interface that is disabled. Stop using the interface, or switch to a version of the ObjectManager that supports the interface. TemporaryIOException_info=CWSOM1005E: ObjectManager caught IOException={0}(java.io.IOException). An IOException was caught by the ObjectManager, the IO operation was abandoned, but could be safely retried by retrying the ObjectManager application programming interface (API), after the underlying cause is fixed. The IOException describes the specific error. Investigate and fix the cause of the underlying IOException, then retry the operation. DuplicateTransactionException_info=CWSOM1012E: ObjectManagerState={0}(ObjectManagerState) attempted to register or free a new transaction={1}(InternalTransaction) that the same LogicalUnitOfWork identifier as transaction={2}(InternalTransaction). The ObjectManager has discovered a new and existing transaction that have the same transaction identifier. This is an internal error and should not occur. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ClassNotFoundException_info=CWSOM1001E: ObjectManager caught ClassNotFoundException={0}(java.lang.ClassNotFoundException) while trying to deserialize an ManagedObject. A java.lang.ClassNotFoundException was caught when the ObjectManager attempted to deserialize a ManagedObject. The exception contains the name of the class that could not be found. Make it available to the ObjectManagers class loader, for example by including the class file on the class path. LogFileHeaderCorruptException_info=CWSOM1023E: Log file has no valid header. The transaction log file contained data that the ObjectManager cannot interpret. Check that the log file is the correct file. ObjectManagerState_Shutdown=CWSOM0003I: ObjectManager using logFile {0} has shut down. The ObjectManager was requested to shutdown. None, unless you did not expect the ObjectManager to shut down. InvalidLogRecordTypeException_info=CWSOM1019E: Invalid log record type={0}(int) was read from the transaction log. The ObjectManager was recovering and found a log record with a type that it did not recognize, the ObjectManager is not instantiated. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . DuplicateObjectStoreIdentifierException_info=CWSOM1047E: Attempt to construct an ObjectStore using, storeName={0}(String) and identifier {1} which has already been used by ObjectStore={2} ObjectStore identifiers must be unique within an ObjectManager. Add existing ObjectStores to the ObjectManagerbefore creating new Objectstores. This procedure enables the ObjectManager to avoid reusing the identifier. LogFileSizeTooSmallException_info=CWSOM1032E: Log fileSize too small, existing size={0}(long) requested size ={1}(long) available space={2}(long) predicted occupancy={3}(float) occupancy threshold={4}(float). The ObjectManager was asked to reduce the size of the transaction log. The requested size was too small to contain the existing log data. The new size is below the limit which will currently allow the ObjectManager to function without continually performing checkpoints. Make a larger request or reduce the load on the log by writing fewer or smaller ManagedObjects. TooManyTransactionsException_info=CWSOM1034E: An application attempted to start more that the defined maximum={0}(long) number of transactions. The ObjectManager was asked to start more transactions than specified in its configuration.The new transaction did not begin. Examine the logic of the application and discover why it tried to start too many transactions. It is possible that the application is starting transactions, but not committing them or backing them out. InternalTransaction_BackoutOrphan=CWSOM0100W: A transaction {0} was discovered during garbage collection and will be backed out. The application lost its reference to a transaction and cannot complete the transaction. Thus, the ObjectManager will back out the transaction in order to free up its resources. Your application lost its reference to a transaction. If the application terminated abnormally there us nothing further to do. If however, the application lost its reference without terminating abnormally this could be considered to be a logic error in the application.