I looked at it briefly, but it seemed more complicated than what I needed. I only need to send messages to the queue; I don't need to read it or deal with sessions. The send.c example worked with ServiceBus in 0.6, so I am not sure if this is an intentional or unintentional change in behavior.
Trying the same same thing with 0.7 causes send to hang indefinitely. It seems related to parsing of the address. The secret (aka password) for the queue often contains a forward slash, which appears to have an effect. Using a secret that doesnt contain a slash works, but without a slash does not. Looking at the history, commit c95c986 changed with url parsing function, and looks like it might be related. Thoughts? Sent from Outlook<http://aka.ms/weboutlook> ________________________________ From: Andrew Stitcher <[email protected]> Sent: Monday, April 24, 2017 8:13:50 PM To: [email protected] Subject: Re: Using proton-c with Azure ServiceBus Queues On Tue, 2017-04-25 at 00:56 +0000, Ryan Sizemore wrote: > Hi, > > > I am trying to get proton-c working with Azure ServiceBus, but the > latest builds of qpid-proton seem to silently fail (or fail to parse > the address) without the message ever being sent to the queue. Before > I dig too much, is there any guidance out there for working with > ServiceBus? Perhaps I am making an obvious mistake somewhere. > > > Previously, I was using qpid-proton-0.6 (old, I know), and this looks > to be the last version of proton before things stopped working. I am > using the sample program under /examples/messenger/c/send.c, and when > I run that, it sends correctly to the queue. However, other builds > fail (0.17 and 0.16 don't work for sure). Have you tried the servicebus example in examples/cpp/service_bus.cpp? You may have better luck with that. Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
