[
https://issues.apache.org/jira/browse/HTTPCLIENT-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Leigh updated HTTPCLIENT-1425:
------------------------------------
Attachment: HTTPCLIENT-1425.patch
This patch only closes the cache-able original response, in BasicHttpCache, if
the response is full cached. In the case that the original response is too
large to cache, it is not closed by CachingExec.
I have also included a test case that you should have better luck reproducing
this error with in TestCachingExec. The test case create a response stream
entity that does not end until after CachingExec has passed on the response.
Cheers,
James
> Socket Closed Exception When Reading Connection: close Response Entities
> ------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1425
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1425
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpCache
> Affects Versions: 4.3.1
> Environment: java version "1.7.0_25"
> OpenJDK Runtime Environment (IcedTea 2.3.12) (7u25-2.3.12-4ubuntu3)
> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: James Leigh
> Fix For: 4.3.2
>
> Attachments: HTTPCLIENT-1425.patch
>
>
> If the server sends a long chunked response, httpclient-cache will throw
> socket closed exception.
> HttpClient can deal with this response no problem (using
> HttpClients.createDefault). However, CachingHttpClients.createMemoryBound
> throws an exception every time I try it.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
