RE: ServiceBus and Proton-C 0.12 IOP Issue

2016-02-27 Thread Randy Armstrong
Issue On 26 February 2016 at 12:46, Robbie Gemmell wrote: > On 25 February 2016 at 23:18, Randy Armstrong > wrote: >> I think it is related to proton because the exact same messages using the >> exact same credentials are processed by an AMQPlite client running at the >> s

RE: ServiceBus and Proton-C 0.12 IOP Issue

2016-02-25 Thread Randy Armstrong
be related to an ACK for the message? -Original Message- From: Andrew Stitcher [mailto:astitc...@redhat.com] Sent: Thursday, February 25, 2016 2:51 PM To: users@qpid.apache.org Subject: Re: ServiceBus and Proton-C 0.12 IOP Issue On Thu, 2016-02-25 at 14:26 -0800, Randy Armstrong wrote:

RE: ServiceBus and Proton-C 0.12 IOP Issue

2016-02-25 Thread Randy Armstrong
eir same use in AMQPLite. Perhaps there is some quoting problem providing the url to messenger (from the command line?). Or possibly the url encoded service bus key is being parsed incorrectly by Proton. You could try creating your own pn_url_t (see url.h) from the url you are using with pn

ServiceBus and Proton-C 0.12 IOP Issue

2016-02-25 Thread Randy Armstrong
I am using the "recv" example from the 0.12 codebase. The URL I am using is: amqps://receiver:@opcfoundation-prototyping.servicebus.windows.net/MyTopic/Subscriptions/ default" I have tried with pn_messenger_set_flags(messenger, PN_FLAGS_ALLOW_INSECURE_MECHS); and pn_messenger_set_flags