Derby
  1. Derby
  2. DERBY-2432

Unimplemented transaction time out for XA transactions may cause that locks will not be released when client terminates outside a unit of work.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.3.1.4
    • Component/s: JDBC
    • Labels:
      None
    • Urgency:
      Normal

      Description

      The XAResource interface provides function setTransactionTimeout which is currently not supported in derby.

      When client application uses client driver to connect to derby database and the application crashes outside the unit of work of XA transaction and the transaction is not committed or rolled back yet the locks held by the transaction will not be released.

      1. description.txt
        3 kB
        Julius Stroffek
      2. d2432.diff
        38 kB
        Julius Stroffek
      3. d2432.stat
        0.9 kB
        Julius Stroffek
      4. d2432_v2.diff
        40 kB
        Julius Stroffek
      5. d2432_v2.stat
        0.9 kB
        Julius Stroffek
      6. d2432_v3.diff
        40 kB
        Julius Stroffek
      7. d2432_v3.stat
        0.9 kB
        Julius Stroffek
      8. d2432_v4.diff
        41 kB
        Julius Stroffek
      9. d2432_v4.stat
        0.9 kB
        Julius Stroffek
      10. d2432_v5.diff
        41 kB
        Julius Stroffek
      11. d2432_v5.stat
        0.9 kB
        Julius Stroffek

        Issue Links

        There are no Sub-Tasks for this issue.

          Activity

            People

            • Assignee:
              Julius Stroffek
              Reporter:
              Julius Stroffek
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development