db-derby-dev mailing list archives

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

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

Knut Anders Hatlen commented on DERBY-4565:

> 4) I don't see any lock timeout exceptions in the test case
> itself. That is, the test does not log any of these exceptions.
> Knut, is it possible that what you are seeing are the
> subtransactions failing to get a write lock immediately and then
> falling back on the parent transaction?

No, I do see actual failures. I made the debug code in the test print
the SQLState of all exceptions and filtered out all the "too much
contention" errors, and saw that the timeout and deadlock errors were
propagated all the way up to the test client.

> 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