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)
Thanks for your help!
- Paul
On Fri, Jan 18, 2013 at 4:05 AM, Gordon Sim <[email protected]> wrote:
> On 01/17/2013 10:34 PM, Paul O'Fallon wrote:
>
>> If it helps, here's the debug log output for both scenarios (not
>> supplying,
>> and then supplying, the protocol connection option):
>>
>
> Not supplying it will always result in the default - i.e. 0-10 - being
> used. The error when supplying it is due to the module not being properly
> loaded, i.e. due to QPID_LOAD_MODULE not being set. Could you send a log
> with QPID_LOG_ENABLE=trace+, where QPID_LOAD_MODULE is set and the protocol
> option is also specified?
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> [email protected].**org<[email protected]>
> For additional commands, e-mail: [email protected]
>
>
