[
https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565326#comment-15565326
]
ASF GitHub Bot commented on JENA-576:
-------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/151
I have just pushed a branch to https://github.com/afs/jena/tree/http_op
where the tests+setup are extracted into a single class
`AFS_TestRemoteEndpointConnection` and if this is called twice (see
`AFS_TS_Debug`) I get one failure on the second run.
The other test is now no more than add a quad and then:
```
JenaConnection conn = this.getConnection(ds);
conn.close();
```
In fact, adding and deleting the test quad still makes the test fail.
My best guess at the moment is that `ServerTest.resetServer();` is broken
(look for `//AFS Suspect`).
It is the only use of `UpdateExecutionFactory.createRemote`.
If a no-op SPARQL Update is done:
```
UpdateRequest request = UpdateFactory.create("INSERT DATA {}") ;
UpdateProcessor proc = UpdateExecutionFactory.createRemote(request,
ServerTest.serviceUpdate) ;
```
there is still a test failure. This is the [AFS-debug-2
commit](https://github.com/afs/jena/commit/7f4030ffd0db394ac1e5ad1bbca2c84a2edce4c7).
Dropping the server and recreating - everything is fine.
Resetting the server in the overall test suite, not between classes -
everything is fine.
> 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)
