Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Date: Tue, 5 Apr 2011 21:07:06 +0000 (UTC)
From: "Albert Lee (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Message-ID: 
 <215463529.35954.1302037626255.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2016586544.25563.1301602025913.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (OPENJPA-1972) DB2 V9.7 changed the default
 behavior concerning blocking behavior with isolation levels greater then
 read uncommitted
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Albert Lee resolved OPENJPA-1972.
---------------------------------

    Resolution: Fixed

> DB2 V9.7 changed the default behavior concerning blocking behavior with isolation levels greater then read uncommitted
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1972
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1972
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 2.0.2, 2.1.0, 2.2.0
>            Reporter: Albert Lee
>            Assignee: Albert Lee
>            Priority: Minor
>             Fix For: 2.1.1, 2.2.0
>
>
> This is an intentional change in DB2 9.7.  Refer to articles:
> http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.wn.doc/doc/c0053503.html
> http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.perf.doc/doc/c0053760.html
> http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.config.doc/doc/r0053556.html
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira