[ https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375001#comment-15375001 ]
ASF GitHub Bot commented on JENA-576: ------------------------------------- Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/151 Right, I think we're fine as long as Jena itself is actually the client (e.g. as part of `SERVICE` action in a query). It was the situation in which some app is using HTTP via `HttpOp` in which an input stream could "leak". But I think that's really just not Jena's problem, right? If you walk away with a resource from the network, you need to deal with it properly. Jena can't run after you pulling on your shirt to remind you. > 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)