You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Roland Weber (JIRA)" <ji...@apache.org> on 2006/12/28 11:09:22 UTC
[jira] Resolved: (HTTPCLIENT-475) Provide support for unconnected
sockets
[ http://issues.apache.org/jira/browse/HTTPCLIENT-475?page=all ]
Roland Weber resolved HTTPCLIENT-475.
-------------------------------------
Resolution: Fixed
patch committed with modifications:
- createSocket renamed to connectSocket
- test case fixed
Marking this issue as resolved. Additional work to make use of the unconnected sockets will be performed has part of other issues.
> Provide support for unconnected sockets
> ---------------------------------------
>
> Key: HTTPCLIENT-475
> URL: http://issues.apache.org/jira/browse/HTTPCLIENT-475
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpConn
> Affects Versions: Nightly Builds
> Environment: Operating System: All
> Platform: PC
> Reporter: Benjamin Chevillon
> Assigned To: Roland Weber
> Priority: Minor
> Fix For: 4.0 Alpha 1
>
> Attachments: 2k6-12-27-socketfactory-1.txt, ConnectTest.java, ConnectTest.log, MethodAbortTest.java, MethodAbortTestWithoutProxy.log, MethodAbortTestWithProxy.log
>
>
> Overview description:
> If Proxy settings are incorrect or host does not reply, the
> HttpClient.executeMethod() hangs, and HttpMethod.abort() does not stop it. Thus,
> you cannot assert that the entire application will stop immediately on demand.
> Expected Results:
> During a HttpMethod.executeMethod(), HttpMethod.abort() should cancel
> immediately the executeMethod().
> Actual Results:
> If HttpMethod.executeMethod() freezes because of Proxy bad settings or not
> responding hostname (in fact impossible to open the socket), the abort() method
> does not do anything.
> Platform:
> I tested it on Windows XP and Linux Debian with HttpClient 3.0 RC2 (but if you
> look further I point the problem and the source code of the nightly build is
> identical).
> See comments for the dialogue about the problem, and 2 Test cases. The solution
> is described at the end, but it may implies a change in the API and works only
> since Java 1.4.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org