[ 
https://issues.apache.org/jira/browse/JENA-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120087#comment-14120087
 ] 

Simon Helsen commented on JENA-775:
-----------------------------------

Matt, just for the record, the explicit gc call did not always work, even 
though it appeared to work most of the time. But then again, it could be that 
an IBM JRE is still acting slightly different. 

> Jena TDB doesn't seem to release all file handles when dataset is closed
> ------------------------------------------------------------------------
>
>                 Key: JENA-775
>                 URL: https://issues.apache.org/jira/browse/JENA-775
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: TDB
>    Affects Versions: TDB 1.0.2
>         Environment: Windows
>            Reporter: Matthew Jarvis
>
> Jena TDB doesn't allow renaming of a TDB directory after a dataset has been 
> opened and a model has been added.  It appears as though there is an open 
> file handle that is preventing the rename from succeeding.  The following 
> JUnit test fails:
> {noformat}
> import java.io.File;
> import junit.framework.Assert;
> import org.junit.Test;
> import com.hp.hpl.jena.query.Dataset;
> import com.hp.hpl.jena.rdf.model.Model;
> import com.hp.hpl.jena.tdb.StoreConnection;
> import com.hp.hpl.jena.tdb.TDBFactory;
> import com.hp.hpl.jena.tdb.base.file.Location;
> import com.hp.hpl.jena.vocabulary.RDFS;
> @Test
> public void testRename() {
>       String path = "C:\\tmp\\indexTdb";
>       Dataset ds = TDBFactory.createDataset(path);
>       StoreConnection.make(path);
>       Model model = ds.getNamedModel(RDFS.Class.getURI());
>       ds.addNamedModel(RDFS.Class.getURI(), model);
>       ds.close();
>       StoreConnection.release(new Location(path));
>       File tdbRename = new File(path);
>       Assert.assertTrue(tdbRename.renameTo(new 
> File("C:\\tmp\indexTdbMoved")));
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to