[
https://issues.apache.org/jira/browse/PROTON-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329424#comment-14329424
]
ASF subversion and git services commented on PROTON-823:
--------------------------------------------------------
Commit aa53a6c00060695a974918bbd574ce555ca14636 in qpid-proton's branch
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=aa53a6c ]
PROTON-823: Fixed the openssl logging to respect the tracing flagsi
(as much as possible)
> Proton prints some log/trace information to stdout/stderr.
> ----------------------------------------------------------
>
> Key: PROTON-823
> URL: https://issues.apache.org/jira/browse/PROTON-823
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.9
> Reporter: Alan Conway
> Assignee: Andrew Stitcher
> Fix For: 0.9
>
>
> > Latest proton trunk seems to be dumping these to stdout or stderr, this
> > is from a proton reatactor based python client:
> >
> > [0x10d4a60]:error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake
> > failure
> >
> > Not sure where its coming from, thought you might know...
> from openssl.c in one of the ssl_log_...
> functions - They don't all seem to check for trace flags
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
