incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Dutton (Updated) (JIRA)" <>
Subject [jira] [Updated] (JENA-218) Fuseki should allow timeouts to be specified on a per-request basis
Date Tue, 13 Mar 2012 08:19:38 GMT


Alexander Dutton updated JENA-218:

    Attachment: config-tdb.ttl

First go at a patch, and a config file that enables the new functionality. I've got SPARQL_ServletBase
passing a DatasetRef in place of a DatasetGraph to perform (though the default implementation
calls perform with the previous signature for compatibility).
The reporting of the length of the timeout when returning the 408 is currently wrong, as it
doesn't take into account any user-provided timeout. I'm not quite sure of the best way to
get the actual timeout into the right place without changing rather a lot (one would be to
include the QueryExecution or timeout value as a member of the QueryExecutionCancelled exception).
Still got to work on the documentation. Do we need tests?
> Fuseki should allow timeouts to be specified on a per-request basis
> -------------------------------------------------------------------
>                 Key: JENA-218
>                 URL:
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki
>    Affects Versions: Fuseki 0.2.1
>            Reporter: Alexander Dutton
>              Labels: needsdocumentation, timeout
>         Attachments: config-tdb.ttl, jena-218-1.diff
> A query endpoint might want to have different timeouts depending on whether queries are
from untrusted or trusted users, or maintenance processes. The timeout could be passed with
an X- header, a Timeout header as per,
or a query parameter, respecting the system default if none is provided. The query parameter
might be less favourable as it'd be harder to filter out for Fuseki instances behind Apache.
> There is a risk that changing the behaviour to allow timeouts to be overridden will lead
to DoSs of query endpoints open to the world to some extent. This can be mitigated by defaulting
to disallowing timeout overrides.
> I'm happy to put a patch together and document it at

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message