Lots of Orphaned XA transactions exist when using Microsoft SQL Server with IBM Business Process Manager (BPM)
There is a link from Microsoft wich recommends the following:
https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/in-doubt-xact-resolution-server-configuration-option?view=sql-server-2017
Use the in-doubt xact resolution option to control the default outcome of transactions that the Microsoft Distributed Transaction Coordinator (MS DTC) is unable to resolve. Inability to resolve transactions may be related to the MS DTC down time or an unknown transaction outcome at the time of recovery.
The following table lists the possible outcome values for resolving an in-doubt transaction.
| Outcome value |
Description |
| 0 |
No presumption. Recovery fails if MS DTC cannot resolve any in-doubt transactions. |
| 1 |
Presume commit. Any MS DTC in-doubt transactions are presumed to have committed. |
| 2 |
Presume abort. Any MS DTC in-doubt transactions are presumed to have aborted. |
My question is which value should I use. I would say 2, what do you think?!
Another question I have is why do we have so much orphaned transactions in Database and how to avoid them?!
------------------------------
Joao Alexandre
Lisboa
------------------------------