WTRN0035_DURING_SERVER_QUIESCE_TX_ROLLBACK_FAILED=WTRN0035W: During server quiesce transaction {0} was found. The attempt to rollback the transaction failed. During the quiesce phase of server shutdown, an outstanding transaction was found. The transaction was not rolled back successfully. No action is required. This transaction will be recovered when the server is next started. WTRN0004_CANT_CREATE_XARESOURCEFACTORY=WTRN0004W: Unable to create XAResourceFactory. The XAResourceFactory class name was {0}. The exception stack trace follows: {1} During server recovery, the identified factory for creating XAResource objects could not be found. This is an internal system error. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0103_RECOVERY_LOG_FAILED=WTRN0103E: Recovery log is being marked as failed. [ {0} {1} ] 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. The server must be restarted so that the log can be repaired. Try to correct any conditions indicated by the exception in the message. WTRN0117_DEFAULT_AND_MINIMUM_LOG_SIZE=WTRN0117E: Invalid transaction log file size specified: {0}. The transaction service will use default log file size of 1M for WebSphere server ({1}). 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. Correct the Transaction log directory configuration. WTRN0066_LOG_WRITE_ERROR=WTRN0066W: Encountered exception during transaction logfile write operation. The exception stack trace follows: {0} An error occurred while writing to the transaction log file. The transaction will be rolled back. This is most likely to be an I/O failure. Examine the exception stack trace to determine the cause of the problem. WTRN0085_BAD_DISSOCIATE=WTRN0085E: No transaction found to dissociate from. This is an internal system error. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0116_UNEXPECTED_LOGFILE_SPECIFICATION=WTRN0116I: Invalid transaction log file configuration string specified: {0}. The transaction service will continue without recovery logging for WebSphere server ({1}). 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. Correct the Transaction log directory configuration. Ensure that the server is restarted to enable transaction recovery logging. WTRN0151_REC_XA_RECOVER=WTRN0151I: Preparing to call xa recover on {0} 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. If any messages following indicate a failure obtaining a connection or xa resource, determine the cause and take appropriate action. WTRN0019_LOGFILE_CORRUPTED=WTRN0019E: The transaction service log file {0} has become corrupted. The transaction service recovery log file has become corrupted and as a result server startup has failed. 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. WTRN0123_INVALID_EXTERNAL_WSTX_URL_PREFIX=WTRN0123E: An incorrect external WS-Transaction HTTP(S) URL prefix was specified: {0} The external WS-Transaction HTTP(S) URL prefix must be a valid URI. Specify a valid external WS-Transaction HTTP(S) URL prefix. WTRN0099_ROLLBACK_RA_UNINSTALLED=WTRN0099W: Outcome not available for transaction {0} as resource adapter {1} has been uninstalled. Transaction is heuristically rolled back. 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. Correct any application data problems that were caused by the heuristic outcome. WTRN0135_RECOVERING_NOTXNS=WTRN0135I: Transaction service recovering no transactions. 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. No user action is required. WTRN0022_UNKNOWN_XARESOURCE_STATE=WTRN0022W: Unknown XAResource state. An XAResource was in an unexpected state. This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0034_DURING_SERVER_QUIESCE_TX_ROLLBACK_SUCCEEDED=WTRN0034W: During server quiesce transaction {0} was found. The attempt to rollback the transaction succeeded. During the quiesce phase of server shutdown, an outstanding transaction was found. This transaction was rolled back successfully. No user action is required. WTRN0051_UNEXPECTED_XA_ERROR_ON_ROLLBACK=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}. The rollback call on a transactional resource did not succeed because of an unexpected failure. The rollback call will be retried at regular intervals. Examine the error code to determine the cause of the problem. WTRN0118_DEPRECATED_CUSTOM_PROPERTY=WTRN0118W: The deprecated transaction service customer property {0} was found in the transaction service configuration. 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. Remove the deprecated transaction service custom property from the configuration and use the corresponding general property setting, using the administrative console. WTRN0126_COMMIT_PRIORITY_CLUSTER=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 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. 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. WTRN0075_HEURISTIC_ON_COMMIT=WTRN0075W: Transaction {0} received a heuristic exception when committing a resource. The transaction service received a heuristic response when delivering a commit outcome to a transaction participant. Correct any application data problems that were caused by the heuristic outcome. WTRN0002_UNABLE_TO_FIND_RESOURCE_CLASS=WTRN0002W: The transaction service was unable to find resource class {0}. The transaction service could not find the XA resource class identified in the message. Ensure that the associated XA resource provider is configured and restart the server. The resource can then be unconfigured and the server shut down. WTRN0040_OBJECT_DESERIALIZE_FAILED=WTRN0040W: Object cannot be deserialized. The exception stack trace follows: {0} This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0139_REC_TXN_FORGET=WTRN0139I: Recovered transaction (tid={0}) forgetting xid {1} with {2} The transaction service is recovering the named transaction and it is issuing a forget to a resource manager. No user action is required. WTRN0149_REC_XA_TRAN=WTRN0149I: Recovered xid {0} from {1} - xid has associated transaction (tid={2}) with logged state {3} 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. No user action is required. WTRN0071_ROLLBACK_FAILED=WTRN0071E: Rollback failed with exception {0} An exception occurred while the transaction was rolling back. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0090_COMPLETED=WTRN0090I: {0}: Vote: {1}. Result: {2}. This message is for informational purposes only. System administrators can use this information to recover manually after transaction errors. WTRN0098_COMMIT_RA_UNINSTALLED=WTRN0098W: Outcome not available for transaction {0} as resource adapter {1} has been uninstalled. Transaction is heuristically committed. 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. Correct any application data problems that were caused by the heuristic outcome. WTRN0011_FACTORY_BIND_FAILURE=WTRN0011E: Unable to register transaction factory in JNDI namespace. An unexpected error occurred during initialization of the transaction service. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0102_HEURISTIC_MAY_HAVE_OCCURED=WTRN0102W: A heuristic condition may have occurred for transaction {0}. Transaction is heuristically rolled back. 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. 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 were caused by the heuristic outcome. WTRN0076_HEURISTIC_ON_ROLLBACK=WTRN0076W: Transaction {0} received a heuristic exception when rolling back a resource. The transaction service received a heuristic response when delivering a rollback outcome to a transaction participant. Correct any application data problems that were caused by the heuristic outcome. WTRN0020_RECOVERING_TRANSACTIONS=WTRN0020W: Recovering transactions for server {0} on this server. 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. Check whether any error messages are output during recovery and correct any actions requested. WTRN0067_PROG_MODEL_EXCEEDED=WTRN0067W: The transaction service has detected usage that exceeds the WebSphere Application programming model An application running in this server is using transaction service functionality that is not part of the application programming model. Consider whether the application can be modified to use only transaction functionality that is supported in the application programming model. WTRN0092_QUIESCE_UNFINISHED=WTRN0092W: Incomplete transaction (localid={0}) found during server quiesce; transaction service will wait. Inbound transactional work has not yet completed. The transaction service will delay server shutdown so that the originator can try to complete the transaction. No action is required. WTRN0060_RECOVERY_EXCEPTION_IN_FORGET=WTRN0060E: Exception caught from forget operation during recovery of transaction {0}: {1} An exception was detected while attempting to recover a transaction. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0025_TRAN_RECOVERY_FAILED=WTRN0025E: Recovery of Transaction failed {0} An exception occurred while attempting to recover a transaction. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0068_COMMIT_FAILED=WTRN0068E: Commit failed with exception {0} An exception occurred while the transaction was committing. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0078_START_FAILED=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} The transactional resource failed when being asked to process a start call. The transaction will be rolled back. Examine the error code to determine the cause of the problem. WTRN0142_REC_TXN_ROLLED=WTRN0142I: Recovered transaction (tid={0}) rolled back xid {1} successfully with {2} The transaction service is recovering the named transaction and it has successfully rolled back a resource. No user action is required. WTRN0052_XAER_RMFAIL_ON_COMMIT_ONE_PHASE=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} The one-phase commit call on a transactional resource did not succeed because the resource manager was unavailable. The transaction will be rolled back. WTRN0063_ILLEGAL_COMMIT_OF_1PC_RESOURCE=WTRN0063E: An illegal attempt to commit a one phase capable resource with existing two phase capable resources has occurred. 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. 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. WTRN0131_BRANCH_COUPLING_CLUSTER=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 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. 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. WTRN0089_PREPARED=WTRN0089I: {0}: Vote: {1}. This message is for informational purposes only. System administrators can use this information to recover manually after transaction errors. WTRN0086_PREPARE_DIAG=WTRN0086I: XAException encountered during prepare phase for transaction {0}. Local resources follow. This message is for informational purposes only. System administrators can use this information to recover manually after transaction errors. WTRN0130_BRANCH_COUPLING=WTRN0130W: Unable to target module {0} on node {1} because the module specifies Resource Branch Coupling support which is not supported on the node The support for resource branch coupling is only available on nodes which are at release 8.0 or later. 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. WTRN0119_UNAUTHORIZED_PROTOCOL_MSG_COUNT=WTRN0119W: Number of WS-TX protocol messages failing authorization: {0} 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. Ensure that the server is correctly configured for WS-AT and WS-BA in a secure environment. WTRN0106_JTADEMARCATION_DISALLOWED=WTRN0106I: Client JTA demarcation is disallowed. JTA demarcation has been configured as disallowed for this client application. To allow JTA demarcation, use the application server toolkit to set the Allow JTA Demarcation property in the client deployment descriptor. WTRN0045_CANNOT_RECOVER_RESOURCE=WTRN0045W: The transaction service cannot recover resource {0}. The exception stack trace follows: {1} 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0101_MANUAL_RA_UNINSTALLED=WTRN0101W: Outcome not available for transaction {0} as resource adapter {1} has been uninstalled. Transaction is awaiting administrator intervention to determine its outcome. The transaction service could not obtain the outcome of the transaction from the resource adapter because the resource adapter has been uninstalled. 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. WTRN0028_RECOVERING_TXNS=WTRN0028I: Transaction service recovering {0} transactions. 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. No user action is required. WTRN0150_REC_XA_ROLLEDBACK=WTRN0150I: Response from rolling back recovered xid {0} from {1} - {2} 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. Examine the error code to determine if the rollback failed. WTRN0039_SERIALIZE_FAILED=WTRN0039E: Unable to serialize an object to byte form. This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0120_INVALID_HA_LOGNAME=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). You must specify a valid transaction log directory path for each server in a cluster when the cluster is enabled for high availability. Change the setting of the transaction log file to a valid location in the file system. WTRN0024_INCONSISTENT_LOGS=WTRN0024E: Inconsistent Transaction and XA Resource recovery logs. This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0044_HEURISTIC_MAY_HAVE_OCCURED=WTRN0044W: A heuristic condition may have occurred for transaction {0} 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. 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. WTRN0114_TRAN_RETRY_NEEDED=WTRN0114I: Transaction {0} could not notify all resources of its outcome. Will retry in {1} seconds. A remote resource manager could not be contacted during recovery restart. The operation will be retried at regular intervals. Ensure that the resource manager is available. WTRN0053_UNEXPECTED_XA_ERROR_ON_COMMIT_ONE_PHASE=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}. The one-phase commit call on a transactional resource did not succeed because of an unexpected failure. The transaction manager will attempt to roll back the transaction. WTRN0047_XAER_RMERR_ON_COMMIT=WTRN0047W: An XAER_RMERR occured when committing the work on a transaction branch. The resource was: {0} A failure has been detected during the commit process for a transaction. Correct any application data problems that were caused by this failure. WTRN0038_ERR_DESTROYING_XARESOURCE=WTRN0038W: An exception occured when destroying an XA resource. The exception stack trace follows: {0} The transaction service could not destroy an XAResource. No action is required, because this should not affect the transaction service. WTRN0084_RESOURCE_ENDING=WTRN0084W: Enlist failed due to resource adapter terminating. A request to enlist a resource in a transaction was rejected because either the server, or the resource adapter, is being closed down. Rerun the transaction after the resource adapter becomes available. WTRN0050_UNEXPECTED_XA_ERROR_ON_COMMIT=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}. The commit call on a transactional resource did not succeed because of an unexpected failure. The commit call will be retried at regular intervals. Examine the error code to determine the cause of the problem. WTRN0093_COMMIT_REPLAY_COMPLETION=WTRN0093W: Outcome not available for subordinate transaction {0}. Transaction is heuristically committed. 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. Correct any application data problems that were caused by the heuristic outcome. WTRN0062_ILLEGAL_ENLIST_FOR_MULTIPLE_1PC_RESOURCES=WTRN0062E: An illegal attempt to use multiple resources that have only one-phase capability has occurred within a global transaction. 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. Modify the application either to use a single resource that is limited to one-phase capability, or to use two-phase capable XAResources. WTRN0001_ERR_INT_ERROR=WTRN0001E: An internal error occurred in method {0} in class {1}; This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0152_UNUSUAL_HA_CONFIG=WTRN0152W: Unusual HA configuration detected. HA is enabled for this cluster but the HA manager is disabled. If this is the desired configuration, no action is required. Otherwise, correct the HA configuration. WTRN0094_ROLLBACK_REPLAY_COMPLETION=WTRN0094W: Outcome not available for subordinate transaction {0}. Transaction is heuristically rolled back. 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. Correct any application data problems that were caused by the heuristic outcome. WTRN0134_RECOVERING_XARMS=WTRN0134I: Recovering {0} XA resource manager(s) from the transaction partner logs 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. No user action is required. WTRN0108_GENERIC_INFOMSG=WTRN0108I: {0} This message code is used to support messages that are not yet allocated their own message code. Refer to the message text for more information. WTRN0128_WSTX_APP_START_FAILURE=WTRN0128E: Unable to start application {0} because the application requires WS Transaction specifications which are not supported on all servers in the cluster. 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. 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. WTRN0138_REC_TXN_ROLLBACK=WTRN0138I: Recovered transaction (tid={0}) rolling back xid {1} with {2} The transaction service is recovering the named transaction and it is issuing a rollback to a resource manager. No user action is required. WTRN0029_ERROR_CLOSE_LOG_IN_SHUTDOWN=WTRN0029E: Error closing the log in shutdown! The transaction service encountered an error while closing its recovery log during server shutdown. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0127_BLOCKED_BY_POLICY_ASSERTION=WTRN0127E: Operation blocked by policy type configuration. The operation was blocked in accordance with the effective policy type configuration. Ensure the policy type configuration is appropriate for this operation. WTRN0000_ERR_INT_ERROR=WTRN0000E: An internal error occurred in method {0} in class {1}; the exception stack trace follows: {2}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0058_RECOVERY_EXCEPTION_IN_COMMIT=WTRN0058E: Exception caught from commit operation during recovery of transaction {0}: {1} An exception was detected while attempting to recover a transaction. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0073_FORGET_BAD_STATE=WTRN0073E: Forget received in bad transaction state {0} The transaction was not in a valid state when asked to carry out forget processing. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0124_TIMED_OUT_TRANSACTION_STACK=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} The stack, captured when the timeout occurred, is provided to help with diagnosis and debugging of transaction timeouts. Examine the stack trace to determine what processing was in progress when the transaction timeout occurred. WTRN0027_RECOVERING_TXN=WTRN0027I: Transaction service recovering 1 transaction. 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. No user action is required. WTRN0122_LOG_FREE_SPACE=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. 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. Consider setting a larger file size for the transaction logs. WTRN0143_REC_TXN_ROLLEDERR=WTRN0143I: Recovered transaction (tid={0}) rollback of xid {1} with {2} resulted in {3} The transaction service is recovering the named transaction and on rolling back a resource received the response code as given in the message. 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. WTRN0018_1PC_RESOURCE_DOES_NOT_SUPPORT_COMMIT=WTRN0018W: One-phase resource does not support commit 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0121_INVALID_HA_CONFIG=WTRN0121E: The high availability (HA) configuration is not valid. The server will stop. One or more servers in a cluster that is enabled for high availability do not have a valid transaction log directory defined. Examine accompanying messages for information about the affected servers. Correct the transaction log directories for these servers, then restart the cluster. WTRN0013_LOGGING_IN_MEMORY=WTRN0013W: No transaction log specified, logging in-memory 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. If you require transaction recovery, reconfigure the transaction service to use logging, and restart the server. WTRN0064_SUBORDINATE_COMMIT_OF_1PC_RESOURCE=WTRN0064E: An illegal attempt to commit a one phase capable resource in a subordinate transaction branch has occurred. 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. Ensure that one-phase capable resources are not involved in a subordinate branch of a distributed transaction. WTRN0041_TXN_ROLLED_BACK=WTRN0041I: Transaction {0} has been rolled back. 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. 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. WTRN0065_XARESOURCE_NOT_KNOWN=WTRN0065W: XAResource is not known to this transaction. The resource was: {0} 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0140_REC_TXN_COMMITED=WTRN0140I: Recovered transaction (tid={0}) committed xid {1} successfully with {2} The transaction service is recovering the named transaction and it has successfully committed a resource. No user action is required. WTRN0112_LOG_OPEN_FAILURE=WTRN0112E: An unexpected error occured whilst opening the recovery log. The log configuration was {0} 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. Examine any related messages to determine the cause of the problem. WTRN0088_EXCEPTION_DIAG=WTRN0088I: {0} encountered XAException with error code {1}. This message is for informational purposes only. System administrators can use this information to recover manually after transaction errors. WTRN0129_WSTX_APP_START_FAILURE=WTRN0129W: The default setting for WS Transaction specification level is inappropriate for a mixed version cluster 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. Set the default WS Transaction specification level to a value which is common to all servers in the cluster. WTRN0003_RECOVERY_TXRECUTILS_LOAD_FAILED=WTRN0003E: During recovery a required JAR file could not be found. The path use to locate it was {0}. During recovery involving an embedded RAR file, a required JAR file could not be found. Without this JAR file, transaction recovery cannot be completed. None. This is an internal system error. WTRN0077_OPERATOR_CANCELLED=WTRN0077W: Transaction {0} was cancelled by the operator. The outcome delivery for the transaction identified in the message was abandoned at the request of the operator. Correct any application data problems that were caused by this failure. WTRN0095_MANUAL_REPLAY_COMPLETION=WTRN0095W: Outcome not available for subordinate transaction {0}. Transaction is awaiting administrator intervention to determine its outcome. 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. 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. WTRN0030_XARESOURCE_RECOVER_FAILURE=WTRN0030E: Recovery of XAResource data failed {0} This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0087_COMPLETION_DIAG=WTRN0087I: XAException encountered during completion phase for transaction {0}. Local resources follow. This message is for informational purposes only. System administrators can use this information to recover manually after transaction errors. WTRN0146_REC_XA_RECOVERED=WTRN0146I: Obtained {0} xid(s) from xa recover on {1} of which {2} will be processed by this server The transaction service successfully issued xa recover on a logged resource manager. No user action is required. WTRN0008_CANT_IMPORT_NESTED_TRAN=WTRN0008W: Transaction service unable to import nested transaction {0} A remote server attempted to import a nested transaction. This action is not supported. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0033_TRANSACTION_FACTORY_CREATE=WTRN0033E: Transaction factory create caught exception {0} This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0048_XAER_RMFAIL_ON_COMMIT=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} 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. Ensure that the resource manager is available. WTRN0137_REC_TXN_COMMIT=WTRN0137I: Recovered transaction (tid={0}) committing xid {1} with {2} The transaction service is recovering the named transaction and it is issuing a commit to a resource manager. No user action is required. WTRN0145_REC_TXN_FORGETERR=WTRN0145I: Recovered transaction (tid={0}) forget of xid {1} with {2} resulted in {3} The transaction service is recovering the named transaction and on forgeting a resource received the response code as given in the message. Examine the response code to determine if the forget failed and take appropriate action. WTRN0081_NULL_JTSXARESOURCE=WTRN0081W: The JTAXAResource object is null. This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0049_XAER_RMFAIL_ON_ROLLBACK=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} 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. Ensure that the resource manager is available. WTRN0082_OPERATOR_ROLLBACK=WTRN0082W: Transaction {0} was rolled back by the operator. The transaction identified in the message was rolled back by operator request. Correct any application data problems that were caused by this failure. WTRN0031_XA_ROLLBACK_FAILED=WTRN0031E: An xa_rollback operation on a transactional resource failed. The global transaction was {0}. The exception stack trace follows: {1} 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. 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. WTRN0032_IMPLEMENTATION_SPECIFIC_ON_INBOUND=WTRN0032E: Implementation specific transaction context received on inbound request. This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0070_ONE_PHASE_COMMIT_FAILED=WTRN0070E: One-phase commit failed with exception {0} An exception occurred while the transaction was committing using the one-phase commit protocol. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0147_REC_XID_LATE=WTRN0147W: Recovered xid {0} from {1} is from a earlier restarted server instance with epoch {2} 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. 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. WTRN0014_UNEXPECTED_LOGFILE_SPECIFICATION=WTRN0014I: The transaction service detected an invalid log file configuration string. The transaction service will continue without recovery logging. 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. Correct the Transaction log directory configuration. Ensure that the server is restarted to enable transaction recovery logging. WTRN0061_ERR_CREATING_JTAXARESOURCE=WTRN0061E: Encountered an error while building a JTAXAResource object This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0091_ASSOCIATE_FAILED=WTRN0091E: Failed to associate Execution Context. Xid: {0}, timeout {1}. This is an internal system error. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0056_TRAN_RESYNC_FAILURE=WTRN0056I: Transaction {0} resynchronization from originator failed, retrying.... A transaction has failed to resynchronize during recovery, and the outcome is unknown, so the server will continue to retry. No action is required. WTRN0006_TRANSACTION_HAS_TIMED_OUT=WTRN0006W: Transaction {0} has timed out after {1} seconds. The transaction service has timed out (rolled back) the transaction identified in the message. To reduce future timeout occurrences, increase the transaction timeout values. WTRN0115_NO_CFW_AVAILABLE=WTRN0115E: Channel Framework configuration is not defined or is invalid for WebServices Atomic Transactions (WSAT) support. 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. Correct or define the channel framework configuration for the Web container. WTRN0107_GENERIC_WARNING=WTRN0107W: {0} This message code is used to support messages that are not yet allocated their own message code. Refer to the message text for more information. WTRN0015_DEFAULT_AND_MINIMUM_LOG_SIZE=WTRN0015E: Invalid transaction log file size specified: {0}. The transaction service will use default log file size of 1M. 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. Correct the Transaction log directory configuration. WTRN0100_GENERIC_ERROR=WTRN0100E: {0} This message code is used to support messages that have not yet been allocated their own message code. Refer to the message text for more information. WTRN0023_INVALID_XAEND_FLAG=WTRN0023W: Invalid XA end flag: {0} This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0037_XA_RECOVER_ERROR=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} 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. Examine the error code to determine the cause of the problem. WTRN0105_CLEAN_SHUTDOWN=WTRN0105I: The transaction service has shutdown successfully with no transactions requiring recovery. This is a normal event. This message is for informational purposes only. No action is required. WTRN0043_LOCAL_TRAN_ROLLBACK=WTRN0043I: LocalTransaction rolled-back due to setRollbackOnly. A local transaction has been rolled back because the setRollbackOnly method has been called. No action is required. WTRN0026_KEYPOINT_EXC_IN_RECOVERY=WTRN0026E: Exception caught during keypoint after recovery! {0} This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0055_GIVING_UP_OUTCOME_DELIVERY=WTRN0055W: Giving up on outcome delivery for transaction {0}. The transaction service could not deliver a commit or rollback outcome to a transaction participant. Correct any application data problems that were caused by this failure. WTRN0125_COMMIT_PRIORITY=WTRN0125W: Unable to target module {0} on node {1} because the module specifies Resource Commit Ordering support which is not supported on the node The support for resource commit ordering is only available on nodes which are at release 7.0 or later. 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. WTRN0017_UNABLE_TO_BEGIN_NESTED_TRANSACTION=WTRN0017W: Unable to begin a nested transaction. Nested transactions are not supported. This error indicates an attempt to begin a nested transaction, but nested transactions are not supported. Ensure that there is not an attempt to begin a transaction when another transaction is already active on the thread. WTRN0080_CLIENT_INACTIVITY_TIMEOUT=WTRN0080W: Transaction {0} has timed out due to no client activity for greater than {1} seconds. The client has been inactive for longer than the inactivity timeout value. 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. WTRN0148_REC_XA_ROLLBACK=WTRN0148I: Recovered xid {0} from {1} - xid has no associated transaction and will be rolled back 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. No user action is required. WTRN0097_HEURISTIC_MANUAL_COMPLETION=WTRN0097W: Unknown transaction outcome occurred for transaction {0}. Transaction is awaiting administrator intervention to determine its outcome. 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. 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. WTRN0133_RECOVERY_COMPLETE=WTRN0133I: Transaction recovery processing for this server is complete 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. No user action is required. WTRN0110_BAD_CUSTOM_PROPERTY=WTRN0110W: {0} is not a valid transaction service custom property A custom property that was specified in the transaction service configuration for this server is not valid and has been ignored. Correct the transaction service custom properties configuration. WTRN0113_LOG_DOWNLEVEL=WTRN0113W: Recovery processing of a downlevel peer WebSphere server is not possible and has been halted ({0}) 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. 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. WTRN0054_XA_FORGET_ERROR=WTRN0054W: An xa_forget operation on a transactional resource encountered an exception. The error code was {0}. The exception stack trace follows: {1} An exception occurred when the transaction service called the xa_forget operation on a resource. Examine the error code to determine the cause of the problem. WTRN0007_CANT_IMPORT_NULL_CONTEXT=WTRN0007W: Transaction service unable to import transaction with null or invalid context. 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0141_REC_TXN_COMMITERR=WTRN0141I: Recovered transaction (tid={0}) commit of xid {1} with {2} resulted in {3} The transaction service is recovering the named transaction and on committing a resource received the response code as given in the message. 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. WTRN0104_RECOVERY_LOG_FAILED_DETAIL=WTRN0104E: Details of recovery log failure: {0} This message is issued with message WTRN0103E to indicate the details of the recovery log failure. Use the information in this message along with message WTRN0103E to correct the condition that caused the recovery log to fail. WTRN0079_END_FAILED=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} The transactional resource failed when being asked to process an end call. The transaction will be rolled back. Examine the error code to determine the cause of the problem. WTRN0059_RECOVERY_EXCEPTION_IN_ROLLBACK=WTRN0059E: Exception caught from rollback operation during recovery of transaction {0}: {1} An exception was detected while attempting to recover a transaction. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0046_PREPARE_FAILED=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} The transactional resource failed when being asked to process a prepare call. The failure will be treated as a rollback vote. Examine the error code to determine the cause of the problem. WTRN0069_COMMIT_BAD_STATE=WTRN0069E: Commit received in bad transaction state {0} The transaction was not in a valid state when it was asked to carry out commit processing. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0009_NO_GLOBAL_TID_ON_IMPORT=WTRN0009E: No globalTID for coordinator resource. No global transaction id was supplied in the imported transaction context. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0136_RECOVERING_TRAN=WTRN0136I: Processing recovered transaction {0} (tid={1}) with {2} 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. No user action is required. WTRN0005_CANT_RECREATE_XARESOURCE=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} During server recovery, an XAResource object could not be recreated by its corresponding factory. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0111_LOG_ALLOCATION=WTRN0111E: Unable to access or create the recovery log. The log configuration was {0} 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. 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. WTRN0042_GLOBAL_TRAN_ROLLBACK=WTRN0042I: GlobalTransaction rolled-back due to timeout or setRollbackOnly. A global transaction has been rolled back because either it has reached a timeout value, or the setRollbackOnly method has been called. If the timeout value is too short or long, use the Administrative console to modify it. WTRN0144_REC_TXN_FORGOT=WTRN0144I: Recovered transaction (tid={0}) forgot xid {1} successfully with {2} The transaction service is recovering the named transaction and it has successfully forgotten a resource. No user action is required. WTRN0132_RECOVERY_INITIATED=WTRN0132I: Transaction recovery for {0} initiated with server uuid {1} and restart epoch {2} 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. No user action is required. WTRN0016_EXC_DURING_RECOVERY=WTRN0016E: Exception caught during transaction service recovery! {0} An exception was detected while the transaction service was attempting to recover from a previous server failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0109_MBEAN_ACTIVATE=WTRN0109W: Exception encountered when activating Transaction JMX MBean: {0} 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0036_DURING_SERVER_QUIESCE_TX_MARKED_ROLLBACK_ONLY=WTRN0036W: During server quiesce transaction {0} was found. The transaction has been marked rollback only. During the quiesce phase of server shutdown, an outstanding transaction was found. This transaction was marked rollback only. No action is required. The transaction will be rolled back during server shutdown, or will be recovered when the server is restarted. WTRN0074_SYNCHRONIZATION_EXCEPTION=WTRN0074E: Exception caught from {0} synchronization operation: {1} An exception was created by a Synchronization object when it was informed of the current completion state of the transaction. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0021_TMRESUME_NOT_SUPPORTED=WTRN0021W: TMRESUME is not supported. This is an internal system error and is probably caused by an earlier failure. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0096_HEURISTIC_MAY_HAVE_OCCURED=WTRN0096W: A heuristic condition may have occurred for transaction {0}. Transaction is heuristically committed. 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. 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. WTRN0072_ROLLBACK_BAD_STATE=WTRN0072E: Rollback received in bad transaction state {0} The transaction was not in a valid state when asked to carry out rollback processing. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0057_HEURISTIC_ON_SUBORDINATE=WTRN0057E: Heuristic raised on prepare/commit_one_phase on subordinate. A subordinate transaction attempted to optimize using one-phase commit during prepare, and a heuristic error occurred. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0012_UNEXP_FACTORY_REG_FAILURE=WTRN0012E: Unexpected failure during transaction factory registration. An unexpected error occurred during initialization of the transaction service. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WTRN0083_LOG_FULL_ERROR=WTRN0083W: The transaction log is full. Transaction {0} rolled back. 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. If this problem occurs frequently, restart the server with a larger file size for the transaction log. WTRN0010_EXC_AT_COORD_REG=WTRN0010E: Transaction rolledback due to exception on registering coordinator with superior {0} There was a problem when a remote transaction was imported into the server, so the transaction was rolled back. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .