[
https://issues.apache.org/jira/browse/DERBY-6546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-6546:
--------------------------------------
Attachment: d6546-1a.diff
I think the DatabasePropertyTestSetup.builtinAuthentication() decorator is the
culprit. It reboots the database so that it can reset the properties. Since the
database is dropped when the test is done anyway, I suppose we could have used
DatabasePropertyTestSetup.builtinAuthenticationNoTeardown(), which skips
resetting the properties.
The attached patch (d6546-1a.diff) takes a different approach and moves the
shutdown of the database from the test case and into DropDatabaseTestSetup.
This way, it doesn't matter what the other decorators do, since
DropDatabaseTestSetup will shut down the database immediately before it is
dropped.
LuceneSupportPermsTest runs cleanly for me on Windows with the patch, and the
database is removed when it's done.
> 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
> Attachments: d6546-1a.diff
>
>
> 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)
