[
https://issues.apache.org/jira/browse/JENA-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236677#comment-17236677
]
Andy Seaborne commented on JENA-1987:
-------------------------------------
[~rvesse] -
The build is showing stacktraces on back and compact operations on the task
thread. Is this right? It looks like an error case but instead of warning it's
writing a stacktrace at level INFO.
(longer extract from TS_FusekiWebapp of the build attached)
{noformat}
[INFO] 14:20:14 INFO Backup :: [357] **** Exception in backup
[INFO] org.apache.jena.fuseki.FusekiException: No dataset provided to backup
[INFO] at org.apache.jena.fuseki.mgt.Backup.backup(Backup.java:84)
~[classes/:?]
[INFO] at org.apache.jena.fuseki.mgt.Backup.backup(Backup.java:72)
~[classes/:?]
[INFO] at
org.apache.jena.fuseki.mgt.ActionBackup$BackupTask.run(ActionBackup.java:62)
~[classes/:?]
[INFO] at
org.apache.jena.fuseki.async.AsyncPool.lambda$submit$0(AsyncPool.java:66)
~[jena-fuseki-core-3.17.0-SNAPSHOT.jar:3.17.0-SNAPSHOT]
[INFO] at org.apache.jena.fuseki.async.AsyncTask.call(AsyncTask.java:100)
[jena-fuseki-core-3.17.0-SNAPSHOT.jar:3.17.0-SNAPSHOT]
[INFO] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[?:1.8.0_275]
[INFO] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[?:1.8.0_275]
[INFO] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[?:1.8.0_275]
[INFO] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_275]
{noformat}
> HTTP API for TDB compact AND/OR periodical compact
> --------------------------------------------------
>
> Key: JENA-1987
> URL: https://issues.apache.org/jira/browse/JENA-1987
> Project: Apache Jena
> Issue Type: New Feature
> Components: Fuseki
> Reporter: Martin Kopeček
> Assignee: Rob Vesse
> Priority: Major
> Fix For: Jena 3.17.0
>
> Attachments: log
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> To be able to use Fuseki server as a standalone service, we need to run the
> compacting of the database from a different node (after updating the data in
> the database) using HTTP API.
> Other solution would be to implement runnign tdb compact on a configurable
> interval (e.g. 5 minutes).
> Our tdb database is updated every five minutes (so grows rapidly) and manual
> compacting is not an option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
