Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 7 Oct 2011 16:37:30 +0000 (UTC)
From: "Mike Matrigali (Commented) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2117668424.8635.1318005450493.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <867695890.3805.1317915929835.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5448) In the 10.8 branch, back out the
 concurrency improvements introduced by using SequenceUpdaters to allocate
 identity values.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mike Matrigali commented on DERBY-5448:
---------------------------------------

rick, those are the switches I was think of.  It looks like lock output has changed since I last debugged these kinds of problems, I will look at code and see if anything else is possible.  

You don't mention how long it takes for you to repro.  Since you seem to have the hardware/jvm combination that repro's could you run a test against the existing 10.8 apache release (not the RC but the actual release), just to verify this is a regression in 10.8.  I believe these kinds of 
issues are very timing dependent and hardware/JVM can affect the runs greatly.  

Also anyone running nstest on top branch can you mention if you are seeing any of the other issues that we were hoping were going to be fixed
by backing out 5448 (like DERBY-5422 and DERBY-5428 and maybe others).
                
> 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