[ 
https://issues.apache.org/jira/browse/DERBY-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124401#comment-13124401
 ] 

Rick Hillegas commented on DERBY-5448:
--------------------------------------

I agree that there are two different deadlocks:

1) A deadlock involving locks on a user table and seen with the "select 
max(serialkey)" query.

2) A deadlock involving locks on a SYSCOLUMNS row and seen with the "insert 
into nstesttab" statement.

(1) may be a bug in NsTest and I agree that it deserves its own JIRA.. Note 
that I have seen both deadlocks on the 10.8 branch after backing out the 
DERBY-4437 work. (2) is still a problem in the 10.8 branch. I have no problem 
with closing this issue as long as DERBY-5430 remains open. Thanks.
                
> In the 10.8 branch, back out the concurrency improvements introduced by using 
> SequenceUpdaters to allocate identity values.
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5448
>                 URL: https://issues.apache.org/jira/browse/DERBY-5448
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation, SQL
>    Affects Versions: 10.8.2.1
>            Reporter: Rick Hillegas
>             Fix For: 10.8.2.1
>
>         Attachments: derby-5448-01-aa-backoutConcurrencyChanges.diff, 
> derby-5448-02-aa-backoutDocsChanges.diff
>
>
> New errors were seen while running NsTest against the 10.8.2 release 
> candidates. These errors are recorded as DERBY-5430 and DERBY-5422. The first 
> error is a deadlock which occurs when inserting into the main table of the 
> test. The second error is a problem clearing the identity cache. These errors 
> have caused people to lose confidence in the concurrency improvements 
> introduced by DERBY-4437. We should back the DERBY-4437 changes out of the 
> 10.8 branch and use the trunk to continue debugging the problems disclosed by 
> NsTest.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to