[
https://issues.apache.org/jira/browse/DERBY-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4302:
--------------------------------------
Component/s: (was: Store)
SQL
Urgency: Normal (was: Urgent)
> Deadlock on system tables
> -------------------------
>
> Key: DERBY-4302
> URL: https://issues.apache.org/jira/browse/DERBY-4302
> Project: Derby
> Issue Type: Bug
> Components: SQL
> 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.
