Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-366

In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.0.2.1
    • 10.1.1.0, 10.2.1.6
    • JDBC
    • None

    Description

      A connection in local transaction has a default holdability of HOLD_CURSORS_OVER_COMMIT. When this connection becomes part of a global transaction, Derby internally switches its holdability to CLOSE_CURSORS_AT_COMMIT (this is because in Derby, holdable cursors do not work with XA transactions). When this connection returns back to local transaction, its holdability should automatically get switched to HOLD_CURSORS_OVER_COMMIT. When running under jdk13, Derby does not perform the last step of restoring the connection holdability. I have attached a program to reporduce this behavior. If this program is run under jdk14, the holdability is restored as expected.

      Attachments

        1. Derby8_Derby366_061805.txt
          33 kB
          Mamta A. Satoor
        2. mamta.java
          7 kB
          Mamta A. Satoor

        Activity

          People

            mamtas Mamta A. Satoor
            mamtas Mamta A. Satoor
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: