[
https://issues.apache.org/jira/browse/JENA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577492#comment-16577492
]
Andy Seaborne commented on JENA-1586:
-------------------------------------
This fix expels the database for TDB1 and TDB2 databases. That should close
all open files associated with the database.
Tom - if you get a chance to confirm this, please let us know.
Note to anyone else looking at this: On MS Windows, closing the database does
not release the memory mapped files until the process exits. This is a
long-term java issue and marked "won't fix" in the Java Issues tracker.
> Fuseki does not close files of dataset when the dataset is removed
> ------------------------------------------------------------------
>
> Key: JENA-1586
> URL: https://issues.apache.org/jira/browse/JENA-1586
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Jena 3.6.0
> Environment: Debian 9.5 with Jena 3.6.0
> Reporter: Tom den Braber
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: Jena 3.9.0
>
>
> When you remove a TDB-dataset over HTTP from the Fuseki server, Fuseki does
> not close the file.
> Steps to reproduce:
> First: create a dataset over HTTP with name 'x'. Then, delete the dataset
> with name 'x'. Now inspect the open files of the fuseki process by running
> \{{lsof -p <FUSEKI_PROCESS_ID>}} you see that a dataset with name 'x' is
> still opened by the Fuseki-process.
> Impact:
> When a Fuseki process runs for a long time, and many datasets are created and
> deleted, it will in the end lead to a situation in which you cannot create
> new datasets anymore. Each attempt to creating a dataset will lead to a HTTP
> response code 500 with message 'java.nio.file.FileSystemException:
> /var/lib/fuseki/templates/config-tdb: Too many open files'. Also, keeping the
> files open leads (I suspect) to a higher memory usage than strictly needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
