Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Date: Wed, 9 Nov 2011 23:11:51 +0000 (UTC)
From: "Alexander Dutton (Commented) (JIRA)" <jira@apache.org>
To: jena-dev@incubator.apache.org
Message-ID: 
 <1330922746.15865.1320880311586.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <190770826.15849.1320879831607.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (JENA-158) QueryCancelledException not being
 caught in Fuseki
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JENA-158?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D131473=
53#comment-13147353 ]=20

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 i=
n 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 mess=
age in this issue's thread on jena-dev.
               =20
> 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
>
> [This is a reformulation of http://mail-archives.apache.org/mod_mbox/incu=
bator-jena-dev/201111.mbox/%3C4EBAA0A3.8%40oucs.ox.ac.uk%3E and following m=
essages]
> 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 erro=
r message provided.
> I don't know what HTTP status code should be provided; the SPARQL spec sa=
ys 500, but that upsets me (and Hugh Glaser)=C2=B9. Andy points out that it=
 should be a 5xx status code=C2=B2. I've started a thread on ietf-http-wg a=
sking for something along the lines of a "Request Too Onerous" status code.=
=C2=B3
> =C2=B9 http://lists.w3.org/Archives/Public/public-lod/2011Apr/0259.html
> =C2=B2 http://lists.w3.org/Archives/Public/public-lod/2011Apr/0268.html
> =C2=B3 http://lists.w3.org/Archives/Public/ietf-http-wg/2011OctDec/0188.h=
tml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira