[ 
https://issues.apache.org/jira/browse/JENA-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398653#comment-13398653
 ] 

Andy Seaborne commented on JENA-236:
------------------------------------

Maybe other work in the area corrected the problem; there a report on fuseki 
locking up on loop bck and it was because the service code was not materialing 
results, leaving results in the server (localcase - limited netwrok buffering).

If so, apologies, I should have noticed and closed the JIRA.  Close now?
                
> Allow Service XML Parsing error to cancel the query on a per query basis
> ------------------------------------------------------------------------
>
>                 Key: JENA-236
>                 URL: https://issues.apache.org/jira/browse/JENA-236
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: ARQ
>    Affects Versions: ARQ 2.9.0
>         Environment: All
>            Reporter: Claude Warren
>            Assignee: Rob Vesse
>              Labels: features
>         Attachments: JENA-236-1.txt
>
>
> Currently an XML parsing error may occur on a hasNext() call on a Sparql 
> service query.  The result is that the entire query (not just the service 
> call) fails.
> The goal of this improvement is to capture the XML parsing error and return 
> false for the hasNext().  The result being that data errors will be silently 
> ignored.  This should be done on a per endpoint basis.  Perhaps as an 
> onParseErrorCancel flag.
> I think there is an interplay of several flags in this request:
> 1) SILENT service parameter.  If silent is true should this also be true by 
> default? (I think not, but perhaps a system setting to make that the case)
> 2) cancelAllowDrain.  If the error occurs should the cancel flag be raised? 
> (I think not, but again perhaps a per service call flag to enable this)
> 3) JENA-93 discusses changing cancelAllowDrain to be a per endpoint setting.  
> If that is the case it may apply here as well.

--
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

        

Reply via email to