1. OpenJPA
  2. OPENJPA-1972

DB2 V9.7 changed the default behavior concerning blocking behavior with isolation levels greater then read uncommitted


    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.2, 2.1.0, 2.2.0
    • Fix Version/s: 2.1.1, 2.2.0
    • Component/s: sql
    • Labels:


      This is an intentional change in DB2 9.7. Refer to articles:

      DB2 9.7 added a cur_commit database configuration setting. By default, for new databases, cur_commit is "ON", which is described as follows in the 2nd article above:

      "Under the new currently committed semantics, only committed data is returned, as was the case previously, but now readers do not wait for writers to release row locks. Instead, readers return data that is based on the currently committed version; that is, data prior to the start of the write operation."

      This change affected the expected outcome of a deadlock test, which need to enhance adapting to this behavior change.


        Albert Lee created issue -
        Albert Lee made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Albert Lee made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Albert Lee made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        5d 59m 1 Albert Lee 05/Apr/11 22:06
        In Progress In Progress Resolved Resolved
        13s 1 Albert Lee 05/Apr/11 22:06
        Resolved Resolved Closed Closed
        7s 1 Albert Lee 05/Apr/11 22:06


          • Assignee:
            Albert Lee
            Albert Lee
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: