db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4565) Create concurrency test to stress sequence generators.
Date Tue, 09 Mar 2010 16:49:27 GMT

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

Rick Hillegas updated DERBY-4565:

    Attachment: derby-4565-02-ab-useWaitTimeout.diff

Attaching a second rev of the second patch: derby-4565-02-ab-useWaitTimeout.diff. This version
makes a couple additional changes:

1) Fixes an NPE raised by the special test implementation of SequenceUpdater.

2) Only calls System.currentTimeMillis() if a retry is necessary, as Knut suggested.

3) Makes the test client report all Throwables and not just SQLExceptions.

I am still not seeing timeout and deadlock errors when I turn on debugging. That is, the following
command runs cleanly without intercepting and printing any errors:

runjava org.apache.derbyTesting.perf.clients.Runner \
    -driver org.apache.derby.jdbc.EmbeddedDriver \
    -init \
    -load seq_gen \
    -load_opts debugging=1,numberOfGenerators=5,tablesPerGenerator=10,insertsPerTransaction=100
    -gen b2b \
    -threads 10 \

Knut, if you apply the patch and run the command above (without changing the code in the patch),
do you still see timeouts and deadlocks?


> Create concurrency test to stress sequence generators.
> ------------------------------------------------------
>                 Key: DERBY-4565
>                 URL: https://issues.apache.org/jira/browse/DERBY-4565
>             Project: Derby
>          Issue Type: Task
>          Components: SQL, Test
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-4565-01-ad-firstRev.diff, derby-4565-02-aa-useWaitTimeout.diff,
> Create a concurrency test to find bottlenecks and bugs in sequence generators.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message