Use these tips to help you troubleshoot problems with the WebSphere® Application Server transaction service.
For messaging problems specific to WebSphere Application Server nodes, see other topics in the information center, such as the topic about messaging troubleshooting tips, and the WebSphere Application Server Support web page.
[10/26/04 8:41:38:887 CDT] 00000029 CoordinationL A CWWTR0100_GENERIC_ERROR [10/26/04 8:41:39:100 CDT] 00000029 RecoveryHandl A CWWTR0100E: An attempt to acquire a file lock needed to perform recovery processing failed. Either the target server is active or the recovery log configuration is incorrect .... [10/26/04 8:42:34:921 CDT] 00000027 HAGroupImpl I CWRHA0130I: The local member of group GN_PS=fwsitkaCell01\fwwsaix1Node01\GriffinServer3, IBM_hc=GriffinCluster,type =WAS_TRANSACTIONS has indicated that is it not alive. The JVM will be terminated. [10/26/04 8:42:34:927 CDT] 00000027 SystemOut O Panic:component requested panic from isAlive
If an application server fails, and the end transaction record is not forced to disk immediately, you might or might not recover a transaction.
[date time] 00000057 WSRdbXaResour E CWWRA0302E: XAException occurred. Error code is: XAER_NOTA (-4). Exception is: XAER_NOTA
If there is a transaction without an end record left in the transaction log, the transaction service tries to check with the database. If the transaction has completed, the database indicates that there is nothing to complete (XAER_NOTA). This behavior is normal, and is not an error.
When an application server shuts down, any active transactions are rolled back. If all transactions complete successfully, message CWWTR0105I is logged, indicating a clean shutdown of the transaction service, and the next server restart does not need any recovery activity. If an application server shuts down and message CWWTR0105I is not logged, this message does not indicate a problem, but it does mean that recovery activity is required when the server restarts.
Before you uninstall the product, you should have a clean shutdown of all application servers so that you avoid data integrity problems.