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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
