On 01/18/2013 07:21 PM, Paul O'Fallon wrote:
Sure, see the log data below. For context, I'm trying to write node.js bindings to qpid. Specifically, I'm after amqp1.0 support, which is why I started with proton directly (and its Messenger API). However, if I can bind to qpid::messaging and provide basic support for multiple versions of amqp (inc. 1.0) then that's even better. (However, given your earlier e-mail, there are likely subtle differences between proton's Messenger and qpid::messaging that I'm not yet aware of.)Here's the log data: ~/qpid-0.20/cpp/examples/messaging$ export QPID_LOG_ENABLE=trace+ ~/qpid-0.20/cpp/examples/messaging$ export QPID_LOAD_MODULE=/home/paul/qpid-0.20/cpp/src/amqpc.so ~/qpid-0.20/cpp/examples/messaging$ ./client myendpoint.servicebus.windows.net '{username: owner, password: mypass, protocol:amqp1.0}' 2013-01-18 14:05:12 [System] debug Exception constructed: Unsupported protocol: amqp1.0 terminate called after throwing an instance of 'qpid::Exception' what(): Unsupported protocol: amqp1.0 Aborted (core dumped)
Unfortunately this appears to be an issue with the cmake build on 0.20. Certain internal symbols which were hidden in http://svn.apache.org/viewvc?view=revision&revision=1406353 are needed by the AMQP 1.0 module.
Options are to either use the autoconf build (i.e. configure instead of cmake), or to apply the patch attached to https://issues.apache.org/jira/browse/QPID-4545.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
