Hi Rajiv,
You can find how to set query timeouts in the Fuseki documentation at [1]
To set server wide timeout:
[] rdf:type fuseki:Server ;
#Server-wide context parameters can be given here.
#For example, to set query timeouts: on a server-wide basis:
#Format 1: "1000"-- 1second timeout
#Format 2: "10000,60000"-- 10s timeout to first result, then 60s
timeout to for rest of query.
#See java doc for ARQ.queryTimeout
#ja:context [ ja:cxtName "arq:queryTimeout"; ja:cxtValue "10000"] ;
Uncomment the last line and set the value you require per the comments
above.
Do you have a reverse proxy configured to limit the rate at which
requests are going to Fuseki? Can you confirm that all your requests
are going through that proxy?
Brian
[1]
http://jena.apache.org/documentation/serving_data/#running-a-fuseki-server
On 11/12/2013 19:47, Chaudhuri, Rajiv wrote:
Hi,
Our application which is running at Tomcat server is making query to Fuseki
TDB store using HTTP protocol.
We have observed that thread count for the Fuseki process is increasing
with time.
I know there might be code issue and resources should be closed properly.
*But we would like to achieve the same using configuration at Fuseki
server- i.e. If the query takes too much time (which means that resource is
not closed by application server) then there should be time out and Fuseki
server should implicitly kill the thread.*
The impact of this thread count getting increased is Fuseki server stop
responding and process gets kill automatically after sometimes and we have
to restart the Fuseki server again.
--
Epimorphics Ltd (http://www.epimorphics.com) Epimorphics Ltd. is a limited
company registered in England (number 7016688)
Registered address: Court Lodge, 105 High Street, Portishead, Bristol BS20 6PT,
UK
