I figured out some of the issue, and I believe that it had to do with the client not finding the proper trust store. I am now getting the following with PN_TRACE_FRM=1:
[0x1d45e00]: -> AMQP [0x1d45e00]:0 -> @open(16) [container-id="dc8f96e5-4f0f-4944-8793-acec19793c40", hostname="127.0.0.1"] [0x1d45e00]:0 -> @begin(17) [next-outgoing-id=0, incoming-window=2147483647, outgoing-window=0] [0x1d45e00]:0 -> @attach(18) [name="topic://test", handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="topic://test", durable=0, timeout=0, dynamic=false], target=@target(41) [address="topic://test", durable=0, timeout=0, dynamic=false], initial-delivery-count=0] [0x1d45e00]:0 -> @flow(19) [incoming-window=2147483647, next-outgoing-id=0, outgoing-window=0, handle=0, delivery-count=0, link-credit=1024, drain=false] [0x1d45e00]:0 -> @close(24) [error=@error(29) [condition=:"amqp:connection:framing-error", description="SSL Failure: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed"]] [0x1d45e00]: <- EOS [0x1d45e00]: -> EOS Any thoughts as to what may be causing it? -- View this message in context: http://qpid.2158936.n2.nabble.com/Proton-c-SSL-Connection-tp7627249p7627367.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
