[
https://issues.apache.org/jira/browse/HTTPCLIENT-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173333#comment-16173333
]
Gary Gregory commented on HTTPCLIENT-1869:
------------------------------------------
As [[email protected]] mentions, based on the Javadoc, I can see
that some folks would justify using an {{EOFException}} as the 'normal' way to
do business when an EOF is found, nasty! Very Java 1.0! ;-) Check out the
@since tag.
{code:java}
/**
* Signals that an end of file or end of stream has been reached
* unexpectedly during input.
* <p>
* This exception is mainly used by data input streams to signal end of
* stream. Note that many other input operations return a special value on
* end of stream rather than throwing an exception.
*
* @author Frank Yellin
* @see java.io.DataInputStream
* @see java.io.IOException
* @since JDK1.0
*/
{code}
> java.io.EOFException: Unexpected end of ZLIB input stream
> ---------------------------------------------------------
>
> Key: HTTPCLIENT-1869
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1869
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.5.3
> Reporter: Philippe Mouawad
> Priority: Minor
> Fix For: 4.5.4
>
>
> At JMeter project a user has reported an issue that generates this stacktrace
> :
> {code:java}
> java.io.EOFException: Unexpected end of ZLIB input stream
> at java.util.zip.InflaterInputStream.fill(Unknown Source)
> at java.util.zip.InflaterInputStream.read(Unknown Source)
> at
> org.apache.http.client.entity.DeflateInputStream.read(DeflateInputStream.java:88)
> at
> org.apache.http.client.entity.LazyDecompressingInputStream.read(LazyDecompressingInputStream.java:70)
> at
> org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135)
> at
> org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:148)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.readResponse(HTTPSamplerBase.java:1814)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPAbstractImpl.readResponse(HTTPAbstractImpl.java:440)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:433)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:74)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1189)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1178)
> at
> org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:491)
> at
> org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:425)
> at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:254)
> at java.lang.Thread.run(Unknown Source)
> {code}
> Although this issue has been reported in the past through
> https://issues.apache.org/jira/browse/HTTPCLIENT-1699 , it is not yet fixed.
> I'll propose a PR.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
