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

ASF GitHub Bot commented on JENA-576:
-------------------------------------

Github user ajs6f commented on the issue:

    https://github.com/apache/jena/pull/151
  
    Sorry, @afs , I'm working on this now but not keeping this conversation up 
to date. In fact, my most recent comment I now believe to have been wrong. See 
[here](https://hc.apache.org/httpcomponents-client-ga/tutorial/html/fundamentals.html#d5e213)
 and also that `HttpClientBuilder` is specifically marked as not thread-safe. 
So I stayed with the original move (thread `HttpClient` through the call stack) 
and got much more careful about closing resources when done with them. That 
solved the problem you found. I _think_ that this PR is ready to go. I say I 
_think_ because I've been looking at it a lot yesterday and today, and I'd like 
to leave it alone for a day and look at it with fresh eyes. But 
comments/criticism welcome immediately!


> Upgrade Apache HTTP Client to 4.3
> ---------------------------------
>
>                 Key: JENA-576
>                 URL: https://issues.apache.org/jira/browse/JENA-576
>             Project: Apache Jena
>          Issue Type: Dependency upgrade
>          Components: ARQ
>    Affects Versions: Jena 2.11.0
>            Reporter: Rob Vesse
>            Assignee: Rob Vesse
>            Priority: Minor
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> As of 2.11.0 ARQ centralizes all HTTP operations through HttpOp which relies 
> on Apache HTTP Client.  Currently we are using 4.2.3 while the latest stable 
> release is actually 4.3.1
> Therefore we should look at upgrading our code to use the latest version 
> which may entail some refactoring since there appears to have been some 
> breaking changes across the minor version bump which users have seen in usage 
> - e.g. 
> https://github.com/pyvandenbussche/sparqles/issues/9#issuecomment-27220738



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to