WTRN

WTRN0000E: 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.

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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .

WTRN0001E: An internal error occurred in method {0} in class {1};

Explanation

This exception is unexpected. The cause is not immediately known.

Action

WTRN0002W: The transaction service was unable to find resource class {0}.

Explanation

The transaction service could not find the XA resource class identified in the message.

Action

Ensure that the associated XA resource provider is configured and restart the server. The resource can then be unconfigured and the server shut down.

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 file, a required JAR file could not be found. Without this JAR file, transaction recovery cannot be completed.

Action

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

During server recovery, the identified factory for creating XAResource objects could not be found. This is an internal system error.

Action

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

During server recovery, an XAResource object could not be recreated by its corresponding factory.

Action

WTRN0006W: Transaction {0} has timed out after {1} seconds.

Explanation

The transaction service has timed out (rolled back) the transaction identified in the message.

Action

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 either no transaction data, or transaction data that is not valid, so a transaction could not be initiated.

Action

WTRN0008W: Transaction service unable to import nested transaction {0}

Explanation

A remote server attempted to import a nested transaction. This action is not supported.

Action

WTRN0009E: No globalTID for coordinator resource.

Explanation

No global transaction id was supplied in the imported transaction context.

Action

WTRN0010E: Transaction rolledback due to exception on registering coordinator with superior {0}

Explanation

There was a problem when a remote transaction was imported into the server, so the transaction was rolled back.

Action

WTRN0011E: Unable to register transaction factory in JNDI namespace.

Explanation

An unexpected error occurred during initialization of the transaction service.

Action

WTRN0012E: Unexpected failure during transaction factory registration.

Explanation

An unexpected error occurred during initialization of the transaction service.

Action

WTRN0013W: No transaction log specified, logging in-memory

Explanation

The transaction service is configured so that it does not write a log to permanent storage. This might cause data integrity problems or locked resources (for example, database tables) if there are outstanding two-phase commit transactions running when the server is stopped.

Action

If you require transaction recovery, 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 directory name for the transaction log file, set in the Transaction log directory field, is not valid. The format should be a fully qualified log file directory, optionally followed by a ";" and the log file size, with M after the log file size to indicate megabytes, or K to indicate kilobytes. The default and minimum log file size is 1M.

Action

Correct the Transaction log directory configuration. Ensure that the server is restarted 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 file size of the transaction log file, set in the Transaction log directory field, is not valid. The format should be a fully qualified log file directory, optionally followed by a ";" and the log file size, with M after the log file size to indicate megabytes, or K to indicate kilobytes. The default and minimum log file size is 1M.

Action

Correct the Transaction log directory configuration.

WTRN0016E: Exception caught during transaction service recovery! {0}

Explanation

An exception was detected while the transaction service was attempting to recover from a previous server failure.

Action

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.

Action

Ensure that there is not an attempt to begin a transaction when another transaction is already active on the thread.

WTRN0018W: One-phase resource does not support commit

Explanation

A resource that supports only 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.

Action

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.

Action

To cold start the server, delete the transaction log files and restart the server. You must manually complete any transactions that were pending in associated resource managers.

WTRN0020W: Recovering transactions for server {0} on this server.

Explanation

This server is recovering transaction logs from another server. If the resources configured on this server do not match those configured on the server for which the logs were created, recovery might not complete.

Action

Check whether 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.

Action

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.

Action

WTRN0023W: Invalid XA end flag: {0}

Explanation

This is an internal system error and is probably caused by an earlier failure.

Action

WTRN0024E: Inconsistent Transaction and XA Resource recovery logs.

Explanation

This is an internal system error and is probably caused by an earlier failure.

Action

WTRN0025E: Recovery of Transaction failed {0}

Explanation

An exception occurred while attempting to recover a transaction.

Action

WTRN0026E: Exception caught during keypoint after recovery! {0}

Explanation

This is an internal system error and is probably caused by an earlier failure.

Action

WTRN0027I: Transaction service recovering 1 transaction.

Explanation

The transaction service has detected that a transaction was still running when the server was last stopped and the transaction service is now recovering this transaction. Further audit messages may be output indicating the progress of recovery processing.

Action

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 stopped and the transaction service is now recovering these transactions. Further audit messages may be output indicating the progress of recovery processing.

Action

No user action is required.

WTRN0029E: Error closing the log in shutdown!

Explanation

The transaction service encountered an error while closing its recovery log during server shutdown.

Action

WTRN0030E: Recovery of XAResource data failed {0}

Explanation

This is an internal system error and is probably caused by an earlier failure.

Action

WTRN0031E: An xa_rollback operation on a transactional resource failed. The global transaction was {0}. The exception stack trace follows: {1}

Explanation

An exception occurred when the transaction service called the xa_rollback operation on a resource that was enlisted with the global transaction identified in the message.

Action

The transaction might have completed with a heuristic outcome. If this is the case, correct all application data problems that were caused by the heuristic outcome.

WTRN0032E: Implementation specific transaction context received on inbound request.

Explanation

This is an internal system error and is probably caused by an earlier failure.

Action

WTRN0033E: Transaction factory create caught exception {0}

Explanation

This is an internal system error and is probably caused by an earlier failure.

Action

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 rolled back successfully.

Action

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 rolled back successfully.

Action

No 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.

Action

No action is required. The transaction will be rolled back during server shutdown, or will be recovered when the server is restarted.

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, to determine the prepared transactions held by the corresponding resource manager. The operation will be retried.

Action

Examine the error code to determine the cause of the problem.

WTRN0038W: An exception occured when destroying an XA resource. The exception stack trace follows: {0}

Explanation

The transaction service could not destroy an XAResource.

Action

No action is required, because this should not affect 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.

Action

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.

Action

WTRN0041I: Transaction {0} has been rolled back.

Explanation

A transaction was previously marked rollbackOnly and has now been rolled back. This might be because of a transaction timeout, or an application decision to mark the transaction rollbackOnly.

Action

No user action is required unless the rollback is undesirable and occurs because 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 transaction timeout values for the server.

WTRN0042I: GlobalTransaction rolled-back due to timeout or setRollbackOnly.

Explanation

A global transaction has been rolled back because either it has reached a timeout value, or the setRollbackOnly method has been called.

Action

If the timeout value is too short or long, use the Administrative console to modify it.

WTRN0043I: LocalTransaction rolled-back due to setRollbackOnly.

Explanation

A local transaction has been rolled back because the setRollbackOnly method has been called.

Action

No 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 whether the resource committed successfully.

Action

All two-phase capable resources will be rolled back. If the one-phase capable resource successfully processed commit, heuristic damage has occurred and you must correct all application data problems that are caused by the heuristic outcome.

WTRN0045W: The transaction service cannot recover resource {0}. The exception stack trace follows: {1}

Explanation

An internal system error occurred when the transaction service attempted to reconstruct a transaction participant during recovery. This is probably caused by an earlier failure.

Action

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.

Action

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.

Action

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 because the resource manager was unavailable. The commit call will be retried at regular intervals.

Action

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 because the resource manager was unavailable. The rollback call will be retried at regular intervals.

Action

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 because of an unexpected failure. The commit call will be retried at regular intervals.

Action

Examine the error code 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 because of an unexpected failure. The rollback call will be retried at regular intervals.

Action

Examine the error code 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 because the resource manager was unavailable.

Action

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 because of an unexpected failure.

Action

The transaction manager will attempt to roll back 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 occurred when the transaction service called the xa_forget operation on a resource.

Action

Examine the error code to determine the cause of the problem.

WTRN0055W: Giving up on outcome delivery for transaction {0}.

Explanation

The transaction service could not deliver a commit or rollback outcome to a transaction participant.

Action

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 resynchronize during recovery, and the outcome is unknown, so the server will continue to retry.

Action

No 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.

Action

WTRN0058E: Exception caught from commit operation during recovery of transaction {0}: {1}

Explanation

An exception was detected while attempting to recover a transaction.

Action

WTRN0059E: Exception caught from rollback operation during recovery of transaction {0}: {1}

Explanation

An exception was detected while attempting to recover a transaction.

Action

WTRN0060E: Exception caught from forget operation during recovery of transaction {0}: {1}

Explanation

An exception was detected while attempting to recover a transaction.

Action

WTRN0061E: Encountered an error while building a JTAXAResource object

Explanation

This is an internal system error and is probably caused by an earlier failure.

Action

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 can be enlisted in a global transaction. This error occurs if multiple resource managers that are only one-phase capable are used in a global transaction, or if multiple unshared connections from a single such resource manager are used in a global transaction.

Action

Modify the application either to use a single resource that is limited to one-phase capability, or to 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 that already involves 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.

Action

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 in a distributed subordinate transaction branch. The transaction will be rolled back.

Action

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 could not delist an XAResource because it was not previously enlisted with the current transaction. This is an internal system error and is probably caused by an earlier failure.

Action

WTRN0066W: Encountered exception during transaction logfile write operation. The exception stack trace follows: {0}

Explanation

An error occurred while writing to the transaction log file. The transaction will be rolled back.

Action

This is most likely to be an I/O 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 application programming model.

Action

Consider whether the application can be modified to use only transaction functionality that is supported in the application programming model.

WTRN0068E: Commit failed with exception {0}

Explanation

An exception occurred while the transaction was committing.

Action

WTRN0069E: Commit received in bad transaction state {0}

Explanation

The transaction was not in a valid state when it was asked to carry out commit processing.

Action

WTRN0070E: One-phase commit failed with exception {0}

Explanation

An exception occurred while the transaction was committing using the one-phase commit protocol.

Action

WTRN0071E: Rollback failed with exception {0}

Explanation

An exception occurred while the transaction was rolling back.

Action

WTRN0072E: Rollback received in bad transaction state {0}

Explanation

The transaction was not in a valid state when asked to carry out rollback processing.

Action

WTRN0073E: Forget received in bad transaction state {0}

Explanation

The transaction was not in a valid state when asked to carry out forget processing.

Action

WTRN0074E: Exception caught from {0} synchronization operation: {1}

Explanation

An exception was created by a Synchronization object when it was informed of the current completion state of the transaction.

Action

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.

Action

Correct any application data problems that were caused by the heuristic outcome.

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.

Action

Correct any application data problems that were caused by the heuristic outcome.

WTRN0077W: Transaction {0} was cancelled by the operator.

Explanation

The outcome delivery for the transaction identified in the message was abandoned at the request of the operator.

Action

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 transaction will be rolled back.

Action

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 transaction will be rolled back.

Action

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 for longer than the inactivity timeout value.

Action

Disregard this message if the client went away leaving a transaction active. If the client is still active, determine whether to change the Client Inactivity Timeout value.

WTRN0081W: The JTAXAResource object is null.

Explanation

This is an internal system error and is probably caused by an earlier failure.

Action

WTRN0082W: Transaction {0} was rolled back by the operator.

Explanation

The transaction identified in the message was rolled back by operator request.

Action

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. The server must be restarted for further two-phase commit work to proceed.

Action

If this problem occurs frequently, restart the server with a larger file size for the transaction log.

WTRN0084W: Enlist failed due to resource adapter terminating.

Explanation

A request to enlist a resource in a transaction was rejected because either the server, or the resource adapter, is being closed down.

Action

Rerun the transaction after the resource adapter becomes available.

WTRN0085E: No transaction found to dissociate from.

Explanation

This is an internal system error.

Action

WTRN0086I: XAException encountered during prepare phase for transaction {0}. Local resources follow.

Explanation

This message is for informational purposes only.

Action

System administrators can use this information to recover manually after transaction errors.

WTRN0087I: XAException encountered during completion phase for transaction {0}. Local resources follow.

Explanation

This message is for informational purposes only.

Action

System administrators can use this information to recover manually after transaction errors.

WTRN0088I: {0} encountered XAException with error code {1}.

Explanation

This message is for informational purposes only.

Action

System administrators can use this information to recover manually after transaction errors.

WTRN0089I: {0}: Vote: {1}.

Explanation

This message is for informational purposes only.

Action

System administrators can use this information to recover manually after transaction errors.

WTRN0090I: {0}: Vote: {1}. Result: {2}.

Explanation

This message is for informational purposes only.

Action

System administrators can use this information to recover manually after transaction errors.

WTRN0091E: Failed to associate Execution Context. Xid: {0}, timeout {1}.

Explanation

This is an internal system error.

Action

WTRN0092W: Incomplete transaction (localid={0}) found during server quiesce; transaction service will wait.

Explanation

Inbound transactional work has not yet completed. The transaction service will delay server shutdown so that the originator can try to complete the transaction.

Action

No action is required.

WTRN0093W: Outcome not available for subordinate transaction {0}. Transaction is heuristically committed.

Explanation

The transaction service could not obtain the outcome of the transaction from its superior in the configured retry period. The transaction will be heuristically committed.

Action

Correct any application data problems that were caused by the heuristic outcome.

WTRN0094W: Outcome not available for subordinate transaction {0}. Transaction is heuristically rolled back.

Explanation

The transaction service could not obtain the outcome of the transaction from its superior in the configured retry period. The transaction will be heuristically rolled back.

Action

Correct any application data problems that were caused by the heuristic outcome.

WTRN0095W: Outcome not available for subordinate transaction {0}. Transaction is awaiting administrator intervention to determine its outcome.

Explanation

The transaction service could not obtain the outcome of the transaction from its superior in the configured retry period. The transaction is now waiting for administrator to manually set the transaction outcome.

Action

Determine the success or failure of the superior transaction, then set the transaction outcome manually. This ensures that heuristic damage does not occur and that all application data remains correct.

WTRN0096W: A heuristic condition may have occurred for transaction {0}. Transaction is heuristically committed.

Explanation

The transaction service 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 whether the resource committed successfully.

Action

All two-phase capable resources will be committed. If the one-phase capable resource failed to process commit, heuristic damage has occurred and you must correct all application data problems that were caused by the heuristic outcome.

WTRN0097W: Unknown transaction outcome occurred for transaction {0}. Transaction is awaiting administrator intervention to determine its outcome.

Explanation

Action

Determine the success or failure of the one-phase commit request, then set the transaction outcome manually. This ensures that heuristic damage does not occur and that all application data remains correct.

WTRN0098W: Outcome not available for transaction {0} as resource adapter {1} has been uninstalled. Transaction is heuristically committed.

Explanation

The transaction service could not obtain the outcome of the transaction from the resource adapter because the resource adapter has been uninstalled. The transaction will be heuristically committed.

Action

Correct any application data problems that were caused by the heuristic outcome.

WTRN0099W: Outcome not available for transaction {0} as resource adapter {1} has been uninstalled. Transaction is heuristically rolled back.

Explanation

The transaction service could not obtain the outcome of the transaction from the resource adapter because the resource adapter has been uninstalled. The transaction will be heuristically rolled back.

Action

Correct any application data problems that were caused by the heuristic outcome.

WTRN0100E: {0}

Explanation

This message code is used to support messages that have not yet been allocated their own message code.

Action

Refer to the message text for more information.

WTRN0101W: Outcome not available for transaction {0} as resource adapter {1} has been uninstalled. Transaction is awaiting administrator intervention to determine its outcome.

Explanation

The transaction service could not obtain the outcome of the transaction from the resource adapter because the resource adapter has been uninstalled.

Action

Determine the success or failure of the transaction from the originator of the resource adapter transaction, then set the transaction outcome manually. This ensures that heuristic damage does not occur and that all application data remains correct.

WTRN0102W: A heuristic condition may have occurred for transaction {0}. Transaction is heuristically rolled back.

Explanation

Action

WTRN0103E: Recovery log is being marked as failed. [ {0} {1} ]

Explanation

The recovery log has failed, and no further access to the recovery log can occur. The component and the exception are indicated in the message.

Action

The server must be restarted so that the log can be repaired. Try to correct any conditions indicated by the exception in the message.

WTRN0104E: Details of recovery log failure: {0}

Explanation

This message is issued with message WTRN0103E to indicate the details of the recovery log failure.

Action

Use the information in this message along with message WTRN0103E to correct the condition that caused the recovery log to fail.

WTRN0105I: The transaction service has shutdown successfully with no transactions requiring recovery.

Explanation

This is a normal event. This message is for informational purposes only.

Action

No action is required.

WTRN0106I: Client JTA demarcation is disallowed.

Explanation

JTA demarcation has been configured as disallowed for this client application.

Action

To allow JTA demarcation, use the application server toolkit to set the Allow JTA Demarcation property in the client deployment descriptor.

WTRN0107W: {0}

Explanation

This message code is used to support messages that are not yet allocated their own message code.

Action

Refer to the message text for more information.

WTRN0108I: {0}

Explanation

This message code is used to support messages that are not yet allocated their own message code.

Action

Refer to the message text for more information.

WTRN0109W: Exception encountered when activating Transaction JMX MBean: {0}

Explanation

An error occurred when attempting to activate a JMX MBean for the transaction service. Although this does not stop the transaction service from starting, any administrative functions that require access to the transaction service will fail.

Action

WTRN0110W: {0} is not a valid transaction service custom property

Explanation

A custom property that was specified in the transaction service configuration for this server is not valid and has been ignored.

Action

Correct the transaction service custom properties configuration.

WTRN0111E: Unable to access or create the recovery log. The log configuration was {0}

Explanation

The transaction service could not access or create recovery logs. If the recovery logs are for the local server, the server will be stopped. If the recovery logs are for a peer recovered server, recovery will be stopped and assigned to another server, and the reporting server will continue normally.

Action

Examine any related messages to determine the cause of the problem. Ensure that the recovery logs can be access by the server or, if they are not yet created, check that there is sufficient disk space available and that the server has correct access permissions to the files or directories specified in the messages.

WTRN0112E: An unexpected error occured whilst opening the recovery log. The log configuration was {0}

Explanation

The transaction service could not open the recovery logs. If the recovery logs are for the local server, the server will be stopped. If the recovery logs are for a peer recovered server, recovery will be stopped and assigned to another server, and the reporting server will continue normally.

Action

Examine any related messages to determine the cause of the problem.

WTRN0113W: Recovery processing of a downlevel peer WebSphere server is not possible and has been halted ({0})

Explanation

The transaction service could not peer recover the specified application server because the logs were formatted by an earlier release of the product, which is incompatible with this server. This instance of peer recovery will be stopped and assigned to another server, and the reporting server will continue normally.

Action

No user action is required. Depending on the cluster configuration, if there is only a single member at a particular release level, peer recovery for that server release might not be possible if the log format has become incompatible across releases.

WTRN0114I: Transaction {0} could not notify all resources of its outcome. Will retry in {1} seconds.

Explanation

A remote resource manager could not be contacted during recovery restart. The operation will be retried at regular intervals.

Action

Ensure that the resource manager is available.

WTRN0115E: Channel Framework configuration is not defined or is invalid for WebServices Atomic Transactions (WSAT) support.

Explanation

The Web container is not defined to use the channel framework, or is defined incorrectly. WS-AT requires the use of channel framework to transfer transactional context between Web services.

Action

Correct or define the channel framework configuration for the Web container.

WTRN0116I: Invalid transaction log file configuration string specified: {0}. The transaction service will continue without recovery logging for WebSphere server ({1}).

Explanation

Action

Correct the Transaction log directory configuration. Ensure that the server is restarted to enable transaction recovery logging.

WTRN0117E: Invalid transaction log file size specified: {0}. The transaction service will use default log file size of 1M for WebSphere server ({1}).

Explanation

Action

Correct the Transaction log directory configuration.

WTRN0118W: The deprecated transaction service customer property {0} was found in the transaction service configuration.

Explanation

A deprecated custom property was specified in the transaction service configuration for this server. The property will override a corresponding general transaction service property in the configuration. The deprecated custom property will be removed in a future release of the product.

Action

Remove the deprecated transaction service custom property from the configuration and use the corresponding general property setting, using the administrative console.

WTRN0119W: Number of WS-TX protocol messages failing authorization: {0}

Explanation

The number of Web Services Atomic Transactions (WS-AT) and Web Service Business Activities (WS-BA) protocol messages indicated (for example, a prepare message) have been received without the expected security credentials.

Action

Ensure that the server is correctly configured for WS-AT and WS-BA in a secure environment.

WTRN0120W: The transaction log directory specification of ;0 for server {1} is not valid because the server is in a cluster {0} that is enabled for high availability (HA).

Explanation

You must specify a valid transaction log directory path for each server in a cluster when the cluster is enabled for high availability.

Action

Change the setting of the transaction log file to a valid location in the file system.

WTRN0121E: The high availability (HA) configuration is not valid. The server will stop.

Explanation

One or more servers in a cluster that is enabled for high availability do not have a valid transaction log directory defined.

Action

Examine accompanying messages for information about the affected servers. Correct the transaction log directories for these servers, then restart the cluster.

WTRN0122W: Transaction service log file {0} has used {1} bytes of a total of {2}. The size of the log file might need to be greater.

Explanation

After a successfully completed keypoint operation (during which deleted and completed entries are removed from a log file which has reached maximum capacity), it has been detected that the log file is still greater than 75% full because of the current active transactional workload. If the log file becomes full, the server must be restarted. Note that this message is only output after a successful keypoint operation on a log file; only then can the capacity of the logs currently in use be calculated.

Action

Consider setting a larger file size for the transaction logs.

WTRN0123E: An incorrect external WS-Transaction HTTP(S) URL prefix was specified: {0}

Explanation

The external WS-Transaction HTTP(S) URL prefix must be a valid URI.

Action

Specify a valid external WS-Transaction HTTP(S) URL prefix.

WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was {0}. The stack trace of this thread when the timeout occurred was: {1}

Explanation

The stack, captured when the timeout occurred, is provided to help with diagnosis and debugging of transaction timeouts.

Action

Examine the stack trace to determine what processing was in progress when the transaction timeout occurred.

WTRN0125W: Unable to target module {0} on node {1} because the module specifies Resource Commit Ordering support which is not supported on the node

Explanation

The support for resource commit ordering is only available on nodes which are at release 7.0 or later.

Action

Install the module on an Application Server at release 7.0 (or later) or use the application"s deployment descriptor editor in the application development tooling to remove any Resource Commit Ordering settings before installing the module. This may be performed by navigating to the commit ordering section of the WebSphere Extensions and unseting the commit priority for each transactional resource.

WTRN0126W: Unable to deploy application {0} on node {1} in cluster {2} because the application specifies Resource Commit Ordering support which is not supported on the node

Explanation

The support for resource commit ordering is only available on nodes which are at release 7.0 or later. The node will not be added to the cluster.

Action

Create cluster members on nodes which have an Application Server installed at release 7.0 (or later) or use the application"s deployment descriptor editor in the application development tooling to remove any Resource Commit Ordering settings before creating the cluster memeber. This may be performed by navigating to the commit ordering section of the WebSphere Extensions and unseting the commit priority for each transactional resource.

WTRN0127E: Operation blocked by policy type configuration.

Explanation

The operation was blocked in accordance with the effective policy type configuration.

Action

Ensure the policy type configuration is appropriate for this operation.

WTRN0128E: Unable to start application {0} because the application requires WS Transaction specifications which are not supported on all servers in the cluster.

Explanation

The application is configured with a WebService policy specifying WS Transaction specifications which are not supported on all servers in the cluster. Application requests or their recovery may be directed to any server in the cluster so all applications must use features which are supported on all servers.

Action

Uninstall the application or modify the WS Transaction policy configuration for the application to use supported features. Alternatively, upgrade all the nodes in the cluster to release 7.0 or later.

WTRN0129W: The default setting for WS Transaction specification level is inappropriate for a mixed version cluster

Explanation

The configured WS Transaction specification level default setting for the server may cause execution problems as all servers in the cluster are not at the same release of the Application Server. All servers in the cluster need to support the same specification level since application requests or their recovery may be directed to any server. If servers support different specification levels, then the application behaviour may change depending on which server it executes.

Action

Set the default WS Transaction specification level to a value which is common to all servers in the cluster.

WTRN0130W: Unable to target module {0} on node {1} because the module specifies Resource Branch Coupling support which is not supported on the node

Explanation

The support for resource branch coupling is only available on nodes which are at release 8.0 or later.

Action

Install the module on an Application Server at release 8.0 (or later) or use the application"s deployment descriptor editor in the application development tooling to remove any Resource Branch Coupling settings before installing the module. This may be performed by navigating to the branch coupling section of the WebSphere Extensions and unseting the branch coupling for each transactional resource.

WTRN0131W: Unable to deploy application {0} on node {1} in cluster {2} because the application specifies Resource Branch Coupling support which is not supported on the node

Explanation

The support for resource branch coupling is only available on nodes which are at release 8.0 or later. The node will not be added to the cluster.

Action

Create cluster members on nodes which have an Application Server installed at release 8.0 (or later) or use the application"s deployment descriptor editor in the application development tooling to remove any Resource Branch Coupling settings before creating the cluster memeber. This may be performed by navigating to the branch coupling section of the WebSphere Extensions and unseting the branch coupling for each transactional resource.

WTRN0132I: Transaction recovery for {0} initiated with server uuid {1} and restart epoch {2}

Explanation

The transaction recovery process is starting for the server. The server uuid and epoch read from the existing transaction logs is reported. These values are used to identify any indoubt xids in xa resource managers which may have originated from previous instances of this server. If the transaction logs did not exist at server startup, the values of uuid and epoch output are those which will be written to the logs and used in future by the server.

Action

No user action is required.

WTRN0133I: Transaction recovery processing for this server is complete

Explanation

The transaction recovery process is complete for this server. All information of transactions and xa resource managers from previous instances of the server is removed from the logs.

Action

No user action is required.

WTRN0134I: Recovering {0} XA resource manager(s) from the transaction partner logs

Explanation

The transaction service has detected that the server may have terminated previously with in doubt transactions and the specified number of logged xa resource managers will be contacted as part of recovery processing.

Action

No user action is required.

WTRN0135I: Transaction service recovering no transactions.

Explanation

The transaction service has processed the transaction recovery logs and determined that there are no transactions that require recovery. Any indoubt xa resources originating from this server are rolled back.

Action

No user action is required.

WTRN0136I: Processing recovered transaction {0} (tid={1}) with {2}

Explanation

The transaction service is recovering the named transaction. The message also indicates the current status of the transaction during recovery. The tid value is used in other recovery processing messages and the administration console to refer to the transaction.

Action

No user action is required.

WTRN0137I: Recovered transaction (tid={0}) committing xid {1} with {2}

Explanation

The transaction service is recovering the named transaction and it is issuing a commit to a resource manager.

Action

No user action is required.

WTRN0138I: Recovered transaction (tid={0}) rolling back xid {1} with {2}

Explanation

The transaction service is recovering the named transaction and it is issuing a rollback to a resource manager.

Action

No user action is required.

WTRN0139I: Recovered transaction (tid={0}) forgetting xid {1} with {2}

Explanation

The transaction service is recovering the named transaction and it is issuing a forget to a resource manager.

Action

No user action is required.

WTRN0140I: Recovered transaction (tid={0}) committed xid {1} successfully with {2}

Explanation

The transaction service is recovering the named transaction and it has successfully committed a resource.

Action

No user action is required.

WTRN0141I: Recovered transaction (tid={0}) commit of xid {1} with {2} resulted in {3}

Explanation

The transaction service is recovering the named transaction and on committing a resource received the response code as given in the message.

Action

Examine the response code to determine if the commit failed and take appropriate action. If the code indicates an heuristic outcome, correct any data problems that may have occurred.

WTRN0142I: Recovered transaction (tid={0}) rolled back xid {1} successfully with {2}

Explanation

The transaction service is recovering the named transaction and it has successfully rolled back a resource.

Action

No user action is required.

WTRN0143I: Recovered transaction (tid={0}) rollback of xid {1} with {2} resulted in {3}

Explanation

The transaction service is recovering the named transaction and on rolling back a resource received the response code as given in the message.

Action

Examine the response code to determine if the rollback failed and take appropriate action. If the code indicates an heuristic outcome, correct any data problems that may have occurred.

WTRN0144I: Recovered transaction (tid={0}) forgot xid {1} successfully with {2}

Explanation

The transaction service is recovering the named transaction and it has successfully forgotten a resource.

Action

No user action is required.

WTRN0145I: Recovered transaction (tid={0}) forget of xid {1} with {2} resulted in {3}

Explanation

The transaction service is recovering the named transaction and on forgeting a resource received the response code as given in the message.

Action

Examine the response code to determine if the forget failed and take appropriate action.

WTRN0146I: Obtained {0} xid(s) from xa recover on {1} of which {2} will be processed by this server

Explanation

The transaction service successfully issued xa recover on a logged resource manager.

Action

No user action is required.

WTRN0147W: Recovered xid {0} from {1} is from a earlier restarted server instance with epoch {2}

Explanation

The transaction service successfully issued xa recover on a logged resource manager and obtained an xid which should have been recovered on the previous server restart. The epoch value indicates the server instance when the xid was originally associated with a transaction.

Action

Examine the epoch value from this message and compare it with the current server restart epoch in message WTRN0132. If intervening server restarts have been successful, check the logs from previous server instances together with the current logs to determine why this xid was not processed during recovery. For example, the resource manager may have been unavailable when the server was restarted previously.

WTRN0148I: Recovered xid {0} from {1} - xid has no associated transaction and will be rolled back

Explanation

The transaction service successfully issued xa recover on a logged resource manager and obtained an xid which does not corrrespond to a logged transaction. The transaction service will rollback the xid as part of recovery processing.

Action

No user action is required.

WTRN0149I: Recovered xid {0} from {1} - xid has associated transaction (tid={2}) with logged state {3}

Explanation

The transaction service successfully issued xa recover on a logged resource manager and obtained an xid which corrresponds to a logged transaction. The transaction service will complete the transaction as part of recovery processing.

Action

No user action is required.

WTRN0150I: Response from rolling back recovered xid {0} from {1} - {2}

Explanation

The transaction service successfully issued xa recover on a logged resource manager and obtained an xid which does not corrrespond to a logged transaction. The transaction service hass attempted to rollback the xid as part of recovery processing.

Action

Examine the error code to determine if the rollback failed.

WTRN0151I: Preparing to call xa recover on {0}

Explanation

The transaction service is preparing to call xa recover on a logged resource manager by opening a connection and obtaining an xa resource. If an xa resource is sucessfully obtained, another message will follow indicating the number of xids returned from xa recover. If a failure occurs obtaining a connection or xa resource, further messages will indicate the cause.

Action

If any messages following indicate a failure obtaining a connection or xa resource, determine the cause and take appropriate action.

WTRN0152W: Unusual HA configuration detected.

Explanation

HA is enabled for this cluster but the HA manager is disabled.

Action

If this is the desired configuration, no action is required. Otherwise, correct the HA configuration.

WTRN0153W: Resource {0} failed an xa_recover call test during enlistment. Exception: {1}

Explanation

The transaction service requested to enlist a resource. When called to recover, the resource gave an exception.

Action

Check the resource and its configuration. The error may be transient. Or, it may be that the resource is not suitable for use in a two phase transaction in its current configuration.

WTRN9001E: ENTRY COULD NOT BE ADDED TO XA RECOVERY TABLE, {0}

Explanation

OTS was attempting to add an XA resource to its internal
tables but failed. OTS will retry the add.

Action

If the problem persists, contact the IBM support
center.

WTRN9002W: RRS ({0}) AND XA ({1}) EPOCH NUMBERS DO NOT MATCH

Explanation

OTS maintains a counter in both the XA partner log and
its RRS logstream. If the counters are not the same, the logs
are not in sync and recovery may fail. This message indicates
that the logs are not in sync, but there is no recovery work to
do.

Action

Ensure both the RRS logstream and XA partner log
are present on the system, and have not been deleted. If the
problem persists, contact the IBM Support Center.

WTRN9003E: NO ENTRY FOUND IN XA RECOVERY TABLE FOR RECOVERY ID {0}

Explanation

OTS was attempting to convert a recovery ID to its
corresponding XA resource implementation. The recovery ID was not
found in the XA recovery table, and it therefore cannot be
recovered. If the recovery ID was being looked up during the
resolution of a restart RRS UR, the branch of the transaction
represented by the recovery ID may not have completed.

Action

The most common cause of this error is that the XA
partner log was deleted from the HFS. Ensure that the partner log
is present on the system and is readable by the Controller. If the
problem persists, contact the IBM Support Center.

WTRN9004E: TRANSACTION FACTORY IOR IS NULL

Explanation

OTS attempted to convert the TransactionFactory object
into an IOR so that it could be bound into the namespace. The
IOR returned from the conversion method was null. The
TransactionFactory will not be bound into the namespace.

Action

If no applications look up the TransactionFactory
object bound in the server_root at "TransactionFactory", then this
error can be ignored. If the problem persists, or if the object
is needed, contact the IBM Support Center.

WTRN9005E: TRANSACTION FACTORY COULD NOT BE INFLATED FROM IOR, {0}

Explanation

OTS attempted to attach the TransactionFactory IOR to
an object which is bound into the namespace. The IOR could not be
inflated, and the TransactionFactory will not be bound into the
namespace.

Action

WTRN9006E: TRANSACTION FACTORY COULD NOT BE BOUND INTO THE NAMESPACE, {0}

Explanation

OTS attempted to attach the TransactionFactory object
into the namespace, but recieved an exception when doing so.
The exception stack trace is provided in the message.

Action

WTRN9007I: RUNTIME CLASSPATH FOR SERVER {0} HAS CHANGED SINCE LAST RESTART

Explanation

The Transaction service logs the runtime class path each
time the server is restarted. This class path is used during
transactional recovery so that connections can be established with
XA resource managers. This message indicates that the current runtime
class path is different from the class path in the recovery log.

Action

None. The class path changes regularly when service is
applied, or when resource managers are installed at the cell, node, or
server level. However, if resource managers are removed from the system,
and transactional recovery needs to take place with those resource
managers, it may be necessary to leave these jar files or libraries
on the system until recovery has completed. If you are seeing error
messages relating to transactional recovery, this may be the cause. A
trace specification of OTS=event=enabled will display how the class path
has changed in the Controller address space.