Troubleshooting
Problem
This technote describes how XA recovery is performed in WebSphere Application Server when the optional XA recovery authentication alias is used.
Resolving The Problem
During the processing of a transaction all unique XA connections to data sources and default messaging provider connection factories enlisted in a transaction will be recorded in the transaction log including the userid/password used to access the resource and the optional XA recovery userid/password. A connection is considered unique if a userid/password combination used to access a resource has not been used before in the current transaction.
When a WebSphere Application Server JVM ends in an ungraceful fashion and there are prepared transactions that have not yet been committed, these transactions will be rolled back using the information contained in the tranlog before the next WebSphere Application Server JVM startup completes or when the transaction log service is failed over to another JVM.
If the optional XA recovery alias has been provided, the XA recovery userid/password is recorded in the tranlogs when the resource was enlisted in the original transaction and that XA recovery authentication alias will be used for recovery instead of the original userid/password that was passed. If the optional XA-recovery alias has not been provided the original userid/password used to access the resource, whether from a component managed authentication alias or from the application, will be used for recovery.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21260425