[DERBY-4302] Deadlock on system tables

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.1.2.1
• Component/s: SQL
• Labels: derby_triage10_5_2
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Egidijus
• Created: 13/Jul/09 07:07
• Updated: 15/Feb/11 21:08

Description

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.