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] Closed: (DERBY-4884) DatabasePropertyTestSetup cannot change static properties in encrypted databases
Date Tue, 09 Nov 2010 10:19:08 GMT

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

Knut Anders Hatlen closed DERBY-4884.

          Resolution: Fixed
       Fix Version/s:
    Issue & fix info:   (was: [Patch Available])

Committed revision 1032907.

> DatabasePropertyTestSetup cannot change static properties in encrypted databases
> --------------------------------------------------------------------------------
>                 Key: DERBY-4884
>                 URL: https://issues.apache.org/jira/browse/DERBY-4884
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>             Fix For:
>         Attachments: derby-4884-1a.diff, derby-4884-2a.diff
> DatabasePropertyTestSetup needs to reboot the database in order to set static properties.
In tests with encrypted databases, the database cannot be rebooted because the boot password
is only known inside the setUp() method of the decorator created by Decorator.encryptedDatabase().
> One of the problems that results from this, is that BlobClob4Blob test cannot reduce
the lock timeout for the encrypted variant of the test. Since there are four test cases that
wait for a lock timeout, the test takes almost four minutes longer than it would have if the
lock timeout had been reduced.

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

View raw message