Explanation | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | An illegal attempt has been made to start a local transaction while a global transaction is active. |
Action | Ensure 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 any global transaction is completed/suspended before a LocalTransactionContainment is resumed. |
Explanation | A local transaction Connection cannot be used because a global transaction is currently active. |
Action | Ensure 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The LocalTranactionContainment is not in a state where a resource can be enlisted. |
Action | 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/. |
Explanation | A local transaction Connection cannot be used because a global transaction is currently active |
Action | Ensure 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 resolved by the container. |
Explanation | The LocalTranactionContainment is not in a state where a resource can be enlisted. |
Action | 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/. |
Explanation | The LocalTranactionContainment can not delist a resource because a global transaction is currently active. |
Action | 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/. |
Explanation | The LocalTranactionContainment can not delist a resource that has not been enlisted for cleanup. |
Action | 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/. |
Explanation | The LocalTranactionContainment is not in a state where a resource can be delisted. |
Action | 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/. |
Explanation | A Synchronization cannot be enlisted with the LocalTransactionContainment because a global transaction is currently active. |
Action | 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/. |
Explanation | The LocalTranactionContainment is not in a state where a Synchronization can be enlisted. |
Action | 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/. |
Explanation | The container could not start the local transaction. |
Action | Investigate resource manager. |
Explanation | The container could not complete the local transaction. |
Action | Investigate resource manager. |
Explanation | The Resources enlisted with the LTC were rolled back instead of committed due to setRollbackOnly() being called on the LTC. |
Action | None, this is for your information only. |
Explanation | A LocalTransactionContainment was already active when an attempt was made to start a new one. |
Action | 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/. |
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The LocalTransactionCoordinator enlisted as an ActivitySessionResource completed with inconsistent results. |
Action | 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/. |
Explanation | The LocalTransactionCoordinator enlisted as an ActivitySessionResource was reset due to setRollbackOnly being called on the LTC |
Action | None, this is for your information only. |
Explanation | The LocalTransactionCoordinator enlisted as an ActivitySessionResource is in an illegal state for completion. |
Action | 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/. |
Explanation | The ActivitySessionManager object could not be found in the JNDI namespace. |
Action | 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/. |
Explanation | The current ActivitySession is not in the correct state for the LTC to enlist as a resource. |
Action |
Explanation | An unexpected error occurred whilst attempting to enlist the LTC with the ActivitySession service. |
Action | 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/. |
Explanation | A LocalTransactionCoordinator is not associated with the current thread and so cannot be cleaned up. |
Action | 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/. |
Explanation | A LocalTransactionCoordinator is not associated with the current thread and so cannot be completed. |
Action | 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/. |
Explanation | The application identified in the message has been assembled with extensions that are not supported in the installed edition of WebSphere. If WebSphere allowed the application to run in the absence of the expected extension support the behaviour could be altered in a way that would impact data integrity; for example, updates to transactional data may take place under several transactions when the presence of the extension support would cause them to occur under the same transaction. For this reason it is not safe for the application to be installed. |
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 it must only be installed on WebSphere 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. For this reason the application is not available. |
Action | 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/. |
Explanation | A LocalTransactionContainment with incomplete local transaction resources ended and caused the resources to be rolled back. |
Action | None, this is for your information only. |
Explanation | The local transaction resource was unresolved at the completion of the LocalTransactionContainment and was rolled back. |
Action | None, this is for your information only. |
Explanation | The LocalTransactionCoordinator enlisted as an ActivitySessionSynchronization completed during cleanup with inconsistent results. |
Action | 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/. |
Explanation | The LocalTransactionCoordinator enlisted as an ActivitySessionSynchronization was reset. |
Action | An application error may have occured, examine any related messages in order to determine the cause of the reset. |
Explanation | A LocalTransactionCoordinator enlisted as an ActivitySessionSynchronization contains one or more resources in an illegal state for completion during cleanup. |
Action | 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/. |
Explanation | A LocalTransactionContainment was already active when an attempt to start a global transaction was made. |
Action | 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/. |