[
https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453266#comment-13453266
]
Mark Greene commented on HTTPASYNC-24:
--------------------------------------
Oleg,
I'm seeing the same issue with a barebones unit test hitting an endpoint that
returns just a 204. The debug logs do say the connection is released but I'm
seeing an infinite loop inside EntityUtils.consume(result.getEntity());.
Here's a sample stack trace of a thread stuck in that 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)
Should this bug be reopened or should I open a new one?
> infinite loop in ContentInputStream.close
> -----------------------------------------
>
> Key: HTTPASYNC-24
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-24
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta2
> Environment: linux
> Reporter: Kireet Reddy
> Attachments: example.zip
>
>
> For requests that respond with no content, an infinite loop occurs at
> ContentInputStream.close() line 86 when using EntityUtils.toString() to read
> the response.
--
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: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
