[
https://issues.apache.org/jira/browse/JENA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Castagna updated JENA-158:
--------------------------------
Fix Version/s: 2.6.5
> QueryCancelledException not being caught in Fuseki
> --------------------------------------------------
>
> Key: JENA-158
> URL: https://issues.apache.org/jira/browse/JENA-158
> Project: Jena
> Issue Type: Improvement
> Components: Fuseki
> Reporter: Alexander Dutton
> Priority: Minor
> Fix For: 2.6.5
>
> Attachments: jena-158.diff
>
>
> [This is a reformulation of
> http://mail-archives.apache.org/mod_mbox/incubator-jena-dev/201111.mbox/%3C4EBAA0A3.8%40oucs.ox.ac.uk%3E
> and following messages]
> When a query times out the client currently receives the following, which
> doesn't explain much:
> > 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.³
> ¹ http://lists.w3.org/Archives/Public/public-lod/2011Apr/0259.html
> ² http://lists.w3.org/Archives/Public/public-lod/2011Apr/0268.html
> ³ http://lists.w3.org/Archives/Public/ietf-http-wg/2011OctDec/0188.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
