You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "William R. Speirs (Created) (JIRA)" <ji...@apache.org> on 2012/03/27 16:52:25 UTC
[jira] [Created] (HTTPASYNC-15) Async Client Hangs on Closed
Conection
Async Client Hangs on Closed Conection
--------------------------------------
Key: HTTPASYNC-15
URL: https://issues.apache.org/jira/browse/HTTPASYNC-15
Project: HttpComponents HttpAsyncClient
Issue Type: Bug
Affects Versions: 4.0-beta1
Reporter: William R. Speirs
When using the Async Client if you connect to a server which immediately closes the connection, the client never calls any of the callbacks. I believe that this is because response is never checked for null in DefaultNHttpClientConnection.consumeInput().
I will attached a basic reproducer which waits on a latch because none of the callbacks are triggered. I've also submitted a patch for this issue, but I'm not entirely sure what should be done in this case. The patch simply throws an HttpException, but I'm not sure if this is the right thing to do.
--
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] [Resolved] (HTTPASYNC-15) Async Client Hangs on Closed
Conection
Posted by "Oleg Kalnichevski (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPASYNC-15.
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.0-beta2
Hi William
I would like to release the new version of HttpCore prior to releasing HttpAsyncClient. This may take a month or two, I am afraid. It might also be that the next release is going to be GA so I would like to run a few performance tests as well prior to the release. Please bear with me.
Oleg
> Async Client Hangs on Closed Conection
> --------------------------------------
>
> Key: HTTPASYNC-15
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-15
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta1
> Reporter: William R. Speirs
> Fix For: 4.0-beta2
>
> Attachments: HTTPASYNC-15.diff, Main.java
>
>
> When using the Async Client if you connect to a server which immediately closes the connection, the client never calls any of the callbacks. I believe that this is because response is never checked for null in DefaultNHttpClientConnection.consumeInput().
> I will attached a basic reproducer which waits on a latch because none of the callbacks are triggered. I've also submitted a patch for this issue, but I'm not entirely sure what should be done in this case. The patch simply throws an HttpException, but I'm not sure if this is the right thing to do.
--
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-15) Async Client Hangs on Closed
Conection
Posted by "William R. Speirs (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239910#comment-13239910 ]
William R. Speirs commented on HTTPASYNC-15:
--------------------------------------------
Tested against trunk and it now returns failed, which is what one would expect.
Any idea when the next beta of HttpAsyncClient will come out?
Thanks!
> Async Client Hangs on Closed Conection
> --------------------------------------
>
> Key: HTTPASYNC-15
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-15
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta1
> Reporter: William R. Speirs
> Attachments: HTTPASYNC-15.diff, Main.java
>
>
> When using the Async Client if you connect to a server which immediately closes the connection, the client never calls any of the callbacks. I believe that this is because response is never checked for null in DefaultNHttpClientConnection.consumeInput().
> I will attached a basic reproducer which waits on a latch because none of the callbacks are triggered. I've also submitted a patch for this issue, but I'm not entirely sure what should be done in this case. The patch simply throws an HttpException, but I'm not sure if this is the right thing to do.
--
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-15) Async Client Hangs on Closed
Conection
Posted by "William R. Speirs (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William R. Speirs updated HTTPASYNC-15:
---------------------------------------
Attachment: HTTPASYNC-15.diff
> Async Client Hangs on Closed Conection
> --------------------------------------
>
> Key: HTTPASYNC-15
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-15
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta1
> Reporter: William R. Speirs
> Attachments: HTTPASYNC-15.diff
>
>
> When using the Async Client if you connect to a server which immediately closes the connection, the client never calls any of the callbacks. I believe that this is because response is never checked for null in DefaultNHttpClientConnection.consumeInput().
> I will attached a basic reproducer which waits on a latch because none of the callbacks are triggered. I've also submitted a patch for this issue, but I'm not entirely sure what should be done in this case. The patch simply throws an HttpException, but I'm not sure if this is the right thing to do.
--
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-15) Async Client Hangs on Closed
Conection
Posted by "William R. Speirs (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William R. Speirs updated HTTPASYNC-15:
---------------------------------------
Attachment: Main.java
> Async Client Hangs on Closed Conection
> --------------------------------------
>
> Key: HTTPASYNC-15
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-15
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta1
> Reporter: William R. Speirs
> Attachments: HTTPASYNC-15.diff, Main.java
>
>
> When using the Async Client if you connect to a server which immediately closes the connection, the client never calls any of the callbacks. I believe that this is because response is never checked for null in DefaultNHttpClientConnection.consumeInput().
> I will attached a basic reproducer which waits on a latch because none of the callbacks are triggered. I've also submitted a patch for this issue, but I'm not entirely sure what should be done in this case. The patch simply throws an HttpException, but I'm not sure if this is the right thing to do.
--
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-15) Async Client Hangs on Closed
Conection
Posted by "Oleg Kalnichevski (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPASYNC-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239887#comment-13239887 ]
Oleg Kalnichevski commented on HTTPASYNC-15:
--------------------------------------------
Hi William
I believe I have fixed the problem in SVN trunk. Could you please try out the latest SVN snapshot and let me know if the problem still persists?
Oleg
> Async Client Hangs on Closed Conection
> --------------------------------------
>
> Key: HTTPASYNC-15
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-15
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta1
> Reporter: William R. Speirs
> Attachments: HTTPASYNC-15.diff, Main.java
>
>
> When using the Async Client if you connect to a server which immediately closes the connection, the client never calls any of the callbacks. I believe that this is because response is never checked for null in DefaultNHttpClientConnection.consumeInput().
> I will attached a basic reproducer which waits on a latch because none of the callbacks are triggered. I've also submitted a patch for this issue, but I'm not entirely sure what should be done in this case. The patch simply throws an HttpException, but I'm not sure if this is the right thing to do.
--
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