Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/ . |
Explanation | There was an attempt to start a local transaction while a global transaction is active, which is not allowed. |
Action | Ensure that any global transaction is complete before performing work in a local transaction. |
Explanation | The container cannot resume a LocalTransactionContainment because a global transaction is currently active. |
Action | Ensure that any global transaction is completed or suspended before a LocalTransactionContainment is resumed. |
Explanation | A local transaction connection cannot be used because a global transaction is currently active. |
Action | Ensure that any global transaction is completed before performing work in a local transaction. |
Explanation | The container has attempted to enlist a resource when the resolution-control value is not ContainerAtBoundary. |
Action | 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/ . |
Explanation | The LocalTransactionContainment is not in a state where a resource can be enlisted. |
Action | 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/ . |
Explanation | A local transaction connection cannot be used because a global transaction is currently active. |
Action | Ensure that any global transaction is completed before performing work in a local transaction. |
Explanation | The application using the local transaction connection is configured for the container to be responsible for starting and resolving local transactions but the application has started a local transaction itself. |
Action | The application should follow the get-use-model of connection usage when using local transactions that are resolved by the container. |
Explanation | The LocalTransactionContainment is not in a state where a resource can be enlisted. |
Action | 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/ . |
Explanation | The LocalTransactionContainment cannot delist a resource because a global transaction is currently active. |
Action | 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/ . |
Explanation | The LocalTransactionContainment cannot delist a resource that has not been enlisted for cleanup. |
Action | 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/ . |
Explanation | The LocalTransactionContainment is not in a state where a resource can be delisted. |
Action | 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/ . |
Explanation | A Synchronization cannot be enlisted with the LocalTransactionContainment because a global transaction is currently active. |
Action | 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/ . |
Explanation | The LocalTransactionContainment is not in a state where a Synchronization can be enlisted. |
Action | 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/ . |
Explanation | The container could not start the local transaction. |
Action | Investigate the resource manager. |
Explanation | The container could not complete the local transaction. |
Action | Investigate the resource manager. |
Explanation | The Resources enlisted with the LocalTransactionContainment (LTC) were rolled back instead of committed because setRollbackOnly() was called on the LTC. |
Action | No action required. This message is for informational purposes only. |
Explanation | A LocalTransactionContainment was already active when an attempt was made to start a new one. |
Action | 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/ . |
Explanation | The LocalTransactionContainment under which the failed operation was performed has been marked rollback-only by the container. |
Action | Use trace to determine why the LocalTransactionContainment was marked rollback-only. |
Explanation | The LocalTransactionContainment under which the failed operation was performed is completing or complete. |
Action | 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/ . |
Explanation | The LocalTransactionCoordinator enlisted as an ActivitySessionResource completed with inconsistent results. |
Action | 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/ . |
Explanation | The LocalTransactionCoordinator enlisted as an ActivitySessionResource was reset because setRollbackOnly was called on the LocalTransactionContainment. |
Action | No action required. This message is for informational purposes only. |
Explanation | The LocalTransactionCoordinator enlisted as an ActivitySessionResource is not in a valid state for completion. |
Action | 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/ . |
Explanation | The ActivitySessionManager object could not be found in the JNDI namespace. |
Action | 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/ . |
Explanation | The current ActivitySession is not in the correct state for the LocalTransactionContainment to enlist as a resource. |
Action | 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/ . |
Explanation | An unexpected error occurred while attempting to enlist the LocalTransactionContainment with the ActivitySession service. |
Action | 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/ . |
Explanation | A LocalTransactionCoordinator is not associated with the current thread and so it cannot be cleaned up. |
Action | 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/ . |
Explanation | A LocalTransactionCoordinator is not associated with the current thread and so it cannot be completed. |
Action | 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/ . |
Explanation | The application identified in the message has been assembled with extensions that are not supported in the installed edition of the product. If the product allowed the application to run in the absence of the expected extension support, the behaviour might alter in a way that would impact data integrity; for example, updates to transactional data might occur under several transactions when the presence of the extension support would cause them to occur under the same transaction. Therefore, it is not safe to install the application. |
Action | Examine the application that has failed to install. If it can be run without the extension support, reassemble the application without specifying the extensions. If the application needs the extended support, install it only on application servers that provide that support. |
Explanation | The bean identified in the message has been assembled with extensions that are not supported. For this reason the application has not been installed. |
Action | The application that has failed to install must be reassembled with an alternate configuration for the bean. |
Explanation | The application identified in the message failed to install correctly and the application is not available. |
Action | 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/ . |
Explanation | A LocalTransactionContainment with incomplete local transaction resources ended, and caused the resources to be rolled back. |
Action | No action required. This message is for informational purposes only. |
Explanation | The local transaction resource was unresolved at the completion of the LocalTransactionContainment and was rolled back. |
Action | No action required. This message is for informational purposes only. |
Explanation | The LocalTransactionCoordinator that is enlisted as an ActivitySessionSynchronization completed during cleanup with inconsistent results. |
Action | 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/ . |
Explanation | The LocalTransactionCoordinator enlisted as an ActivitySessionSynchronization was reset. |
Action | An application error may have occurred. Examine any related messages to determine the cause of the reset. |
Explanation | A LocalTransactionCoordinator that is enlisted as an ActivitySessionSynchronization contains one or more resources that are not in a valid state for completion during cleanup. |
Action | 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/ . |
Explanation | A LocalTransactionContainment was already active when there was an attempt to start a global transaction. |
Action | 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/ . |