hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Poul (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1586) Enrich ConnectException with remoteAddress
Date Sat, 06 Dec 2014 18:30:12 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236916#comment-14236916

Gerhard Poul commented on HTTPCLIENT-1586:

[~olegk] you are correct; I have now cleared my maven cache and performed a mvn clean and
I see the same exception you see with the non-legacy code. Not sure what went wrong there

Do you think it might make sense still to enhance the legacy code as well? I would volunteer
to do it if you can tell me what you think should be done or what you think about my current

If you don't want to change the legacy code as it will be dropped anyway, we can certainly
also close this ticket.

> 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

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

View raw message