Notes on Product Behavior

Using the XAResource.prepare call causes a global transaction to enter a prepared state, which allows it to be persistent. Typically, the prepared state is just a transitional state before the transaction outcome is determined. However, if the system crashes, recovery puts transactions in the prepared state back into that state and awaits instructions from the transaction manager.

If a user opens an XAConnection with a user name and password, the transaction it created cannot be attached to an XAConnection opened with a different user name and password. A transaction created with an XAConnection without a user name and password can be attached to any XAConnection.

However, the user name and password for recovered global transactions are lost; any XAConnection can commit or roll back that in-doubt transaction.

Note:

Derby's XADataSources can only be embedded. No remote (client/server) support is provided.