[
https://issues.apache.org/jira/browse/JENA-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446736#comment-16446736
]
Andy Seaborne commented on JENA-1528:
-------------------------------------
What do you understand "readTimeout" to be? I was taking it as the time between
connection reads, not total time. Socket timeout is an approximation of that.
In the query case, the request is sent immediately, and then the connection is
read so socket activity is reading.
[~nithril] - what were you looking for?
It is useful as a means of "making progress", guarding against slow remote
servers, and some network failures where either the TCP timeouts are too long
or the TCP connection does not go away properly due to intermediates (they can
compound TCP timeouts).
The error message is "Read timed out" on a read:
https://stackoverflow.com/questions/38555255/sockettimeoutexception-read-timed-out-httpclient
> 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)
