You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Kireet Reddy (JIRA)" <ji...@apache.org> on 2012/08/21 23:44:38 UTC
[jira] [Created] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Kireet Reddy created HTTPASYNC-24:
-------------------------------------
Summary: 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
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Mark Greene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453306#comment-13453306 ]
Mark Greene commented on HTTPASYNC-24:
--------------------------------------
Also...I have a unit test that I can attach but since this issue is closed JIRA doesn't present the option to upload.
> 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-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453475#comment-13453475 ]
Oleg Kalnichevski commented on HTTPASYNC-24:
--------------------------------------------
Yes, please go ahead and raise a new JIRA.
Oleg
> 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-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453347#comment-13453347 ]
Oleg Kalnichevski commented on HTTPASYNC-24:
--------------------------------------------
Mark,
If you have a reproducer, please re-open the issue and attach the test case.
Oleg
> 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-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439590#comment-13439590 ]
Oleg Kalnichevski commented on HTTPASYNC-24:
--------------------------------------------
Kireet,
I do not quite see how an empty response entity would cause the ContentInputStream#close() got into an infinite loop, given that -1 (end of stream) value returned by the read operation immediately terminates the loop. Could you please submit a test case that reproduces the issue?
Oleg
> 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Mark Greene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453370#comment-13453370 ]
Mark Greene commented on HTTPASYNC-24:
--------------------------------------
Hi Oleg,
I do in fact have a reproducer but it doesn't appear I have permission to re-open or edit this issue. Should I create 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-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Resolved] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPASYNC-24.
----------------------------------------
Resolution: Cannot Reproduce
Kireet,
I was unable to reproduce the problem using the test app you have provided. All looks OK to me. Unfortunately, I am unable to proceed without additional input.
---
INFO AsyncUrlReader - http client initialized with max connections = 20
DEBUG AsyncUrlReader - fetching http://www.feedly.com/empty.html
DEBUG DefaultHttpAsyncClient - [exchange: 1] start execution
DEBUG DefaultHttpAsyncClient - [exchange: 1] Request connection for {}->http://www.feedly.com
DEBUG PoolingClientAsyncConnectionManager - Connection request: [route: {}->http://www.feedly.com][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
DEBUG PoolingClientAsyncConnectionManager - Connection leased: [id: 1][route: {}->http://www.feedly.com][total kept alive: 0; route allocated: 1 of 2; total allocated: 0 of 20]
DEBUG DefaultHttpAsyncClient - [exchange: 1] Connection allocated: [id:1][route:{}->http://www.feedly.com][state:null]
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][r:]: Set attribute http.nio.exchange-handler
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][rw:]: Event set [w]
DEBUG HttpAsyncRequestExecutor - http-outgoing-1 [ACTIVE]: Connected
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][rw:]: Set attribute http.nio.http-exchange-state
DEBUG HttpAsyncRequestExecutor - http-outgoing-1 [ACTIVE] Request ready
DEBUG DefaultHttpAsyncClient - [exchange: 1] Attempt 1 to execute request
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][rw:]: Set timeout 5000
DEBUG RequestAddCookies - CookieSpec selected: best-match
DEBUG RequestAuthCache - Auth cache not set in the context
DEBUG RequestTargetAuthentication - Target auth state: UNCHALLENGED
DEBUG RequestProxyAuthentication - Proxy auth state: UNCHALLENGED
DEBUG headers - http-outgoing-1 >> GET /empty.html HTTP/1.1
DEBUG headers - http-outgoing-1 >> Accept: */*
DEBUG headers - http-outgoing-1 >> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.7) Gecko/2009021906 Firefox/3.0.7
DEBUG headers - http-outgoing-1 >> Referer: http://www.feedly.com
DEBUG headers - http-outgoing-1 >> Host: www.feedly.com
DEBUG headers - http-outgoing-1 >> Connection: Keep-Alive
DEBUG headers - http-outgoing-1 >> Accept-Encoding: gzip,deflate
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][rw:]: Event set [w]
DEBUG DefaultHttpAsyncClient - [exchange: 1] Request completed
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][rw:w]: 261 bytes written
DEBUG wire - http-outgoing-1 >> "GET /empty.html HTTP/1.1[\r][\n]"
DEBUG wire - http-outgoing-1 >> "Accept: */*[\r][\n]"
DEBUG wire - http-outgoing-1 >> "User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.7) Gecko/2009021906 Firefox/3.0.7[\r][\n]"
DEBUG wire - http-outgoing-1 >> "Referer: http://www.feedly.com[\r][\n]"
DEBUG wire - http-outgoing-1 >> "Host: www.feedly.com[\r][\n]"
DEBUG wire - http-outgoing-1 >> "Connection: Keep-Alive[\r][\n]"
DEBUG wire - http-outgoing-1 >> "Accept-Encoding: gzip,deflate[\r][\n]"
DEBUG wire - http-outgoing-1 >> "[\r][\n]"
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][r:w]: Event cleared [w]
DEBUG HttpAsyncRequestExecutor - http-outgoing-1 [ACTIVE] Request ready
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][r:r]: 273 bytes read
DEBUG wire - http-outgoing-1 << "HTTP/1.1 200 OK[\r][\n]"
DEBUG wire - http-outgoing-1 << "Content-Type: text/html[\r][\n]"
DEBUG wire - http-outgoing-1 << "Content-Length: 0[\r][\n]"
DEBUG wire - http-outgoing-1 << "Connection: close[\r][\n]"
DEBUG wire - http-outgoing-1 << "Accept-Ranges: bytes[\r][\n]"
DEBUG wire - http-outgoing-1 << "Access-Control-Allow-Origin: *[\r][\n]"
DEBUG wire - http-outgoing-1 << "Date: Thu, 23 Aug 2012 12:18:56 GMT[\r][\n]"
DEBUG wire - http-outgoing-1 << "ETag: W/"0-1345648347000"[\r][\n]"
DEBUG wire - http-outgoing-1 << "Last-Modified: Wed, 22 Aug 2012 15:12:27 GMT[\r][\n]"
DEBUG wire - http-outgoing-1 << "Server: Apache-Coyote/1.1[\r][\n]"
DEBUG wire - http-outgoing-1 << "[\r][\n]"
DEBUG headers - http-outgoing-1 << HTTP/1.1 200 OK
DEBUG headers - http-outgoing-1 << Content-Type: text/html
DEBUG headers - http-outgoing-1 << Content-Length: 0
DEBUG headers - http-outgoing-1 << Connection: close
DEBUG headers - http-outgoing-1 << Accept-Ranges: bytes
DEBUG headers - http-outgoing-1 << Access-Control-Allow-Origin: *
DEBUG headers - http-outgoing-1 << Date: Thu, 23 Aug 2012 12:18:56 GMT
DEBUG headers - http-outgoing-1 << ETag: W/"0-1345648347000"
DEBUG headers - http-outgoing-1 << Last-Modified: Wed, 22 Aug 2012 15:12:27 GMT
DEBUG headers - http-outgoing-1 << Server: Apache-Coyote/1.1
DEBUG HttpAsyncRequestExecutor - http-outgoing-1 [ACTIVE] Response received
DEBUG DefaultHttpAsyncClient - [exchange: 1] Response received HTTP/1.1 200 OK
DEBUG HttpAsyncRequestExecutor - http-outgoing-1 [ACTIVE] Input ready
DEBUG DefaultHttpAsyncClient - [exchange: 1] Consume content
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][r:r]: 0 bytes read
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[ACTIVE][r:r]: Close
DEBUG DefaultHttpAsyncClient - [exchange: 1] Response fully read
DEBUG DefaultHttpAsyncClient - [exchange: 1] Connection cannot be kept alive
DEBUG BoundedAsyncResponseConsumer - building result of size 0 bytes for http://www.feedly.com/empty.html
DEBUG DefaultHttpAsyncClient - [exchange: 1] Response processed
DEBUG DefaultHttpAsyncClient - [exchange: 1] releasing connection [id:1][route:{}->http://www.feedly.com][state:null]
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[CLOSED][]: Remove attribute http.nio.exchange-handler
DEBUG IOSessionImpl - http-outgoing-1 192.168.42.190:36181<->216.218.207.140:80[CLOSED][]: Shutdown
DEBUG PoolingClientAsyncConnectionManager - Connection released: [id: 1][route: {}->http://www.feedly.com][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20]
DEBUG AsyncUrlReader - http://www.feedly.com/empty.html completed
---
Oleg
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Updated] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Kireet Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kireet Reddy updated HTTPASYNC-24:
----------------------------------
Attachment: example.zip
run Bug24.java
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Mark Greene (JIRA)" <ji...@apache.org>.
[ 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-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439629#comment-13439629 ]
Oleg Kalnichevski commented on HTTPASYNC-24:
--------------------------------------------
Kireet,
Could you please try to reduce the amount of custom code necessary to reproduce the issue to the absolute minimum, removing all non-essential custom classes, something as close to a unit test as possible?
Oleg
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
[jira] [Commented] (HTTPASYNC-24) infinite loop in
ContentInputStream.close
Posted by "Kireet Reddy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439618#comment-13439618 ]
Kireet Reddy commented on HTTPASYNC-24:
---------------------------------------
these are also the basic classes I use for Bug 23. I will see if I can get a full log for you for that 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org