[
https://issues.apache.org/jira/browse/PROTON-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721028#comment-17721028
]
ASF subversion and git services commented on PROTON-2729:
---------------------------------------------------------
Commit 62c409728edf2200087fe4e5edba672169b2d6ca in qpid-proton-dotnet's branch
refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=qpid-proton-dotnet.git;h=62c4097 ]
PROTON-2729 Ensure that a connect failed error message has details
Log using the configured remote host and port and not the resulting
resolved Endpoint which isn't populated if the channel has been fully
connected.
> [proton-dotnet] Ensure logging on failed connect displays remote location data
> ------------------------------------------------------------------------------
>
> Key: PROTON-2729
> URL: https://issues.apache.org/jira/browse/PROTON-2729
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-dotnet
> Affects Versions: proton-dotnet-1.0.0-M8
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Minor
> Fix For: proton-dotnet-1.0.0-M9
>
>
> The logging for transport connection failures can end up logging null for the
> remote location because a transport channel doesn't get populated for remote
> endpoint details unless a successful connection is made. Instead log the
> configure host and port values which are always set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
