[
https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15558621#comment-15558621
]
ASF GitHub Bot commented on JENA-576:
-------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/151
I pulled this PR into a clean copy of Jena (I did `git pull
https://github.com/apache/jena/ pull/151/head` in to a branch
I get test failures in jena-jdbc-driver-remote: with maven:
```
Failed tests:
TestRemoteEndpointConnection>AbstractJenaConnectionTests.connection_statement_query_select_max_rows_01:531
expected:<10> but was:<0>
TestRemoteEndpointConnection>AbstractJenaConnectionTests.connection_statement_query_select_max_rows_02:578
expected:<1> but was:<0> It looks like state across tests is
TestRemoteEndpointConnection>AbstractJenaConnectionTests.connection_statement_query_select_max_rows_03:625
expected:<10> but was:<0>
TestRemoteEndpointConnectionWithResultSetTypes>AbstractJenaConnectionTests.connection_statement_query_select_max_rows_01:531
expected:<10> but was:<0>
TestRemoteEndpointConnectionWithResultSetTypes>AbstractJenaConnectionTests.connection_statement_query_select_max_rows_02:578
expected:<1> but was:<0>
TestRemoteEndpointConnectionWithResultSetTypes>AbstractJenaConnectionTests.connection_statement_query_select_max_rows_03:625
expected:<10> but was:<0>
```
In Eclipse:
If I run `TestRemoteEndpointConnection` on its own it runs.
If I run the tests in the `connections` package,
`TestRemoteEndpointConnectionWithResultSetTypes` has 3 failures but not
`TestRemoteEndpointConnection`.
Running `TestRemoteEndpointConnectionWithResultSetTypes` on it own it works.
Also in Eclipse (right-click on the project, runAs -> JUnit test), ,
running all the tests in jena-jdbc-driver-remote locks up. (Running in Eclipse
with maven gives the 6 failures.)
What is different this time in the lock-up is that the connections are in
state ESTABLISHED, not TIME_WAIT. This shows that there is deadlock, not
resource problems.
> 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)
