Interestingly, the c++ client (specifically the helloworld) does not
connect to the Java broker.
I added this line to my .bash_profile
export QPID_LOG_ENABLE=trace+:amqp_0_10
and I turned up the logging on the java broker as Oleksandr Rudyy
("Alex") had suggested.
There is no additional logging activity in the java broker console,
nor is there any log files generated that I noticed.
When I run the c++ client helloworld on the, I only see this:
[sean@fedora16 messaging]$ ./hello_world
Failed to connect (reconnect disabled)
I ran the spout and drain (c++ client) as Alex had suggested, and they
worked with the java broker. (interesting).
[sean@fedora16 messaging]$ ./spout -c 1 -b guest/guest@localhost
--connection-options {sasl-mechanism:PLAIN} queue
[sean@fedora16 messaging]$ ./drain -c 1 -b guest/guest@localhost
--connection-options {sasl-mechanism:PLAIN} queue
Message(properties={spout-id:74c4541b-f57b-44ec-b229-9300b4c972c8:0,
x-amqp-0-10.routing-key:queue}, content='')
On Sun, Oct 28, 2012 at 11:57 PM, Gordon Sim <g...@redhat.com> wrote:
> On 10/26/2012 11:00 AM, Rob Godfrey wrote:
>>
>> OK... I think I know what the problem is now - the machine on which
>> you built the C++ client almost certainly doesn't have the SASL
>> libraries installed.
>>
>> When I build on a CentOS machine without SASL installed then I see
>> exactly the issue you are reporting.
>
>
> Can you get a protocol trace for that (e.g. set
> QPID_LOG_ENABLE=trace+:amqp_0_10 on the client)?
>
> The cyrus integration is supposed to be optional and if not available a
> default implementation that supports only ANONYMOUS and PLAIN *should* be
> built in.
>
> You can explicitly control the SASL mechanism used through the connection
> options e.g. --connection-options '{sasl_mechanisms:PLAIN}'.
>
> (You can if desired also specify the username and password in the connection
> options instead of in the URL e.g. --connection-options
> '{sasl_mechanisms:PLAIN,username:guest,password:guest}')
>
>
>> If I install the SASL libraries and rebuild the C++ client then it all
>> works fine
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
