Explanation | Reply to a previous message was not valid. The previous message is reissued. |
Action | Issue a valid reply to the reissued message. |
Explanation | A global transaction in which OTS was involved has exceeded its maximum processing time. The transaction wasmarked for rollback only. Any further method dispatches in this transaction will cause a CORBA::TRANSACTION_ROLLEDBACK exception to be thrown. |
Action | Examine the application for a possible coding error. The transaction timeout value may have been explicitly set by the application to any value less than or equal to the value of the transaction_maximumTimeout environment variable. If a timeout was not explicitly set, it will default to the value in the transaction_defaultTimeout environment variable. |
Explanation | WebSphere Application Server for z/OS failed in the resource recovery service indicated and that service completed with a hexadecimal return code indicated. |
Action | See return codes for resource recovery services in the MVS Programming: Resource Recovery book for additional information. |
Explanation | This message is issued after a UR goes in-Doubt with RRS. It is only issued after this debug aid has been explicitly enabled with a modify command |
Action | This is an internal programming error. For further information on resolving this error, please consult the IBM WebSphere Application Server for z/OS Support website at: http://www-3.ibm.com/software/webservers/appserv/zos_os390/support.html. This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Explanation | WebSphere Application Server for z/OS has detected that one or more resource managers involved in the global transaction, whose ID is displayed in the message, has indicated that some resources were assigned an outcome that was different than the overall outcome of the global transaction. For example, if the overall outcome of the transaction was commit, some of the resources that were involved in the transaction have been rolled back. |
Action | This message contains the transaction identifier for which the heuristic condition occurred. Review the RRS transaction logs via the ATRFPCMN dialog facility provided by zOS, to determine which resources are inconsistent, and follow the procedures for that particular resource manager to restore or correct the state of those resources. |
Explanation | WebSphere Application Server for z/OS has detected that one or more resource managers involved in the global transaction, whose ID is displayed in the message, may have assigned an outcome that was different than the overall outcome of the global transaction. |
Action | This message contains the transaction identifier for which the heuristic condition may have occurred. Review the RRS transaction logs via the ATRFPCMN dialog facility provided by zOS, to determine if any resources are inconsistent, and follow the procedures for that particular resource manager to restore or correct the state of those resources. In addition, because this condition may have occurred when transactional optimizations were used, RRS may be unaware of the transactional outcome, because of a delegation of commit responsibilites to the single resource manager. In this case, the outcome of the single resource manager is unknown and a hazard condition exists. To determine the outcome, follow documented procedures for the given resource manager to determine the outcome or to correct any resources involved in the global transaction as displayed in this message. |
Explanation | The transaction services component has initiated transaction restart and recovery with RRS. |
Action | None. |
Explanation | The transaction services component has received restart units of recovery from RRS. The counts indicate the number of units of work with states at a previous server termination such that some recovery action must be performed during this restart. The IN-BACKOUT count specifies the number that were in the process of backing out. These must undergo recovery to restore resources modified by them to their previous consistent state. The IN-DOUBT count specifies the number that were interrupted between phase 1 and phase 2 of the commit process. These must undergo recovery to ensure resources modified by them are unavailable until their indoubt status is resolved. The IN-COMMIT count specifies the number that had started but not completed phase 2 of the commit process. These must undergo recovery to complete the commit process. |
Action | None. |
Explanation | The transaction services restart process has completed. All units of recovery have been resolved. |
Action | None. |
Explanation | During the RRS log name exchange process, RRS indicated that no previous log name was set. When restart is initiated, no incomplete RRS units of recovery will be returned. |
Action | None. |
Explanation | During the RRS log name exchange process, RRS indicated that a log name was previouly set. When restart is initiated, some incomplete RRS units of recovery may be returned. |
Action | None. |
Explanation | The transaction services restart process has completed. All units of recovery have been resolved. |
Action | None. |
Explanation | The transaction service restart processing for the given URID has completed. |
Action | None. |
Explanation | The transaction service restart processing for the server running in restart and recovery mode was unable to resolve all incomplete transactions in the configured amount of time. This is generally due to a communications failure with a another server that was involved in the transaction. It is possible that unresolved transactions will prevent a successful restart with RRS on the server's configured system. |
Action | If the server should continue its attempts to resolve incomplete transactions for the duration specified by the transaction_recoveryTimeout environment variable, reply 'CONTINUE.' If the server should not continue its attempts to resolve incomplete transactions, a reply of 'TERMINATE' will stop the server. Information about the unresolved transactions can be found in the server's job output. This information can be used to resolve transactions using the RRS panels. |
Explanation | The transaction services restart processing has not completed within the configured time. The operator has indicated (by reply) that the server should no longer attempt recovery. Some units of recovery have not been completed and forgotten. |
Action | None. |
Explanation | The transaction services restart processing has not completed within the configured time. The operator has indicated (by reply) that the server should continue to attempt transaction completion for an additional duration time specified by the transaction_recoveryTimeout environment variable. |
Action | None. |
Explanation | The transaction services restart processing is still trying to resolve some incomplete restart units of recovery in restart and recovery mode. This message is issued at regular intervals to update the installation on the progress of the transaction recovery process. |
Action | None. |
Explanation | WebSphere Application Server for z/OS detected that RRS was not available. WebSphere requires RRS to be active and will not proceed with its initialization until RRS is available. |
Action | Start RRS. Once RRS has started, WebSphere Application Server for z/OS will continue with its initialization. |
Explanation | WebSphere Application Server for z/OS was notified that RRS is no longer available on this system and has terminated processing. RRS and WebSphere must be restarted before new work will be accepted. |
Action | WebSphere must be restarted on the system where RRS became unavailable. |
Explanation | WebSphere Application Server for z/OS has recovery work to do, but the versions of the RRS log and XA partner log do not match. In order for recovery to complete successfully, both of these logs must be in sync. It is possible that one or both of these logs were deleted, or restored to a previous state that is not consistent. The RRS log is stored as a logstream defined at installation time. The XA partner log is defined through the admin console. It is also possible that the controler failed to initialize on the previous restart, which would not allow the XA partner log to sync up with the RRS logstream. |
Action | If the log data mismatch is expected, reply CONTINUE to the WTOR. If the mismatch is unexpected, reply CANCEL to terminate the controller and determine the cause of the mismatch. Note that by replying CONTINUE, recovery will complete but there is a chance that some resources will be left in an inconsistent state. |
Explanation | The transaction services restart processing is still trying to resolve some incomplete restart units of recovery in restart and recovery mode. This message is issued at regular intervals to update the installation on the progress of the transaction recovery process. Since each XA resource manager maintains its own logs, it is impossible to tell how many units of recovery need to be resolved until each resource manager is contacted. |
Action | None. |
Explanation | Transactional recovery for this server is currently executing on a peer server using the HA recovery framework. This server must wait for the HA recovery process to terminate before it can take over the transactional logs for this server. |
Action | None. The peer server has been notified that it must terminate recovery. |
Explanation | The transaction services recovery processing has not completed within the configured amount of retries. The operator has indicated (by reply) that recovery process should continue to attempt transaction completion for an additional amount of times specified by the transaction_heuristicRetryLimit environment variable. |
Action | None. |
Explanation | The transaction services recovery processing has been terminated because the operator has indicated (by reply) that recovery process should stop. Some Units of Recovery have not been completed. |
Action | None |
Explanation | The transaction services recovery processing was terminated because recovery for the failed server is already taking place on another server. The transaction service could not obtain the resources needed because they are being held by another server attempting perform recovery on the same failed server. |
Action | This is an internal programming error. For further information on resolving this error, please contact the WebSphere Support team. |
Explanation | The transaction services recovery processing will be terminated because server for which recovery is taking place has been restarted. If recovery was not completed on the peer server, it will continue during server restart. |
Action | None |
Explanation | The transaction service attempted to drive a transactional object residing on the server, host and port specified in the message. The security credentials supplied on the call were rejected by the remote server. |
Action | The security policy of the remote server may have changed since the transaction was started. If this is the case, update the security policy on the remote server temporarily to allow this transaction to complete. The operation will retry automatically. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The transaction service was unable to find the given XA resource class. |
Action | Ensure that the associated XA resource provider is configured and restart the server. The resource can then be unconfigured and the server shutdown. |
Explanation | During recovery involving an embedded RAR 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. |
Explanation | This failure indicates that during server recovery, the given factory for creating XAResource objects could not be found. This is an internal system error. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | This failure indicates that during server recovery an XAResource object could not be recreated by its corresponding factory. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The transaction service has timed out (rolled back) the given transaction. |
Action | To reduce future timeout occurrences, increase the transaction timeout values. |
Explanation | A context was imported into the server with invalid or no transaction data so a transaction could not be initiated. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Importing of a nested transaction was attempted by a remote server. This is not supported. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | No global transaction id was supplied in the imported transaction context. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | A problem occurred importing a remote transaction into the server so the transaction was rolled back. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An unexpected error occurred during transaction service initialization. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An unexpected error occurred during transaction service initialization. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The transaction service is configured not to log to permanent storage. This may cause data integrity problems or locked resources (for example, database tables) if there are outstanding 2 phase commit transactions running when the server is terminated. |
Action | If transaction recovery is required, then reconfigure the Transaction Service to use logging and restart the server. |
Explanation | The transaction service log file configuration string specified in systems management is invalid. The format should be a fully qualified log file directory optionally followed a ';' and the log file size. The log file size should be followed by either 'M' or 'K' to indicate megabytes or kilobytes respectively. The default and minimum log file size is 1M. |
Action | Correct the transaction service log file configuration. Ensure that the server is restarted to enable transaction recovery logging. |
Explanation | The transaction service log file configuration string specified in systems management is invalid. The format should be a fully qualified log file directory optionally followed a ';' and the log file size. The log file size should be followed by either 'M' or 'K' to indicate megabytes or kilobytes respectively. The default and minimum log file size is 1M. |
Action | Correct the transaction service log file configuration. |
Explanation | An exception was caught whilst the transaction service was attempting to recover from a previous server failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | This error indicates an attempt to begin a nested transaction, but nested transactions are not supported. |
Action | Ensure that no attempt is made to begin a transaction when another transaction is already active on the thread of execution. |
Explanation | A resource that only supports one-phase optimized commit has been enlisted with the transaction service and called to process a standard two phase commit operation. This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
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. It will be necessary to manually complete any transactions that were pending in associated resource managers. |
Explanation | The transaction logs for server {0} are being recovered by this server. If resources configured on this server do not match those configured for the server for which the logs were created, then recovery may fail to complete. |
Action | Check if any error messages are output during recovery and correct any actions requested. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An XAResource was in an unexpected state. This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An exception occurred whilst attempting to recover a transaction. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
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 so that it can be committed. Any transactions that were rolled back are not counted. |
Action | No user action is required. |
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 so that they can be committed. Any transactions that were rolled back are not counted. |
Action | No user action is required. |
Explanation | The transaction service encountered an error whilst closing its recovery log during server shutdown. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An exception occured when the transaction service called the xa_rollback operation on a resource enlisted with the given global transaction. |
Action | This exception may indicate that a heuristic has occured. If this is the case, correct all application data problems that were caused by the heuristic decision. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | During the quiesce phase of server shutdown an outstanding transaction was found. This transaction was rolledback successfully. |
Action | No user action is required. |
Explanation | During the quiesce phase of server shutdown an outstanding transaction was found. The transaction was not rolledback successfully. |
Action | No user action is required. This transaction will be recovered when the server is next started. |
Explanation | During the quiesce phase of server shutdown an outstanding transaction was found. This transaction was marked rollback only. |
Action | No user action is required. The transaction will be rolledback during server shutdown or will be recovered upon server restart. |
Explanation | The transaction service encountered an error when calling xa_recover on a resource, in order to determine the prepared transactions held by the corresponding resource manager. The operation will be retried. |
Action | Examine the error code in order to determine the cause of the failure. |
Explanation | The transaction service was unable to destroy an XAResource. |
Action | No action is required as this should not affect the running of the transaction service. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Transaction {0} was previously marked rollbackOnly and has now been rolled back. This may be due to a transaction timeout or an application decision to mark the transaction rollbackOnly. |
Action | No user action is required unless the rollback is undesirable and occurs as a result of a transaction timeout. If this is the case, investigate why the transaction takes longer to complete than the timeout period and consider increasing the duration of the transaction timeout values for the server. |
Explanation | A Global transaction has been rolled-back due to a pre-defined timeout value being reached or setRollbackOnly being called. |
Action | If the timeout value is too short/long modify using the Admin Console. |
Explanation | A Local transaction has been rolled-back due to setRollbackOnly being called. |
Action | No user action is required. |
Explanation | The transaction service has detected that the specified transaction involved mixed one phase and two phase capable resources. The transaction service passed a one phase commit request to the single one phase capable resource, but the server failed before the commit could complete. It is not known if the resource committed successfully. |
Action | All two phase capable resources will be rolled back. If the one phase capable resource successfully processed commit, then heuristic damage has occurred and all application data problems that were caused by the heuristic must be corrected. |
Explanation | An internal system error occured when the transaction service attempted to reconstruct a transaction participant during recovery. This is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
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. |
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. |
Explanation | The commit call on a transactional resource did not succeed as the resource manager was unavailable. The commit call will be retried at regular intervals. |
Action | Ensure that the resource manager is available. |
Explanation | The rollback call on a transactional resource did not succeed as the resource manager was unavailable. |
Action | The rollback call will be retried at regular intervals. Ensure that the resource manager is available. |
Explanation | The commit call on a transactional resource did not succeed due to an unexpected failure. |
Action | The commit call will be retried at regular intervals. Examine the error code in order to determine the cause of the problem. |
Explanation | The rollback call on a transactional resource did not succeed due to an unexpected failure. |
Action | The rollback call will be retried at regular intervals. Examine the error code in order to determine the cause of the problem. |
Explanation | The one phase commit call on a transactional resource did not succeed as the resource manager was unavailable. |
Action | The transaction will be rolled back. |
Explanation | The one phase commit call on a transactional resource did not succeed due to an unexpected failure. |
Action | The transaction manager will attempt to rollback the transaction. |
Explanation | An exception occured when the transaction service called the xa_forget operation on a resource. |
Action | Examine the error code to determine what caused this error. |
Explanation | The transaction service was unable to deliver a commit or rollback outcome to a transaction participant. |
Action | Correct any application data problems that were caused by this failure. |
Explanation | A transaction has failed to resync during recovery and the outcome is unknown so the server will continue to retry. |
Action | No user action is required. |
Explanation | A subordinate transaction attempted to optimize using one-phase commit during prepare and a heuristic error occurred. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An exception was caught while attempting to recover a transaction. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An exception was caught while attempting to recover a transaction. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An exception was caught while attempting to recover a transaction. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Only a single resource that is limited to one-phase capability may be enlisted in a global transaction. This error occurs if muliple resource managers that are only one-phase capable are used within a global transaction or if multiple unshared connections from a single such resource manager are used within a global transaction. |
Action | Modify the application to use only a single resource that is limited to one-phase capability or else use two-phase capable XAResources. |
Explanation | The transaction service has refused an attempt to commit a one phase capable resource with a transaction already involving other two phase capable resources. Either Last Participant Support (LPS) is not available, or if LPS is available, the application does not accept the heuristic risk that this would involve. |
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. |
Explanation | The transaction service has refused an attempt to commit a one phase capable resource within a distributed subordinate transaction branch. The transaction will be rolled back. |
Action | Ensure that one phase capable resources are not involved in a subordinate branch of a distributed transaction. |
Explanation | The transaction manager was unable to delist an XAResource because it had not been previously enlisted with the current transaction. This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An error occured writing to the transaction log file. The transaction will be rolled back. |
Action | This is most likely to be an IO failure. Examine the exception stack trace to determine the cause of the problem. |
Explanation | An application running in this server is using transaction service functionality that is not part of the WebSphere application programming model. |
Action | Consider whether the application can be modified to only utilize the J2EE transaction functionality. |
Explanation | An exception occurred whilst the transaction was committing. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The transaction was in an invalid state when asked to carry out commit processing. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An exception occurred whilst the transaction was committing using the one-phase commit protocol. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An exception occurred whilst the transaction was rolling-back. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The transaction was in an invalid state when asked to carry out rollback processing. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The transaction was in an invalid state when asked to carry out forget processing. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | An exception was thrown by a Synchronization object when it was informed of the transactions current completion state. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
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 this failure. |
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 this failure. |
Explanation | The outcome delivery for the given transaction was abandonned at operator request. |
Action | Correct any application data problems that were caused by this failure. |
Explanation | The transactional resource failed when being asked to process a start call. The failure will cause the transaction to be rolled back. |
Action | Examine the error code to determine the cause of the problem. |
Explanation | The transactional resource failed when being asked to process an end call. The failure will cause the transaction to be rolled back. |
Action | Examine the error code to determine the cause of the problem. |
Explanation | The client has been inactive longer than inactivity timeout value of {1} seconds. |
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. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | The given transaction was rolled back by operator request. |
Action | Correct any application data problems that were caused by this failure. |
Explanation | The transaction log files are full with records from active transactions. Any further two phase commit transactions will be rolled back until space is freed up in the log files when active transactions complete. |
Action | If this problem occurs frequently, restart the server with a larger transaction log file size specification. |
Explanation | A request to enlist a resource within a transaction has been rejected as either the server or the resource adapter is being closed down. |
Action | Rerun the transaction once the resource adapter is available, |
Explanation | Internal system error. |
Action | This is an internal error which should be reported to IBM. |
Explanation | Informational. |
Action | Used by system administrators to manually recover after transaction errors. |
Explanation | Informational. |
Action | Used by system administrators to manually recover after transaction errors. |
Explanation | Informational. |
Action | Used by system administrators to manually recover after transaction errors. |
Explanation | Informational. |
Action | Used by system administrators to manually recover after transaction errors. |
Explanation | Informational. |
Action | Used by system administrators to manually recover after transaction errors. |
Explanation | Internal system error. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support. |
Explanation | Inbound transactional work has not yet completed. The transaction service will delay server shutdown to allow the originator the chance to complete the transaction. |
Action | No action is necessary. |
Explanation | The transaction service was unable to obtain the outcome of the transaction from its superior within the configured retry period. The transaction will be heuristically committed. |
Action | Correct any application data problems that were caused by this failure. |
Explanation | The transaction service was unable to obtain the outcome of the transaction from its superior within the configured retry period. The transaction will be heuristically rolled back. |
Action | Correct any application data problems that were caused by this failure. |
Explanation | The transaction service was unable to obtain the outcome of the transaction from its superior within the configured retry period. The transaction is now waiting for administrator to manually set the transaction outcome. |
Action | The system administrator should manually set the transaction outcome after determining the success or failure of the superior transaction. This ensures that heuristic damage does not occur and that all application data remains correct. |
Explanation | The transaction service has detected that the specified transaction involved mixed one phase and two phase capable resources. The transaction service passed a one phase commit request to the single one phase capable resource, but the server failed before the commit could complete. It is not known if the resource committed successfully. |
Action | All two phase capable resources will be committed. If the one phase capable resource failed to process commit, then heuristic damage has occurred and all application data problems that were caused by the heuristic must be corrected. |
Explanation | The transaction service has detected that the specified transaction involved mixed one phase and two phase capable resources. The transaction service passed a one phase commit request to the single one phase capable resource, but the server failed before the commit could complete. It is not known if the resource committed successfully. |
Action | The system administrator should manually set the transaction outcome after determining the success or failure of the one phase commit request. This ensures that heuristic damage does not occur and that all application data remains correct. |
Explanation | The transaction service was unable to obtain the outcome of the transaction from the resource adapter as it has been uninstalled. The transaction will be heuristically committed. |
Action | Correct any application data problems that were caused by this failure. |
Explanation | The transaction service was unable to obtain the outcome of the transaction from the resource adapter as it has been uninstalled. The transaction will be heuristically rolled back. |
Action | Correct any application data problems that were caused by this failure. |
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. |
Explanation | The transaction service was unable to obtain the outcome of the transaction from the resource adapter as it has been uninstalled. |
Action | The system administrator should manually set the transaction outcome after determining the success or failure from the originator of the resource adapter transaction. This ensures that heuristic damage does not occur and that all application data remains correct. |
Explanation | The transaction service has detected that the specified transaction involved mixed one phase and two phase capable resources. The transaction service passed a one phase commit request to the single one phase capable resource, but the server failed before the commit could complete. It is not known if the resource committed successfully. |
Action | All two phase capable resources will be rolled back. If the one phase capable resource successfully processed commit, then heuristic damage has occurred and all application data problems that were caused by the heuristic must be corrected. |
Explanation | The recovery log has failed, and not further access to the recovery log can occur. The component is indicated in the message along with the exception taken. |
Action | The server must be restarted so that the log can be repaired. Attempt to fix any conditions indicated by the exception in the message. If the problem persists, please contact IBM Support. |
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 whatever condition caused the recovery log to fail. |
Explanation | This is a normal event and the message is for information only. |
Action | No action is required by the user. |
Explanation | JTA demarcation has been configured to be disallowed for this client application. |
Action | To allow JTA demarcation, use the assembly toolkit to set the Allow JTA Demarcation property in the client deployment descriptor. |
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. |
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. |
Explanation | An error occured when attempting to activate a JMX MBean for the transaction service. Although this does not prevent the transaction service from starting, it does mean that any administrative functions which require access to the transaction service will fail. |
Action | If this continues to occur, contact IBM Support. |
Explanation | An invalid custom property was specified in the transaction service configuration for this server and has been ignored. |
Action | Correct the transaction service custom properties configuration. |
Explanation | The transaction service was unable to access or create recovery logs. If the recovery logs are for the local server, then the server will be terminated. If the recovery logs are for a peer recovered server then recovery will be terminated and assigned to another server, and the reporting server will continue normally. |
Action | Examine any related messages in order to determine the cause of the problem. Ensure 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 the server has correct access permissions to the files or directories specified in the messages. |
Explanation | The transaction service was unable to open the recovery logs. If the recovery logs are for the local server, then the server will be terminated. If the recovery logs are for a peer recovered server then recovery will be terminated and assigned to another server, and the reporting server will continue normally. |
Action | Examine any related messages in order to determine the cause of the problem. |
Explanation | The transaction service was unable to peer recover the specified WebSphere server because the logs were formatted by an earlier release of WebSphere Application Server which is incompatible with this server. This instance of peer recovery will be terminated 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, then peer recovery for that server release may not be possible if the log format has become incompatible across releases. Contact IBM Support to determine if there are any migration options available to overcome this problem. |
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. |
Explanation | The Web Container is not defined to use the channel framework, or is defined incorrectly. WSAT requires the use of channel framework to transfer transactional context between WebServices. |
Action | Correct or define the channel framework configuration for the Web Container. |
Explanation | The transaction service log file configuration string specified in systems management is invalid. The format should be a fully qualified log file directory optionally followed a ';' and the log file size. The log file size should be followed by either 'M' or 'K' to indicate megabytes or kilobytes respectively. The default and minimum log file size is 1M. |
Action | Correct the transaction service log file configuration. Ensure that the server is restarted to enable transaction recovery logging. |
Explanation | The transaction service log file configuration string specified in systems management is invalid. The format should be a fully qualified log file directory optionally followed a ';' and the log file size. The log file size should be followed by either 'M' or 'K' to indicate megabytes or kilobytes respectively. The default and minimum log file size is 1M. |
Action | Correct the transaction service log file 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 WebSphere Application Server. |
Action | Remove the deprecated transaction service custom property from the configuration and use the corresponding general property setting via the admin console. |
Explanation | The log file is nearly full because of the transactional workload. If the log file becomes full, the server must be restarted. |
Action | Consider setting a larger file size for the transaction logs. |