From dev-return-18849-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Mar 31 20:07:48 2011 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 57323 invoked from network); 31 Mar 2011 20:07:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Mar 2011 20:07:46 -0000 Received: (qmail 17186 invoked by uid 500); 31 Mar 2011 20:07:45 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 17143 invoked by uid 500); 31 Mar 2011 20:07:45 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 17135 invoked by uid 99); 31 Mar 2011 20:07:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Mar 2011 20:07:45 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Mar 2011 20:07:43 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id DFC2A8C97F for ; Thu, 31 Mar 2011 20:07:05 +0000 (UTC) Date: Thu, 31 Mar 2011 20:07:05 +0000 (UTC) From: "Albert Lee (JIRA)" To: dev@openjpa.apache.org Message-ID: <2016586544.25563.1301602025913.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org 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.1.0, 2.0.2, 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