Thanks for the replies! Steve, I agree with you that the error message is ambiguous. I checked cpp/src/qpid/client/TCPConnector.cpp and it looks like the first version mentioned in the error message (1-0) is the one returned by the server and the second (0-10) is the one being attempted by the client. This matches my own experience, since I can connect and send/receive messages via proton directly.
Ken, I tried setting that environment variable to point to my proton library (/usr/lib/libqpid-proton.so) but still get the same errors (both with and without specifying the protocol on the command line). - Paul On Wed, Jan 16, 2013 at 10:07 AM, Steve Huston <[email protected]> wrote: > Hmmm... re-reading the error message seems to imply that your client is > speaking 1-0 and Azure only knows 0-10. Could that be? > > > -----Original Message----- > > From: Paul O'Fallon [mailto:[email protected]] > > Sent: Tuesday, January 15, 2013 6:48 PM > > To: [email protected] > > Subject: Re: Activating amqp 1.0 / proton in C++ messaging example > > > > Thanks for the reply! I have not run the broker -- I'm trying to use the > > example command line client to connect to Azure Service Bus (via amqp > 1.0). > > When I run this command: > > > > ~/qpid-0.20/cpp/examples/messaging$ ./client > > myendpoint.servicebus.windows.net '{username: owner, password: > > mypass}' > > > > I get this error response: > > > > [System] error Caught exception in state: 3 with event: 1: Unsupported > > version: 1-0 supported version 0-10 > > > > From reading this prior list e-mail (http://bit.ly/TZ6HQM) I assumed I > needed > > to add a "protocol" element to my connection options, so I tried > > this: > > > > ~/qpid-0.20/cpp/examples/messaging$ ./client > > myendpoint.servicebus.windows.net '{username: owner, password: > > mypass, > > protocol: amqp1.0}' > > > > which gives this error response > > > > terminate called after throwing an instance of 'qpid::Exception' > > what(): Unsupported protocol: amqp1.0 > > > > To your point, I assumed that this extra connection option is what would > > trigger the loading of the proton module. I've connected to this > endpoint via > > the proton C library directly, so I know it works, but I don't know how > to tell > > the C++ Qpid library to use proton in this example. > > > > Thanks again, > > Paul > > > > > > On Tue, Jan 15, 2013 at 5:26 PM, Steve Huston <[email protected]> > > wrote: > > > > > Hi Paul, > > > > > > When you built Qpid 0.20-rc4 and started the broker (I assume that's > > > the broker you ran; let me know if this is not true) did you load the > > > proton module explicitly? Although the build system found it and built > > > it, my understanding is that it's built as a loadable module, not > > > built into the broker proper. > > > > > > -Steve > > > > > > > -----Original Message----- > > > > From: Paul O'Fallon [mailto:[email protected]] > > > > Sent: Tuesday, January 15, 2013 5:14 PM > > > > To: [email protected] > > > > Subject: Activating amqp 1.0 / proton in C++ messaging example > > > > > > > > Hello. I've had proton installed for a while, coding directly > > > > against > > > it's C API > > > > (connecting to Azure ServiceBus). Now I want to connect via c++ > > > > through Qpid itself. I've built Qpid 0.20-rc4 and the build output > > > > indicates > > > that it > > > > *does* find the proton libraries and that amqp 1.0 support is > enabled. > > > > > > > > When I run the "client" c++ example (in cpp/examples/messaging) > > > > without specifying a protocol option, I get "error Caught exception > > > > in state: 3 > > > with > > > > event: 1: Unsupported version: 1-0 supported version 0-10" (i.e. > > > > it's > > > trying > > > > amqp 0.10 and not 1.0). However, when I add the connection option > > > > "protocol: amqp1.0" I get an error stating that this is an > > > > "Unsupported protocol". > > > > > > > > Is there a different connection option I need to use to trigger the > > > > use > > > of the > > > > proton library / amqp 1.0? > > > > > > > > Thanks! > > > > > > > > - Paul > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] For > > > additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
