Explanation | A global transaction in which the CORBA Object Transaction Service was involved has exceeded its maximum processing time. The transaction was marked for rollback only. Any further method dispatches in this transaction will cause a CORBA::TRANSACTION_ROLLEDBACK exception. |
Action | Examine the application for a possible coding error. The application might explicitly set the transaction timeout value to a value less than or equal to the value of the transaction_maximumTimeout environment variable. If a timeout was not explicitly set, it defaults to the value in the transaction_defaultTimeout environment variable. |
Explanation | The resource recovery service indicated in the message failed and that service completed with the indicated hexadecimal return code. |
Action | See return codes for resource recovery services in the MVS Programming: Resource Recovery book for additional information. |
Explanation | One or more resource managers involved in the global transaction whose ID is identified in the message were assigned an outcome that was different from the outcome of the global transaction. For example, if the outcome of the transaction was commit, some resources that were involved in the transaction have been rolled back. |
Action | This message shows the transaction identifier for which the heuristic outcome occurred. Use the ATRFPCMN dialog facility to review the resource recovery services (RRS) transaction logs and determine which resources are inconsistent. Follow the procedures for that particular resource manager to restore or correct the state of those resources. |
Explanation | One or more resource managers involved in the global transaction whose ID is identified in the message might be assigned an outcome that was different from the outcome of the global transaction. |
Action | This message shows the transaction identifier for which the heuristic outcome might have occurred. Use the ATRFPCMN dialog facility to review the resource recovery services (RRS) transaction logs and determine whether any resources are inconsistent. Follow the procedures for that particular resource manager to restore or correct the state of those resources. Also, if this condition occurs when transactional optimizations are used, RRS might not be aware of the transactional outcome, because commit responsibilities are delegated to the single resource manager. In this situation, the outcome of the single resource manager is unknown and a hazard condition exists. To determine the outcome, follow documented procedures for the resource manager identified in the message to determine the outcome or to correct any resources involved in the global transaction shown in this message. |
Explanation | The transaction services component has initiated transaction restart and recovery with the resource recovery services (RRS). |
Action | No action is required. |
Explanation | The transaction services component has received restart units of recovery from the resource recovery services (RRS). The counts indicate the number of units of work that had states when the server was stopped previously such that some recovery action is required 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 that they modified 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 that resources that they modified do not become available 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 | No action is required. |
Explanation | The transaction services restart process has completed. All units of recovery have been resolved. |
Action | No action is required. |
Explanation | During the resource recovery services (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 | No action is required. |
Explanation | During the resource recovery services (RRS) log name exchange process, RRS indicated that a log name was previously set. When restart is initiated, some incomplete RRS units of recovery might be returned. |
Action | No action is required. |
Explanation | The transaction services restart process has completed. All units of recovery have been resolved. |
Action | No action is required. |
Explanation | The transaction service restart processing for the unit of recovery identifier (URID) shown in the message has completed. |
Action | No action is required. |
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 show the progress of the transaction recovery process. |
Action | No action is required. |
Explanation | While in restart and recovery mode, the application server could not contact the recovery coordinator for the transaction branch with the XID provided. The host name and port were obtained from the Interoperable Object Reference (IOR) for the recovery coordinator. If the IOR points to a WebSphere/390 object, the server name is also written. |
Action | Ensure that the server and host can be reached by this application server. If connectivity cannot be restored, you can use the transaction information in this message to resolve the outcome of the transaction manually with the resource recovery services (RRS) ISPF panels or the ATRSRV macro. Note that resolving the transaction manually can result in mixed transaction outcomes across resource managers and servers. |
Explanation | While in restart and recovery mode, the application server could not contact the recovery coordinator for the transaction branch with the XID provided. Because the outcome could not be determined, this server could not provide a transaction resolution to the resources registered with the transaction coordinator on this server for the transaction branch with the XID information in this message. |
Action | No action is required. |
Explanation | While in restart and recovery mode, the application server could not successfully commit or roll back the resource involved in the transaction branch described by the XID information in this message. The outcome of the transaction has been determined, but it cannot be completed until all subordinate OTS resources have been told the outcome. |
Action | Ensure that the server and host can be reached by this application server. If connectivity cannot be restored, you can use the transaction information in this message to resolve the outcome of the transaction for the subordinate nodes manually. The CORBA Object Transaction Service (OTS) interests in the resource recovery services (RRS) unit of recovery with the unit of recovery identifier (URID) shown can be removed with the RRS ISPF panels or the ATRSRV macro. |
Explanation | While in restart and recovery mode, the application server was not told to forget an heuristic outcome for a transaction it was involved in. A transaction that is not forgotten is not complete, because the resource recovery services (RRS) unit of recovery (UR) with the unit of recovery identifier (URID) shown is still active. |
Action | Ensure that the server and host in this message can successfully connect to this server. If connectivity cannot be restored, or the superior does not know of the heuristic outcome, you can use the RRS ISPF panels or ATRSRV macro to remove the CORBA Object Transaction Service (OTS) interests in the UR with the URID shown. |
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 show the progress of the transaction recovery process. Because 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 | No action is required. |
Explanation | Transactional recovery for this server is being performed on a peer server using the high availability (HA) recovery framework. This server must wait for the HA recovery process to stop before it can take over the transactional logs for this server. |
Action | No action is required. The peer server has been notified that it must stop recovery. |
Explanation | The transaction service's recovery processing has not completed within the configured amount of retries. The transaction's outcome has been heuristically set to commit according to the setting of "Heuristic completion direction" in the transaction service configuration. |
Action | No action is required. |
Explanation | The transaction service's recovery processing has not completed within the configured amount of retries. The transaction's outcome has been heuristically set to rollback according to the setting of "Heuristic completion direction" in the transaction service configuration. |
Action | No action is required. |
Explanation | The transaction service's recovery processing has not completed within the configured amount of retries. The transaction's outcome has been heuristically set to manual according to the setting of "Heuristic completion direction" in the transaction service configuration. |
Action | Access the RRS panels to view and resolve any pending transactions. */ |
Explanation | The transaction services recovery processing was stopped 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 that is attempting perform recovery on the same failed server. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: 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/ . |
Explanation | The transaction services recovery processing will be stopped because the 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 | No action is required. |
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 might have changed after the transaction was started. In this situation, update the security policy on the remote server to temporarily allow this transaction to complete. The operation will retry automatically. |