[
https://issues.apache.org/jira/browse/HTTPCORE-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCORE-309:
---------------------------------------
Summary: [Regression] HttpAsyncRequestExecutor incorrectly handles 204,
205, 304 responses (content body enclosed) (was: Infinite Loop in
ContentInputStream.close())
The problem is caused by HttpAsyncRequestExecutor failing to handle 204, 205,
304 responses correctly by returning a message with an enclosed content body.
Oleg
> [Regression] HttpAsyncRequestExecutor incorrectly handles 204, 205, 304
> responses (content body enclosed)
> ---------------------------------------------------------------------------------------------------------
>
> Key: HTTPCORE-309
> URL: https://issues.apache.org/jira/browse/HTTPCORE-309
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Affects Versions: 4.2.1
> Reporter: Mark Greene
> Attachments: asyncbug.tar
>
>
> I've noticed this specifically with 204 status codes (No Content). I've
> stepped through this and it appears the main cause is that the 'endOfStream'
> variable inside SimpleInputBuffer doesn't appear to be set to true.
> Here's a stack trace of a thread that is stuck in an infinite loop:
> "I/O dispatcher 7" daemon prio=10 tid=0x08ab8400 nid=0x2dcd runnable
> [0xf2bd3000]
> java.lang.Thread.State: RUNNABLE
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:129)
> at
> org.apache.http.nio.util.SimpleInputBuffer.read(SimpleInputBuffer.java:100)
> at
> org.apache.http.nio.entity.ContentInputStream.close(ContentInputStream.java:86)
> at org.apache.http.util.EntityUtils.consume(EntityUtils.java:85)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
