You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Rob Vesse (JIRA)" <ji...@apache.org> on 2012/05/03 18:28:50 UTC

[jira] [Resolved] (JENA-240) If the remote SPARQL Service endpoint does not respond the query hangs, Adding timeout to the Service should fix the problem

     [ https://issues.apache.org/jira/browse/JENA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Vesse resolved JENA-240.
----------------------------

       Resolution: Fixed
    Fix Version/s: ARQ 2.9.1

Marking as resolved now patch is applied, will leave open for a few days to allow time for this to land in snapshots and get tested by others
                
> If the remote SPARQL Service endpoint does not respond the query hangs, Adding timeout to the Service should fix the problem
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JENA-240
>                 URL: https://issues.apache.org/jira/browse/JENA-240
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: ARQ
>    Affects Versions: ARQ 2.9.0, ARQ 2.9.1
>            Reporter: Claude Warren
>            Assignee: Rob Vesse
>             Fix For: ARQ 2.9.1
>
>         Attachments: TestService.java, patch.txt, patch.txt
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When creating the HttpQuery object the com.hp.hpl.jena.sparql.engine.http.Service class does not set any timeout values.  HttpQuery will hang if the remote endpoint does not respond. 
> I think the solution is to allow the context to specify the timeout values (and perhaps other setter values on HttpQuery).  The context should have default values and provide a mechanism to override the defaults based on the URL.  Similar to the way query parameters are configured after JENA-195.

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