qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gordon Sim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-1395) Better description of ssl errors in logs
Date Wed, 07 Aug 2019 19:56:00 GMT

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

Gordon Sim commented on DISPATCH-1395:

I'm not sure whether this is a proton or dispatch issue or perhaps a bit of both.

> Better description of ssl errors in logs
> ----------------------------------------
>                 Key: DISPATCH-1395
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1395
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>            Reporter: Gordon Sim
>            Priority: Major
> See also PROTON-1870. The two issues I hit were both related to the router. The first
is as described in that proton issue, attempting to use a cert that was only valid as a tls
server for an outgoing connector. The second was a mismatch between key and cert where the
error in the log simply says 'can't set credentials'. However I then added a printf to proton
where it logs to the transport and there was a much clearer and detailed message there. Would
be good to get all that detail through to the router log to speed up debugging of these sorts
of issues.

This message was sent by Atlassian JIRA

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

View raw message