CoreContextFactory keeps reference to resources after shutdown

• Key: DIRSERVER-324
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Alex Karasulu
• Reporter: Stephane Bailliez

Description

I'm trying to build apacheds on windows and tests fails because it is unable to delete database files created during tests.
Here is the typical stacktrace I get when running tests:

Unable to delete file: target\apacheds\apacheUpdn.lg
java.io.IOException: Unable to delete file: target\apacheds\apacheUpdn.lg
at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:659)
at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:540)
at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:509)
at org.apache.ldap.server.AbstractCoreTest.doDelete(AbstractCoreTest.java:144)
at org.apache.ldap.server.AbstractCoreTest.setUp(AbstractCoreTest.java:128)
at org.apache.ldap.server.authn.SimpleAuthenticationTest.setUp(SimpleAuthenticationTest.java:90)

As far as I can see, it might be because org.apache.ldap.server.jndi.CoreContextFactory keeps references to SystemPartition, GlobalRegistries and RootNexus which themselves hold references to JDBMDatabase which probably hold references to db files.

The shutdown command does not close and clean these references which does not show under linux when doing a brute force file directory deletion, but with windows as it is not possible to delete files which handles are not released it might be the cause of the problem.
 I'm investigating but I'm missing a lot of the logic behind it and the problem might go even deeper.

Comments

[Trustin Lee]

This issue has been resolved. Please check the branch 'direve-158'.

[Emmanuel Lecharny]

Closing all issues created in 2005 and before which are marked resolved