From derby-user-return-13593-apmail-db-derby-user-archive=db.apache.org@db.apache.org Fri May 13 23:50:20 2011 Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7FF6B4636 for ; Fri, 13 May 2011 23:50:20 +0000 (UTC) Received: (qmail 68842 invoked by uid 500); 13 May 2011 23:50:20 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 68813 invoked by uid 500); 13 May 2011 23:50:20 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 68806 invoked by uid 99); 13 May 2011 23:50:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 23:50:20 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [32.97.182.142] (HELO e2.ny.us.ibm.com) (32.97.182.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 23:50:09 +0000 Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by e2.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p4DNTwBw004349 for ; Fri, 13 May 2011 19:29:58 -0400 Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p4DNnjB41306814 for ; Fri, 13 May 2011 19:49:45 -0400 Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p4DNnjZF024903 for ; Fri, 13 May 2011 20:49:45 -0300 Received: from [127.0.0.1] (sig-9-48-97-43.mts.ibm.com [9.48.97.43]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p4DNngmu024827; Fri, 13 May 2011 20:49:44 -0300 Message-ID: <4DCDC39A.2000509@sbcglobal.net> Date: Fri, 13 May 2011 16:49:46 -0700 From: Kathey Marsden User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Derby Discussion CC: "Dag H. Wanvik" Subject: Re: Deadlock issue References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------080207080403020704060808" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------080207080403020704060808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 5/13/2011 3:46 PM, Dag H. Wanvik wrote: > Hi, > > In general, this resource may help you understand how Derby uses locks: > > http://db.apache.org/derby/docs/10.8/devguide/cdevconcepts30291.html > > and specifically how to debug deadlocks: > > http://db.apache.org/derby/docs/10.8/devguide/cdevconcepts50894.html > http://wiki.apache.org/db-derby/LockDebugging > > If you feel you understand how Derby takes locks but are seeing Derby > take locks that you feel are not appropriate for your usage and > isolation level, please let us know. If you can provide a lock table > dump, that would be helpful. Please state version of Derby are you > using, too. > If you are using the new 10.8.1.2 release, setting derby.stream.error.extendedDiagSeverityLevel=30000 // will print the stack traces of all active threads on deadlock to derby.log, which can help debug both application and possible Derby issues with Deadlocks. http://db.apache.org/derby/docs/10.8/ref/rrefproperextdiagsevlevel.html --------------080207080403020704060808 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 5/13/2011 3:46 PM, Dag H. Wanvik wrote:
Hi,

In general, this resource may help you understand how Derby uses locks:

http://db.apache.org/derby/docs/10.8/devguide/cdevconcepts30291.html

and specifically how to debug deadlocks:

http://db.apache.org/derby/docs/10.8/devguide/cdevconcepts50894.html
http://wiki.apache.org/db-derby/LockDebugging

If you feel you understand how Derby takes locks but are seeing Derby
take locks that you feel are not appropriate for your usage and
isolation level, please let us know. If you can provide a lock table
dump, that would be helpful. Please state version of Derby are you
using, too.

If you are using the new 10.8.1.2 release, setting derby.stream.error.extendedDiagSeverityLevel=30000
will print the stack traces of all active threads on deadlock to derby.log, which can help debug both application and possible Derby  issues with Deadlocks.

http://db.apache.org/derby/docs/10.8/ref/rrefproperextdiagsevlevel.html


--------------080207080403020704060808--