[
https://issues.apache.org/jira/browse/JENA-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084175#comment-13084175
]
Simon Helsen commented on JENA-95:
----------------------------------
Andy, I will try again with the latest build (I am using one from 0809).
Comments:
1) we do not expel when transactions on that particular store are still active
(at least not knowingly - perhaps there is a bug). We abort all still running
queries when a shutdown is initiated
2) it is a regular use case for us to be able to be able shutdown any of our
triple stores and the restart them (typical use-cases are back up, reindex,
compacting, etc.), so I am not sure what you mean by "It should not be
necessary to call either in regular use". What is regular for you?
3) When you say the "order of operations" seems important, what does that mean?
4) can you please comment on what I wrote in the second comment above (re:
NodeTableTrans)
> 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
> 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
