Gordon Sim created PROTON-924:
-
Summary: links are not uniquely named by messenger
Key: PROTON-924
URL: https://issues.apache.org/jira/browse/PROTON-924
Project: Qpid Proton
Issue Type: Bug
Gordon Sim created PROTON-925:
-
Summary: proton-c seems to treat unspecified channel-max as
implying 0
Key: PROTON-925
URL: https://issues.apache.org/jira/browse/PROTON-925
Project: Qpid Proton
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]
Chuck Rolke created PROTON-926:
--
Summary: [proton-c windows] Create all binary executables in
build/proton-c folder
Key: PROTON-926
URL: https://issues.apache.org/jira/browse/PROTON-926
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14606267#comment-14606267
]
ASF subversion and git services commented on PROTON-922:
Commit
Greetings,
I just wanted to give a heads up for the python folks in the community
(including me) on this[0]. It'd be great if we could have an amqp1.0
transport for kombu.
I might take a look at this but, since I currently don't have the time
for it, I thought that maybe one of you did. :)
It seems like your client is not able to verify the server certificate against
your trust store. I had this kind of problems using proton-j the last days, but
this had to do with client authentication with a certificate.
You could try to use openssl to check that, e.g. openssl verify -CAfile
