On 06/05/15 19:03, Christian Schwaderer wrote:
Hi,
thanks for the answer!
The full config file looks like so:
@prefix : <#> .
@prefix fuseki: <http://jena.apache.org/fuseki#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> .
[] rdf:type fuseki:Server ;
ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "4000" ] ;
.
(Comments removed)
Yes, I created the dataset with the UI. How can I remove the dataset timeout
setting?
There is a bit more in:
http://mail-archives.apache.org/mod_mbox/jena-users/201504.mbox/%3C5533D97F.20406%40apache.org%3E
but the workaround is:
The directory run/system_files has a copy of the file. This is not the
file the server works off (that's in the database).
0/ Stop the server
1/ If you have only one dataset, copy that file to
run/configuration/mydatabase.ttl (any fresh base name, must end ttl).
2/ Edit the "run/configuration" file to remove the line:
ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "3000" ] ;
or set it to whatever you want.
3/ Delete the system database
4/ Restart the server
Andy
Best,
Christian
----------------------------------------
Date: Wed, 6 May 2015 18:52:10 +0100
From: [email protected]
To: [email protected]
Subject: Re: Fuseki as Web Application read configuration file
On 06/05/15 18:44, Christian Schwaderer wrote:
Hi again,
I'm almost done setting up Fuseki as Tomcat web application. Still, there is
another problem: How can I make sure that Fuseki reads its configuration file?
I want to set a timeout (4sec) and thus, I've added the line
ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "4000" ] ;
in the file /etc/fuseki/config.ttl
But it doesn't work. Fuseki still executes queries taking about 20 seconds.
I've also copied the file config.ttl to /etc/fuseki/configuration - but to no
avail.
Thanks in advance and best regards
Christian
Hi Christian,
What's the full config file? One thing to be aware of is that it is not
set on the datatset as the more specific setting overrides the server
wide setting.
If the TDB database was created via the UI, unfortunately there is a bug
in the template for created TDB databases and it puts in a timout. It
can be removed; the server needs to be restarted.
Andy
