[
https://issues.apache.org/jira/browse/JENA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268319#comment-13268319
]
Andy Seaborne commented on JENA-240:
------------------------------------
If there were some documentation (plain text, or markdown) we could add it to
the website. Javadoc can be hard to find.
In fact a page on using federated would be good - if the features of Service
are documented, I'll start a more general federated query page and include it.
> 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
