You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Alexander Dutton (Created) (JIRA)" <ji...@apache.org> on 2011/11/10 00:03:51 UTC
[jira] [Created] (JENA-158) QueryCancelledException not being
caught in Fuseki
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/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
[jira] [Commented] (JENA-158) QueryCancelledException not being
caught in Fuseki
Posted by "Alexander Dutton (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147353#comment-13147353 ]
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: 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/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
[jira] [Closed] (JENA-158) QueryCancelledException not being caught
in Fuseki
Posted by "Andy Seaborne (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne closed JENA-158.
------------------------------
> 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
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: Fuseki 0.2.1
>
> Attachments: jena-158.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> [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
[jira] [Updated] (JENA-158) QueryCancelledException not being
caught in Fuseki
Posted by "Paolo Castagna (Updated) (JIRA)" <ji...@apache.org>.
[ 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: (was: Jena 2.6.5)
Fuseki 0.2.1
> 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: Fuseki 0.2.1
>
> Attachments: jena-158.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> [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
[jira] [Updated] (JENA-158) QueryCancelledException not being
caught in Fuseki
Posted by "Paolo Castagna (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (JENA-158) QueryCancelledException not being
caught in Fuseki
Posted by "Andy Seaborne (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne resolved JENA-158.
--------------------------------
Resolution: Fixed
Fix Version/s: Fuseki 0.2.1
Assignee: Andy Seaborne
Patch applied.
> 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
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: Fuseki 0.2.1
>
> Attachments: jena-158.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> [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
[jira] [Updated] (JENA-158) QueryCancelledException not being
caught in Fuseki
Posted by "Alexander Dutton (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Dutton updated JENA-158:
----------------------------------
Attachment: jena-158.diff
Improves Fuseki to return a 503 with a friendlier error message on timeout.
NB. My CCLA is pending sign-off from the PTB at OUCS. The license grant is conditional on my CCLA getting the go-ahead.
> 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
> 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
[jira] [Updated] (JENA-158) QueryCancelledException not being
caught in Fuseki
Posted by "Paolo Castagna (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paolo Castagna updated JENA-158:
--------------------------------
Remaining Estimate: 1h
Original Estimate: 1h
> 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
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> [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
[jira] [Commented] (JENA-158) QueryCancelledException not being
caught in Fuseki
Posted by "Andy Seaborne (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147822#comment-13147822 ]
Andy Seaborne commented on JENA-158:
------------------------------------
Alex, thanks.
Ping this JIRA when the license grant is sorted out.
> 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
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> [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
[jira] [Updated] (JENA-158) QueryCancelledException not being
caught in Fuseki
Posted by "Paolo Castagna (Updated) (JIRA)" <ji...@apache.org>.
[ 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: (was: Fuseki 0.2.1)
> 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
> Attachments: jena-158.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> [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
[jira] [Commented] (JENA-158) QueryCancelledException not being
caught in Fuseki
Posted by "Andy Seaborne (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148685#comment-13148685 ]
Andy Seaborne commented on JENA-158:
------------------------------------
ASF has received your CCLA.
> 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
> Attachments: jena-158.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> [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