ASF GitHub Bot commented on JENA-576:

Github user ajs6f commented on the issue:

    The errors I get in `TS_Fuseki` are always in `TestSPARQLProtocol` or 
`TestQuery`, which use `resetServer()` and load up sample data over which to 
work. They are `Connection reset` exceptions, oddly. It's as though something 
is happening between `resetServer()` and the moment when the `DatasetAccessor` 
is used to push data. I've tried using a non-pooling client, on a guess, but 
that changed nothing. The two tests succeed on their own, but run in a suite, 
they fail (at least without `static { allocServer(); }`).
    org.apache.jena.atlas.web.HttpException: java.net.SocketException: 
Connection reset
        at org.apache.jena.riot.web.HttpOp.exec(HttpOp.java:1098)
        at org.apache.jena.riot.web.HttpOp.execHttpPut(HttpOp.java:963)
        at org.apache.jena.web.DatasetAdapter.putModel(DatasetAdapter.java:63)
    Caused by: java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:209)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)

> 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