WebSphere Transaction Monitor messages

WLTC0001E: An internal error occurred in method {0} in class {1}; the exception stack trace follows: {2}.
Explanation: This exception is unexpected. The cause is not immediately known.
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/.

WLTC0002E: Cannot begin a LocalTransactionContainment because a global transaction is active.
Explanation: An illegal attempt has been made to start a local transaction while a global transaction is active.
User Response: Ensure any global transaction is complete before performing work in a local transaction.

WLTC0003E: Cannot resume a LocalTransactionContainment because a global transaction is active.
Explanation: The container cannot resume a LocalTransactionContainment because a global transaction is currently active.
User Response: Ensure any global transaction is completed/suspended before a LocalTransactionContainment is resumed.

WLTC0004E: Cannot enlist a local transaction Resource because a global transaction is active.
Explanation: A local transaction Connection cannot be used because a global transaction is currently active.
User Response: Ensure any global transaction is completed before performing work in a local transaction.

WLTC0005E: Cannot enlist Resource. The local-transaction resolution-control value is Application and so resources may only be enlisted for cleanup.
Explanation: The container has attempted to enlist a resource when the resolution-control value is not ContainerAtBoundary.
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/.

WLTC0006E: Cannot enlist Resource. The LocalTransactionContainment is completing or completed.
Explanation: The LocalTranactionContainment is not in a state where a resource can be enlisted.
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/.

WLTC0007E: Cannot enlist Resource for cleanup because a global transaction is active.
Explanation: A local transaction Connection cannot be used because a global transaction is currently active
User Response: Ensure any global transaction is completed before performing work in a local transaction.

WLTC0008E: Cannot enlist Resource for cleanup. The local-transaction resolution-control value is ContainerAtBoundary and so resources may not be enlisted for cleanup.
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.
User Response: The application should follow the get-use-model of Connection usage when using local transactions resolved by the container.

WLTC0009E: Cannot enlist Resource for cleanup. The LocalTransactionContainment is completing or completed.
Explanation: The LocalTranactionContainment is not in a state where a resource can be enlisted.
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/.

WLTC0010E: Cannot delist Rsourcee because a global transaction is active.
Explanation: The LocalTranactionContainment can not delist a resource because a global transaction is currently active.
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/.

WLTC0011E: Cannot delist Resource. It is not enlisted for cleanup in the LocalTransactionContainment.
Explanation: The LocalTranactionContainment can not delist a resource that has not been enlisted for cleanup.
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/.

WLTC0012E: Cannot delist Resource. LocalTransactionContainment is completing or completed.
Explanation: The LocalTranactionContainment is not in a state where a resource can be delisted.
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/.

WLTC0013E: Cannot enlist Synchronization because a global transaction is active.
Explanation: A Synchronization cannot be enlisted with the LocalTransactionContainment because a global transaction is currently active.
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/.

WLTC0014E: Cannot enlist Synchronization. LocalTransactionContainment is completing or completed.
Explanation: The LocalTranactionContainment is not in a state where a Synchronization can be enlisted.
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/.

WLTC0015E: Resource {0} failed to start. Exception stack trace follows: {1}.
Explanation: The container could not start the local transaction.
User Response: Investigate resource manager.

WLTC0016E: Resource {0} failed to complete. Exception stack trace follows: {1}.
Explanation: The container could not complete the local transaction.
User Response: Investigate resource manager.

WLTC0017E: Resources rolled back due to setRollbackOnly() being called.
Explanation: The Resources enlisted with the LTC were rolled back instead of committed due to setRollbackOnly() being called on the LTC.
User Response: None, this is for your information only.

WLTC0018E: Cannot begin a LocalTransactionContainment. A LocalTransactionContainment is already active.
Explanation: A LocalTransactionContainment was already active when an attempt was made to start a new one.
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/.

WLTC0019E: Cannot perform operation. The LocalTransactionContainment has been marked rollback-only.
Explanation: The LocalTransactionContainment under which the failed operation was performed has been marked rollback-only by the container.
User Response: Use trace to determine why the LocalTransactionContainment was marked rollback-only.

WLTC0020E: Cannot perform operation. The LocalTransactionContainment is completing or completed.
Explanation: The LocalTransactionContainment under which the failed operation was performed is completing or complete.
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/.

WLTC0021E: Resource's completed state is inconsistent.
Explanation: The LocalTransactionCoordinator enlisted as an ActivitySessionResource completed with inconsistent results.
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/.

WLTC0022E: Resource was reset due to setRollbackOnly being called on LTC
Explanation: The LocalTransactionCoordinator enlisted as an ActivitySessionResource was reset due to setRollbackOnly being called on the LTC
User Response: None, this is for your information only.

WLTC0023E: Resource failed to complete due to illegal state.
Explanation: The LocalTransactionCoordinator enlisted as an ActivitySessionResource is in an illegal state for completion.
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/.

WLTC0024E: Cannot contact ActivitySession service. Failed to lookup ActivitySessionManager.
Explanation: The ActivitySessionManager object could not be found in the JNDI namespace.
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/.

WLTC0025E: Cannot enlist with ActivitySession service. ActivitySession is in an illegal state.
Explanation: The current ActivitySession is not in the correct state for the LTC to enlist as a resource.
User Response:

WLTC0026E: An unexpected error occurred whilst interacting with the ActivitySession service.
Explanation: An unexpected error occurred whilst attempting to enlist the LTC with the ActivitySession service.
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/.

WLTC0027E: No LocalTransactionCoordinator to cleanup.
Explanation: A LocalTransactionCoordinator is not associated with the current thread and so cannot be cleaned up.
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/.

WLTC0028E: No LocalTransactionCoordinator to complete.
Explanation: A LocalTransactionCoordinator is not associated with the current thread and so cannot be completed.
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/.

WLTC0029E: Application install failed; the application component {0} has WebSphere deployment descriptor extensions that are not enabled in the installed edition of WebSphere Application Server; their use may result in loss of data integrity: ActivationPolicy is {1}; LocalTransactionBoundary is {2}.
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.
User Response: 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.

WLTC0030E: Application install failed; the application bean {0} is configured to manage its own transactions but has an incompatible local transaction resolution control setting of ContainerAtBoundary.
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.
User Response: The application that has failed to install must be reassembled with an alternate configuration for the bean.

WLTC0031E: Application install failed; the application component {0} could not be installed.
Explanation: The application identified in the message failed to install correctly. For this reason the application is not available.
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/.

WLTC0032W: One or more local transaction resources were rolled back during the cleanup of a LocalTransactionContainment.
Explanation: A LocalTransactionContainment with incomplete local transaction resources ended and caused the resources to be rolled back.
User Response: None, this is for your information only.

WLTC0033W: Resource {0} rolled back in cleanup of LocalTransactionContainment.
Explanation: The local transaction resource was unresolved at the completion of the LocalTransactionContainment and was rolled back.
User Response: None, this is for your information only.

WLTC0034E: LocalTransactionContainment completed state is inconsistent during cleanup.
Explanation: The LocalTransactionCoordinator enlisted as an ActivitySessionSynchronization completed during cleanup with inconsistent results.
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/.

WLTC0035W: An unresolved LocalTransactionContainment was reset during cleanup.
Explanation: The LocalTransactionCoordinator enlisted as an ActivitySessionSynchronization was reset.
User Response: An application error may have occured, examine any related messages in order to determine the cause of the reset.

WLTC0036E: One or more resources registered in a LocalTransactionContainment failed to complete during cleanup due to illegal state.
Explanation: A LocalTransactionCoordinator enlisted as an ActivitySessionSynchronization contains one or more resources in an illegal state for completion during cleanup.
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/.

WLTC0037E: Cannot start a global transaction. A LocalTransactionContainment is already active with work.
Explanation: A LocalTransactionContainment was already active when an attempt to start a global transaction was made.
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/.