incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Dutton (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-158) QueryCancelledException not being caught in Fuseki
Date Wed, 09 Nov 2011 23:11:51 GMT


Alexander Dutton commented on JENA-158:

I'll get a patch together tomorrow. My plan is to add a default message of "Query cancelled"
to QueryCancelledException, and add another catch block in SPARQL_ServletBase to return a
more useful error message.

For now I'll go with a 503 status, as Andy suggests in his most recent message in this issue's
thread on jena-dev.
> QueryCancelledException not being caught in Fuseki
> --------------------------------------------------
>                 Key: JENA-158
>                 URL:
>             Project: Jena
>          Issue Type: Improvement
>          Components: Fuseki
>            Reporter: Alexander Dutton
>            Priority: Minor
> [This is a reformulation of
and following messages]
> When a query times out the client currently receives the following, which doesn't explain
> > Error 500: Server Error
> This is the result of a QueryCancelledException being caught at line 107 of SPARQL_ServletBase,
which has the comment "This should not happen"
> It'd be good if this were explicitly caught and a more user-friendly error message provided.
> I don't know what HTTP status code should be provided; the SPARQL spec says 500, but
that upsets me (and Hugh Glaser)¹. Andy points out that it should be a 5xx status code².
I've started a thread on ietf-http-wg asking for something along the lines of a "Request Too
Onerous" status code.³
> ¹
> ²
> ³

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