[
https://issues.apache.org/jira/browse/JENA-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141395#comment-15141395
]
Andy Seaborne commented on JENA-1043:
-------------------------------------
{{close()}} exists but it gets complicated because app can close when it's
still in use resulting in unexpected crashes. Anything exposed in the public
API is at risk of that effect so {{DatasetGraph}} at most, not {{Dataset}}.
If Fuseki were better integrated into Tomcat shutdown, it would release earlier
so be less prone to JENA-1136 (which looks like the fact Tomcat shutdown is
quite slow until true JVM exit). It would find each service and/or even
directly close TDB databases by calling {{StoreConnection}}. I'm not sure if
jena-text datasets have the same access at the moment.
(Caveat: I haven't a chance to test this - this is thinking out loud.)
> Running Fuseki in Tomcat does not respect Tomcat manager stop/start.
> --------------------------------------------------------------------
>
> Key: JENA-1043
> URL: https://issues.apache.org/jira/browse/JENA-1043
> Project: Apache Jena
> Issue Type: Bug
> Components: eki, Fuseki
> Affects Versions: Fuseki 2.3.0
> Reporter: Andy Seaborne
>
> Fuseki needs a dataset start/stop lifecycle and couple this into
> {{FusekiServerListener}} which is the {{ServletContextListener}} for Fuseki.
> See [thread on
> users@|http://mail-archives.apache.org/mod_mbox/jena-users/201509.mbox/%3C55F849D7.3010403%40u.washington.edu%3E].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
