xadisk
  1. xadisk
  2. XADISK-156

Response of XAResourceImpl in case of self-initiated rollbacks by XADisk.

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 1.2.2
    • Fix Version/s: None
    • Component/s: connector
    • Labels:
      None

      Description

      Thanks to Alex for bringing this to my attention at thread:

      https://groups.google.com/forum/#!topic/xadisk/SWxa1o03ccw

      There are some cases when XADisk rolls back its transactions by itself, even in case of a distributed transaction (which is co-ordinated by the transaction-manager[TM]), eg transaction timeout, deadlock detection.

      As the TM, being unaware of these rollbacks, would still call, as in general, methods like end, prepare, commit, rollback etc, the XADisk should choose the right mechanism to signal the early self-initiated rollback to the TM. There is an error code of XA_RB* (in XAException), can XADisk employ these error codes?

        Activity

        Nitin Verma created issue -
        Nitin Verma made changes -
        Field Original Value New Value
        Description Thanks to Alex for bringing this to my attention at thread:

        https://groups.google.com/forum/#!topic/xadisk/SWxa1o03ccw

        There are some cases when XADisk rolls back its transactions by itself, even in case of a distributed transaction (which is co-ordinated by the transaction-manager[TM]), eg transaction timeout, deadlock detection.

        As the TM, being unaware of these rollbacks, would call, as in general, methods like end, prepare, commit, rollback etc, the XADisk should choose the right mechanism to signal the early self-initiated rollback to the TM. There is an error code of XA_RB* (in XAException), can XADisk employ these error codes?
        Thanks to Alex for bringing this to my attention at thread:

        https://groups.google.com/forum/#!topic/xadisk/SWxa1o03ccw

        There are some cases when XADisk rolls back its transactions by itself, even in case of a distributed transaction (which is co-ordinated by the transaction-manager[TM]), eg transaction timeout, deadlock detection.

        As the TM, being unaware of these rollbacks, would still call, as in general, methods like end, prepare, commit, rollback etc, the XADisk should choose the right mechanism to signal the early self-initiated rollback to the TM. There is an error code of XA_RB* (in XAException), can XADisk employ these error codes?
        Nitin Verma made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Won't Fix [ 2 ]

          People

          • Assignee:
            Nitin Verma
            Reporter:
            Nitin Verma
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: