Yes that line is showing the query processing time [1447] is the Fuseki Request ID, it is an atomic sequential counter starting from 1 that simply numbers requests in the order that they arrive. This value is also returned in the HTTP response via the Fuseki-Request-ID header
How are you implementing the timeout? If you are using ARQ remote SPARQL support as your client then the timeout is entirely implemented on the client side and mainly the client just stops waiting for the HTTP response. Though depending on the point in the remote request process the time-out may not actually apply at all. It does not pass the timeout through to the remote server (ecause there is no standard mechanism for this and the code does not know what kind of server it is talking to. Therefore Fuseki has no idea whether a query is supposed to be terminated. It won't notice that the client has stopped waiting for a response until it tries to write out a response and gets an IO error which will be logged. In general Fuseki does not currently have any mechanism to allow the client to communicate a desired timeout for a query to the server. Fuseki does allow for configuring a global server side timeout, the example configuration file in the documentation at https://jena.apache.org/documentation/serving_data/index.html#fuseki-config uration-file does show an example of setting this Rob On 16/06/2014 11:44, "Matteo Moci" <[email protected]> wrote: >Hi All, >I developed a client that connects to a remote fuseki through an http >client, >configurable with a timeout on the queries that exceed 1 minute >in answering. > >I saw that on the server side logs there are lines like these: > >11:00:08 INFO Fuseki :: [1447] POST >http://srvgal100.deri.ie:8080/l2m/query >11:00:08 WARN Fuseki :: SPARQL Query: Unrecognize request >parameter (ignored): queryLn >11:00:08 WARN Fuseki :: SPARQL Query: Unrecognize request >parameter (ignored): infer >11:00:08 INFO Fuseki :: [1447] Query = […] >11:00:08 INFO Fuseki :: [1447] exec/select >11:00:08 DEBUG ConNeg :: Accept request: >application/sparql-results+xml;q=0.8, application/xml;q=0.8 >11:00:08 DEBUG ConNeg :: Content type chosen: >[application/sparql-results+xml] >11:00:08 TRACE Fuseki :: Content-Type for response: >application/sparql-results+xml >11:00:08 INFO Fuseki :: [*1447*] 200 OK (*80 ms*) > >Is the last line showing the current query processing time, with 1447 >being >the thread id? > >Since I have some timeouts happening on the client side, >I'd like to ask if it's possible (on the server side) >to log the queries who have a timeout happening. > >I see really low times for any type of query, >so it's a bit strange that sometimes >the latency for a query goes over the roof to 1 minute. > >Anyway, I'll have to look into network issues. > >Thanks, >Matteo > > > > > >-- >Matteo Moci >http://mox.fm
