[
https://issues.apache.org/jira/browse/JENA-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446781#comment-16446781
]
A. Soroka commented on JENA-1528:
---------------------------------
Yeah, this is all rather poorly documented. :sigh: I got most of it by reading
Stackoverflow and tracing the code. As I understand it, {{readTimeout}} is the
time before first packet received. {{socketTimeout}} is the time between
sockets. And there is no "total time" timeout. But as you ask, the real
question is what [~nithril] is looking for.
We could certainly expose {{socketTimeout}}, which might be quite useful. But
it's not total time elapsed.
> HttpQuery does not set the readTimeout
> --------------------------------------
>
> Key: JENA-1528
> URL: https://issues.apache.org/jira/browse/JENA-1528
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 3.7.0
> Reporter: Nicolas Labrot
> Assignee: A. Soroka
> Priority: Minor
>
> {{org.apache.jena.sparql.engine.http.HttpQuery#contextualizeTimeoutSettings}}
> sets the connectTimeout but not the readTimeout
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
