Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <524214963.1247468954863.JavaMail.jira@brutus>
Date: Mon, 13 Jul 2009 00:09:14 -0700 (PDT)
From: "Egidijus (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-4302) Deadlock on system tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Deadlock on system tables
-------------------------

                 Key: DERBY-4302
                 URL: https://issues.apache.org/jira/browse/DERBY-4302
             Project: Derby
          Issue Type: Bug
          Components: Store
            Reporter: Egidijus


Using 3d part libraries which uses embedded Derby DB, I got following stack trace which shows that deadlock appears between *system* tables (unfortunately there are no code to reproduce). Connecting without auto commit and DB is used by two users: 

Lock : TABLE, SYSCOLUMNS, Tablelock
  Waiting XID : {9404, IS} , APP, SELECT cdo_version, cdo_created,
cdo_revised, cdo_resource, cdo_container, cdo_feature, name, id FROM
core_File WHERE cdo_id= ? AND (cdo_revised = 0 )
  Granted XID : {7351, IX}
Lock : ROW, SYSTABLES, (2,14)
  Waiting XID : {7351, X} , APP, CREATE TABLE core_File (cdo_id BIGINT
NOT NULL, cdo_version INTEGER NOT NULL, cdo_class BIGINT NOT NULL,
cdo_created BIGINT NOT NULL, cdo_revised BIGINT NOT NULL, cdo_resource
BIGINT NOT NULL, cdo_container BIGINT NOT NULL, cdo_feature INTEGER
NOT NULL, name VARCHAR(32672), id VARCHAR(32672))
  Granted XID : {9404, S}
. The selected victim is XID : 9404. 


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.