db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5494) Same value returned by successive calls to a sequence generator flanking an unorderly shutdown.
Date Thu, 12 Apr 2012 01:14:21 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-5494:
----------------------------------

    Attachment: derby-5494_diff_1a.txt

patch not ready for commit. First step of proposed fix, this change causes all user level
nested write transactions to flush commit log record.  Next step is to isolate the flushing
to just sequences as I don't understand the performance ramifications of other usages in SQL
layer of the nested write transaction.  Seems to fix ij repro in this JIRA, going to run tests
over night to see if it has any obvious problems.  needs some comments also.

                
> Same value returned by successive calls to a sequence generator flanking an unorderly
shutdown.
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5494
>                 URL: https://issues.apache.org/jira/browse/DERBY-5494
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2, 10.9.0.0
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_9
>         Attachments: derby-5494_diff_1a.txt
>
>
> The following sequence of steps causes a sequence generator to return the same value
on successive NEXT VALUE FOR calls.
> 1) Bring up ij and issue the following commands:
> connect 'jdbc:derby:db;create=true';
> create sequence s;
> values next value for s; 
> 2) Control-c out of ij so that the engine comes down hard without an orderly shutdown.
> 3) Now bring up ij again and issue the following commands:
> connect 'jdbc:derby:db';
> values next value for s; 
> Thanks to Knut for finding this one.

--
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

        

Mime
View raw message