[
https://issues.apache.org/jira/browse/DERBY-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881039#comment-17881039
]
Richard N. Hillegas commented on DERBY-7169:
--------------------------------------------
A good place to start is the following wiki page about analyzing and fixing
deadlocks: https://cwiki.apache.org/confluence/display/DERBY/LockDebugging I
recommend that you read the Derby Developer's Guide's extensive section on
locks, deadlocks, and concurrency:
https://db.apache.org/derby/docs/10.17/devguide/cdevconcepts30291.html
> Deadlocks can occur when creating tables and querying indexes in multiple
> threads
> ---------------------------------------------------------------------------------
>
> Key: DERBY-7169
> URL: https://issues.apache.org/jira/browse/DERBY-7169
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.14.1.0
> Reporter: Richard Evans
> Priority: Major
> Attachments: dmdlock.java
>
>
> In multiple threads, create tables and also query meta data using
> getIndexInfo. After a number of successful table creates the test hangs and
> fails with
> ERROR 40XL1: A lock could not be obtained within the time requested
> If run with -Dderby.locks.waitTimeout=-1 the test hangs indefinitely.
> Test case attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
