WebSphere Transaction Messages
WTRN0000E: An internal error occurred in method {0} in class {1}; the exception stack trace follows: {2}.
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
Consult the IBM WAS Support website
WTRN0001E: An internal error occurred in method {0} in class {1};
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
Consult the IBM WAS Support website.
WTRN0002W: The transaction service was unable to find resource class {0}.
Explanation:
The transaction service was unable to find the given XA resource class.
User Response:
Ensure that the associated XA resource provider is configured and restart the server. The resource can then be unconfigured and the server shutdown.
WTRN0003E: During recovery a required JAR file could not be found. The path use to locate it was {0}.
Explanation:
During recovery involving an embedded RAR a required JAR file could not be found. Without this JAR file transaction recovery cannot be completed.
User Response:
None. This is an internal system error.
WTRN0004W: Unable to create XAResourceFactory. The XAResourceFactory class name was {0}. The exception stack trace follows: {1}
Explanation:
This failure indicates that during server recovery, the given factory for creating XAResource objects could not be found. This is an internal system error.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0005W: An exception occured while creating an XAConnection and XAResource. The exception stack trace follows: {0}
Explanation:
A problem has occured attempting to access a resource provided by a resource manager (such as a database).
User Response:
Ensure the expected resource managers and resources are accessible. For example, ensure that all data sources are correctly defined.
WTRN0005W: The XAResource for a transaction participant could not be recreated and transaction recovery may not be able to complete properly. The resource was {0}. The exception stack trace follows: {1}
Explanation:
This failure indicates that during server recovery an XAResource object could not be recreated by its corresponding factory.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0006W: Encountered an error while closing XAConnection: {0} The exception stack trace follows: {1}
Explanation:
An SQLException occured when attempting to close a connection to the resource manager.
User Response:
No action is required, as this should not affect the running of the transaction service.
WTRN0006W: Transaction {0} has timed out after {1} seconds.
Explanation:
The transaction service has timed out (rolled back) the given transaction.
User Response:
To reduce future timeout occurrences, increase the transaction timeout values.
WTRN0007W: Transaction service unable to import transaction with null or invalid context.
Explanation:
A context was imported into the server with invalid or no transaction data so a transaction could not be initiated.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0008W: Transaction service unable to import nested transaction {0}
Explanation:
Importing of a nested transaction was attempted by a remote server. This is not supported.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0009E: No globalTID for coordinator resource.
Explanation:
No global transaction id was supplied in the imported transaction context.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0010E: Transaction rolledback due to exception on registering coordinator with superior {0}
Explanation:
A problem occurred importing a remote transaction into the server so the transaction was rolled back.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0011E: Unable to register transaction factory in JNDI namespace.
Explanation:
An unexpected error occurred during transaction service initialization.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0012E: Unexpected failure during transaction factory registration.
Explanation:
An unexpected error occurred during transaction service initialization.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0013W: No transaction log specified, logging in-memory
Explanation:
The transaction service is configured not to log to permanent storage. This may cause data integrity problems or locked resources (for example, database tables) if there are outstanding 2 phase commit transactions running when the server is terminated.
User Response:
If transaction recovery is required, then reconfigure the Transaction Service to use logging and restart the server.
WTRN0014I: The transaction service detected an invalid log file configuration string. The transaction service will continue without recovery logging.
Explanation:
The transaction service log file configuration string specified in systems management is invalid. The format should be a fully qualified log file directory optionally followed a ';' and the log file size. The log file size should be followed by either 'M' or 'K' to indicate megabytes or kilobytes respectively. The default and minimum log file size is 1M.
User Response:
Correct the transaction service log file configuration. Ensure that the server is cycled to enable transaction recovery logging.
WTRN0015E: Invalid transaction log file size specified: {0}. The transaction service will use default log file size of 1M.
Explanation:
The transaction service log file configuration string specified in systems management is invalid. The format should be a fully qualified log file directory optionally followed a ';' and the log file size. The log file size should be followed by either 'M' or 'K' to indicate megabytes or kilobytes respectively. The default and minimum log file size is 1M.
User Response:
Correct the transaction service log file configuration.
Explanation:
An exception was caught whilst the transaction service was attempting to recover from a previous server failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0017W: Unable to begin a nested transaction. Nested transactions are not supported.
Explanation:
This error indicates an attempt to begin a nested transaction, but nested transactions are not supported.
User Response:
Ensure that no attempt is made to begin a transaction when another transaction is already active on the thread of execution.
WTRN0018W: One-phase resource does not support commit
Explanation:
A resource that only supports one-phase optimized commit has been enlisted with the transaction service and called to process a standard two phase commit operation. This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0019E: The transaction service log file {0} has become corrupted.
Explanation:
The transaction service recovery log file has become corrupted and as a result server startup has failed.
User Response:
To cold start the server, delete the transaction log files and restart the server. It will be necessary to manually complete any transactions that were pending in associated resource managers.
WTRN0020W: Recovering transactions for server {0} on this server.
Explanation:
The transaction logs for server {0} are being recovered by this server. If resources configured on this server do not match those configured for the server for which the logs were created, then recovery may fail to complete.
User Response:
Check if any error messages are output during recovery and correct any actions requested.
WTRN0021W: TMRESUME is not supported.
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0022W: Unknown XAResource state.
Explanation:
An XAResource was in an unexpected state. This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0023W: Invalid XA end flag: {0}
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0024E: Inconsistent Transaction and XA Resource recovery logs.
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0025E: Recovery of Transaction failed {0}
Explanation:
An exception occurred whilst attempting to recover a transaction.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0026E: Exception caught during keypoint after recovery! {0}
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0027I: Transaction service recovering 1 transaction.
Explanation:
The transaction service has detected that a transaction was still running when the server was last terminated and is now in the process of recovering this transaction.
User Response:
No user action is required.
WTRN0028I: Transaction service recovering {0} transactions.
Explanation:
The transaction service has detected that transactions were still running when the server was last terminated and is now in the process of recovering these transactions.
User Response:
No user action is required.
WTRN0029E: Error closing the log in shutdown!
Explanation:
The transaction service encountered an error whilst closing its recovery log during server shutdown.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0030E: Recovery of XAResource data failed {0}
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0031E: An xa_rollback operation on a transactional resource failed. The global transaction was {0}. The exception stack trace follows: {1}
Explanation:
An exception occured when the transaction service called the xa_rollback operation on a resource enlisted with the given global transaction.
User Response:
This exception may indicate that a heuristic has occured. If this is the case, correct all application data problems that were caused by the heuristic decision.
WTRN0032E: Implementation specific transaction context received on inbound request.
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0033E: Transaction factory create caught exception {0}
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0034W: During server quiesce transaction {0} was found. The attempt to rollback the transaction succeeded.
Explanation:
During the quiesce phase of server shutdown an outstanding transaction was found. This transaction was rolledback successfully.
User Response:
No user action is required.
WTRN0035W: During server quiesce transaction {0} was found. The attempt to rollback the transaction failed.
Explanation:
During the quiesce phase of server shutdown an outstanding transaction was found. The transaction was not rolledback successfully.
User Response:
No user action is required. This transaction will be recovered when the server is next started.
WTRN0036W: During server quiesce transaction {0} was found. The transaction has been marked rollback only.
Explanation:
During the quiesce phase of server shutdown an outstanding transaction was found. This transaction was marked rollback only.
User Response:
No user action is required. The transaction will be rolledback during server shutdown or will be recovered upon server restart.
WTRN0037W: The transaction service encountered an error on an xa_recover operation. The resource was {0}. The error code was {1}. The exception stack trace follows: {2}
Explanation:
The transaction service encountered an error when calling xa_recover on a resource, in order to determine the prepared transactions held by the corresponding resource manager. The operation will be retried.
User Response:
Examine the error code in order to determine the cause of the failure.
WTRN0038W: An exception occured when destroying an XA resource. The exception stack trace follows: {0}
Explanation:
The transaction service was unable to destroy an XAResource.
User Response:
No action is required as this should not affect the running of the transaction service.
WTRN0039E: Unable to serialize an object to byte form.
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0040W: Object cannot be deserialized. The exception stack trace follows: {0}
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0041I: Transaction {0} has been rolled back.
Explanation:
Transaction {0} was previously marked rollbackOnly and has now been rolled back. This may be due to a transaction timeout or an application decision to mark the transaction rollbackOnly.
User Response:
No user action is required unless the rollback is undesirable and occurs as a result of a transaction timeout. If this is the case, investigate why the transaction takes longer to complete than the timeout period and consider increasing the duration of the transaction timeout values for the server.
WTRN0042I: GlobalTransaction rolled-back due to timeout or setRollbackOnly.
Explanation:
A Global transaction has been rolled-back due to a pre-defined timeout value being reached or setRollbackOnly being called.
User Response:
If the timeout value is too short/long modify using the Admin Console.
WTRN0043I: LocalTransaction rolled-back due to setRollbackOnly.
Explanation:
A Local transaction has been rolled-back due to setRollbackOnly being called.
User Response:
No user action is required.
WTRN0044W: A heuristic condition may have occurred for transaction {0}
Explanation:
The transaction service has detected that the specified transaction involved mixed one phase and two phase capable resources. The transaction service passed a one phase commit request to the single one phase capable resource, but the server failed before the commit could complete. It is not known if the resource committed successfully.
User Response:
All two phase capable resources will be rolled back. If the one phase capable resource successfully processed commit, then heuristic damage has occurred and all application data problems that were caused by the heuristic must be corrected.
WTRN0045W: The transaction service cannot recover resource {0}. The exception stack trace follows: {1}
Explanation:
An internal system error occured when the transaction service attempted to reconstruct a transaction participant during recovery. This is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0046E: An attempt by the transaction manager to call prepare on a transactional resource has resulted in an error. The error code was {0}. The exception stack trace follows: {1}
Explanation:
The transactional resource failed when being asked to process a prepare call. The failure will be treated as a rollback vote.
User Response:
Examine the error code to determine the cause of the problem.
WTRN0047W: An XAER_RMERR occured when committing the work on a transaction branch. The resource was: {0}
Explanation:
A failure has been detected during the commit process for a transaction.
User Response:
Correct any application data problems that were caused by this failure.
WTRN0048W: An attempt by the transaction manager to call commit on a transactional resource has resulted in an XAER_RMFAIL error. The resource was {0}
Explanation:
The commit call on a transactional resource did not succeed as the resource manager was unavailable. The commit call will be retried at regular intervals.
User Response:
Ensure that the resource manager is available.
WTRN0049W: An attempt by the transaction manager to call rollback on a transactional resource has resulted in an XAER_RMFAIL error. The resource was {0}
Explanation:
The rollback call on a transactional resource did not succeed as the resource manager was unavailable.
User Response:
The rollback call will be retried at regular intervals. Ensure that the resource manager is available.
WTRN0050E: An attempt by the transaction manager to call commit on a transactional resource has resulted in an unexpected error. The XA error code was {0}.
Explanation:
The commit call on a transactional resource did not succeed due to an unexpected failure.
User Response:
The commit call will be retried at regular intervals. Examine the error code in order to determine the cause of the problem.
WTRN0051E: An attempt by the transaction manager to call rollback on a transactional resource has resulted in an unexpected error. The XA error code was {0}.
Explanation:
The rollback call on a transactional resource did not succeed due to an unexpected failure.
User Response:
The rollback call will be retried at regular intervals. Examine the error code in order to determine the cause of the problem.
WTRN0052E: An attempt by the transaction manager to call one phase commit on a transactional resource has resulted in an XAER_RMFAIL error. The resource was {0}
Explanation:
The one phase commit call on a transactional resource did not succeed as the resource manager was unavailable.
User Response:
The transaction will be rolled back.
WTRN0053E: An attempt by the transaction manager to call one phase commit on a transactional resource has resulted in an unexpected error. The XA error code was {0}.
Explanation:
The one phase commit call on a transactional resource did not succeed due to an unexpected failure.
User Response:
The transaction manager will attempt to rollback the transaction.
WTRN0054W: An xa_forget operation on a transactional resource encountered an exception. The error code was {0}. The exception stack trace follows: {1}
Explanation:
An exception occured when the transaction service called the xa_forget operation on a resource.
User Response:
Examine the error code to determine what caused this error.
WTRN0055W: Giving up on outcome delivery for transaction {0}.
Explanation:
The transaction service was unable to deliver a commit or rollback outcome to a transaction participant.
User Response:
Correct any application data problems that were caused by this failure.
WTRN0056I: Transaction {0} resynchronization from originator failed, retrying....
Explanation:
A transaction has failed to resync during recovery and the outcome is unknown so the server will continue to retry.
User Response:
No user action is required.
WTRN0057E: Heuristic raised on prepare/commit_one_phase on subordinate.
Explanation:
A subordinate transaction attempted to optimize using one-phase commit during prepare and a heuristic error occurred.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0058E: Exception caught from commit operation during recovery of transaction {0}: {1}
Explanation:
An exception was caught while attempting to recover a transaction.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0059E: Exception caught from rollback operation during recovery of transaction {0}: {1}
Explanation:
An exception was caught while attempting to recover a transaction.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0060E: Exception caught from forget operation during recovery of transaction {0}: {1}
Explanation:
An exception was caught while attempting to recover a transaction.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0061E: Encountered an error while building a JTAXAResource object
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0062E: An illegal attempt to use multiple resources that have only one-phase capability has occurred within a global transaction.
Explanation:
Only a single resource that is limited to one-phase capability may be enlisted in a global transaction. This error occurs if muliple resource managers that are only one-phase capable are used within a global transaction or if multiple unshared connections from a single such resource manager are used within a global transaction.
User Response:
Modify the application to use only a single resource that is limited to one-phase capability or else use two-phase capable XAResources.
WTRN0063E: An illegal attempt to commit a one phase capable resource with existing two phase capable resources has occurred.
Explanation:
The transaction service has refused an attempt to commit a one phase capable resource with a transaction already involving other two phase capable resources. Either Last Participant Support (LPS) is not available, or if LPS is available, the application does not accept the heuristic risk that this would involve.
User Response:
Ensure that one and two phase capable resources are not involved in the same transaction, or if LPS is available, reconfigure the application to accept the heuristic risk that this would involve.
WTRN0064E: An illegal attempt to commit a one phase capable resource in a subordinate transaction branch has occurred.
Explanation:
The transaction service has refused an attempt to commit a one phase capable resource within a distributed subordinate transaction branch. The transaction will be rolled back.
User Response:
Ensure that one phase capable resources are not involved in a subordinate branch of a distributed transaction.
WTRN0065W: XAResource is not known to this transaction. The resource was: {0}
Explanation:
The transaction manager was unable to delist an XAResource because it had not been previously enlisted with the current transaction. This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0066W: Encountered exception during transaction logfile write operation. The exception stack trace follows: {0}
Explanation:
An error occured writing to the transaction log file. The transaction will be rolled back.
User Response:
This is most likely to be an IO failure. Examine the exception stack trace to determine the cause of the problem.
WTRN0067W: The transaction service has detected usage that exceeds the WebSphere Application programming model
Explanation:
An application running in this server is using transaction service functionality that is not part of the WebSphere application programming model.
User Response:
Consider whether the application can be modified to only utilize the J2EE transaction functionality.
WTRN0068E: Commit failed with exception {0}
Explanation:
An exception occurred whilst the transaction was committing.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0069E: Commit received in bad transaction state {0}
Explanation:
The transaction was in an invalid state when asked to carry out commit processing.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0070E: One-phase commit failed with exception {0}
Explanation:
An exception occurred whilst the transaction was committing using the one-phase commit protocol.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0071E: Rollback failed with exception {0}
Explanation:
An exception occurred whilst the transaction was rolling-back.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0072E: Rollback received in bad transaction state {0}
Explanation:
The transaction was in an invalid state when asked to carry out rollback processing.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0073E: Forget received in bad transaction state {0}
Explanation:
The transaction was in an invalid state when asked to carry out forget processing.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0074E: Exception caught from {0} synchronization operation: {1}
Explanation:
An exception was thrown by a Synchronization object when it was informed of the transactions current completion state.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0075W: Transaction {0} received a heuristic exception when committing a resource.
Explanation:
The transaction service received a heuristic response when delivering a commit outcome to a transaction participant.
User Response:
Correct any application data problems that were caused by this failure.
WTRN0076W: Transaction {0} received a heuristic exception when rolling back a resource.
Explanation:
The transaction service received a heuristic response when delivering a rollback outcome to a transaction participant.
User Response:
Correct any application data problems that were caused by this failure.
WTRN0077W: Transaction {0} was cancelled by the operator.
Explanation:
The outcome delivery for the given transaction was abandonned at operator request.
User Response:
Correct any application data problems that were caused by this failure.
WTRN0078E: An attempt by the transaction manager to call start on a transactional resource has resulted in an error. The error code was {0}. The exception stack trace follows: {1}
Explanation:
The transactional resource failed when being asked to process a start call. The failure will cause the transaction to be rolled back.
User Response:
Examine the error code to determine the cause of the problem.
WTRN0079E: An attempt by the transaction manager to call end on a transactional resource has resulted in an error. The error code was {0}. The exception stack trace follows: {1}
Explanation:
The transactional resource failed when being asked to process an end call. The failure will cause the transaction to be rolled back.
User Response:
Examine the error code to determine the cause of the problem.
WTRN0080W: Transaction {0} has timed out due to no client activity for greater than {1} seconds.
Explanation:
The client has been inactive longer than inactivity timeout value of {1} seconds.
User Response:
This can be a normal occurrence if the client goes away and leaves a transaction active. If the client is still active, the administrator must determine whether to change the Client or Inactivity Timeout value.
WTRN0081W: The JTAXAResource object is null.
Explanation:
This is an internal system error and is probably caused by an earlier failure.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0082W: Transaction {0} was rolled back by the operator.
Explanation:
The given transaction was rolled back by operator request.
User Response:
Correct any application data problems that were caused by this failure.
WTRN0083W: The transaction log is full. Transaction {0} rolled back.
Explanation:
The transaction log files are full with records from active transactions. Any further two phase commit transactions will be rolled back until space is freed up in the log files when active transactions complete.
User Response:
If this problem occurs frequently, restart the server with a larger transaction log file size specification.
WTRN0084W: Enlist failed due to resource adapter terminating.
Explanation:
A request to enlist a resource within a transaction has been rejected as either the server or the resource adapter is being closed down.
User Response:
Rerun the transaction once the resource adapter is available,
WTRN0085E: No transaction found to dissociate from.
Explanation:
Internal system error.
User Response:
This is an internal error which should be reported to IBM.
WTRN0086I: XAException encountered during prepare phase for transaction {0}. Local resources follow.
Explanation:
Informational.
User Response:
Used by system administrators to manually recover after transaction errors.
WTRN0087I: XAException encountered during completion phase for transaction {0}. Local resources follow.
Explanation:
Informational.
User Response:
Used by system administrators to manually recover after transaction errors.
WTRN0088I: {0} encountered XAException with error code {1}.
Explanation:
Informational.
User Response:
Used by system administrators to manually recover after transaction errors.
WTRN0089I: {0}: Vote: {1}.
Explanation:
Informational.
User Response:
Used by system administrators to manually recover after transaction errors.
WTRN0090I: {0}: Vote: {1}. Result: {2}.
Explanation:
Informational.
User Response:
Used by system administrators to manually recover after transaction errors.
WTRN0091E: Failed to associate Execution Context. Xid: {0}, timeout {1}.
Explanation:
Internal system error.
User Response:
Examine related messages. If none, contact IBM Support
WTRN0100E: {0}
Explanation:
This message code is used to support messages that have not yet been allocated their own message code.
User Response:
Refer to the message text for more information.
Thu Oct 16 11:01:00 EDT 2003
|