You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/04/22 12:45:16 UTC

[jira] [Assigned] (DERBY-6546) Database can't be dropped on Windows using the decoration of LuceneSupportPermsTest

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

Knut Anders Hatlen reassigned DERBY-6546:
-----------------------------------------

    Assignee: Knut Anders Hatlen

Probably, one of the decorators needs to connect to the database in its tearDown() method. Since the decorators' tearDown() methods execute after the tearDown() method of the test case, that will cause the database to be rebooted after the engine was shut down.

I'll take a look.

> Database can't be dropped on Windows using the decoration of LuceneSupportPermsTest
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-6546
>                 URL: https://issues.apache.org/jira/browse/DERBY-6546
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Knut Anders Hatlen
>
> LuceneSupportPermsTest piles on sql authorization, sql authentication, custom policy file, custom locale, and single use decorators. With this combination, the database cannot be removed at test termination on Windows machines. The problem may be that the authentication hurdle prevents the decorator machinery from getting a connection to the database in order to shut it down. So files are left open and Windows can't delete the database directory.



--
This message was sent by Atlassian JIRA
(v6.2#6252)