ASF GitHub Bot commented on JENA-576:

Github user afs commented on the issue:

    It looks like only a partial set of changes from http_op_3. Maybe I got the 
remote repo into a inconsistent state. I pushed some (I hoped) unrelated 
cleanup today.
    I will now also backport ServerCtl to Fuseki1 - the logging messages from 
RetryExec were suppressed and hiding a problem. This happens when the pooling 
client is not closed when the server is freed and reallocated.
    Branch http_op_3 has many small changes across  Fuseki1 and 
jena-jdbc-driver-remote testing as I made connect handling and server restart 
consistent, and also remove some debugging code left in the PR that clears the 
httpClient (sets it to null) but didn't close the old one.

> 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

Reply via email to