You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2014/12/07 13:31:12 UTC

[jira] [Resolved] (HTTPCLIENT-1586) Enrich ConnectException with remoteAddress

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPCLIENT-1586.
-------------------------------------------
    Resolution: Won't Fix

Gerhard,
The next release after 4.4 is very likely to be 5.0. I would not bother with patching deprecated code. There are better ways to improve HttpClient.

Oleg

> Enrich ConnectException with remoteAddress
> ------------------------------------------
>
>                 Key: HTTPCLIENT-1586
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1586
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpConn
>    Affects Versions: 4.4 Beta1
>            Reporter: Gerhard Poul
>            Priority: Minor
>         Attachments: httpclient-1586-patch1.patch
>
>
> When a ConnectException is thrown by Java it only contains information like "connection refused", but not the remoteAddress that we tried connecting to and while some code paths in HttpClient log this as info the core Exception is just propagated to the end-user.
> I propose to either change the description of the original ConnectException or create a new httpclient-specific ConnectException like java.rmi does.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org