[
https://issues.apache.org/jira/browse/JENA-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085046#comment-13085046
]
Andy Seaborne commented on JENA-95:
-----------------------------------
This wasn't the original US for expel, but it seems reasonable to use it as
this (rename as "release"?). No file handles should be kept.
But it does seem to work for me - I can't reproduce this. What is needed is a
test case to give a sequence of TxTDB operations that leads to the situation.
The code you cite (in JournalControl.recoverNodeDat) is called only on dataset
recovery. I've added dataJrnl.close() ;
Is there a recovery going on? Recovery is done if a non-empty node data
journal file is found during initializing that dadaset for transactions.
> journal.jrl is not released when expelling a alocation
> ------------------------------------------------------
>
> Key: JENA-95
> URL: https://issues.apache.org/jira/browse/JENA-95
> Project: Jena
> Issue Type: Bug
> Components: TDB
> Reporter: Simon Helsen
> Priority: Critical
>
> whenever I call StoreConnection.expel(location) it seems that something is
> holding on to journal.jrl in location
> Caused by:
> java.io.IOException: Could not delete
> D:\jfsDev\working_dir\indices\4cb718ffab6047639c383cf9582633dc\jfs-rdfindex\journal.jrnl
> at java.lang.Throwable.<init>(Throwable.java:67)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
