[
https://issues.apache.org/jira/browse/JENA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174023#comment-15174023
]
Andy Seaborne commented on JENA-1146:
-------------------------------------
Your choice - whichever way works best for you.
We seem to have have evolved to closing in bulk when a release is done for the
last few releases (with no email notifications!). i.e. leave as "resolved" and
it gets done later.
The "resolve" is the important step from the point of view of tracking JIRA.
> jena.textindexer does not close resources
> ------------------------------------------
>
> Key: JENA-1146
> URL: https://issues.apache.org/jira/browse/JENA-1146
> Project: Apache Jena
> Issue Type: Bug
> Components: Cmd line tools, Jena, Text
> Affects Versions: Jena 3.0.1
> Reporter: Joël Kuiper
> Assignee: Osma Suominen
> Priority: Minor
> Fix For: Jena 3.1.0
>
>
> This is a bit of a minor issue since the jena.textindexer is meant to be ran
> from the command line. But in our app we call it directly from the JVM
> process and then proceed to do some other operations. This fails when also
> using the text index, since Lucene can't acquire a lock in that case (it's
> limited to one connection). As a work-around we now set the textIndex and
> dataset fields to public using reflection, and manually close the resources.
> But ideally this should happen after the main command body.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
