On Qui, 2013-05-23 at 16:33 +0100, Gordon Sim wrote:
> On 05/23/2013 04:24 PM, Bruno Matos wrote:
> > On Qui, 2013-05-23 at 15:45 +0100, Gordon Sim wrote:
> >> On 05/23/2013 02:23 PM, Bruno Matos wrote:
> >>> Yes, I'm using 0.22 RC3 with the patch from revision 1485467.
> >>> I've created the domain like this
> >>>
> >>> ./qpid-ctrl create type=domain name=my-domain
> >>> properties="{'url':'B','sasl_mechanisms':'PLAIN','username':'someuser','password':'somepass'}"
> >>> -b someuser/somepass@A
> >>>
> >>> Created a queue on B with name 'queue2'.
> >>>
> >>> Then I send a message to queue2@my-domain to broker A and it complains:
> >>>
> >>> Exception received from broker: not-found: not-found: Queue not found:
> >>> queue2@my-domain
> >>
> >> Is the sender created on a 1.0 connection? (This does not at present
> >> work for 0-10).
> >>
> >
> > No the sender is using 0-10. The only way to use 1.0 is using proton?
>
> The 1.0 support in qpid::messaging relies on proton, yes. But presumably
> you have that already since the domain stuff is only available with 1.0
> also.
>
> You can still use the qpid::messaging API though. You just need to load
> the amqpc.so lib on the client and specify 'protocol:amqp1.0' in the
> connection-options.
>
With the module loaded and 1.0 selected, something goes wrong again in
the handshake, maybe a miss configuration. SASL it's complaining about
no mechanisms available. I'll take a closer look.
In attachment are the client logs, if you want to take a look.
Thank you.
--
Bruno Matos
2013-05-24 16:24:02 [Messaging] debug Driver started
2013-05-24 16:24:02 [Messaging] debug mymachine:5672 Connecting ...
2013-05-24 16:24:02 [System] info Connecting: [::1]:5672
2013-05-24 16:24:02 [Messaging] debug mymachine:5672 Connected
2013-05-24 16:24:02 [Messaging] debug wakeupDriver()
2013-05-24 16:24:02 [Messaging] debug mymachine:5672 Waiting to be authenticated...
2013-05-24 16:24:02 [Security] trace mymachine:5672 Sasl::canEncode(): 1 || 0
2013-05-24 16:24:02 [Security] trace mymachine:5672 Sasl::canEncode(): 1 || 0
2013-05-24 16:24:02 [Protocol] debug mymachine:5672 writing protocol header: 1-0
2013-05-24 16:24:02 [Security] trace mymachine:5672 Sasl::encode(65535): 8
2013-05-24 16:24:02 [Security] trace mymachine:5672 Sasl::canEncode(): 0 || 0
2013-05-24 16:24:11 [Protocol] debug mymachine:5672 read protocol header: 1-0
2013-05-24 16:24:11 [Security] trace Reading SASL frame of size 27
2013-05-24 16:24:11 [Security] trace Reading SASL-MECHANISMS
2013-05-24 16:24:11 [Protocol] debug mymachine:5672 Received SASL-MECHANISMS(PLAIN)
2013-05-24 16:24:11 [Security] debug CyrusSasl::start(PLAIN)
2013-05-24 16:24:11 [Security] debug min_ssf: 0, max_ssf: 256
2013-05-24 16:24:11 [System] debug Exception constructed: Sasl error: SASL(-4): no mechanism available: No worthy mechs found (/tmp/qpid/qpidc-0.22/src/qpid/SaslFactory.cpp:311)
2013-05-24 16:24:11 [System] error Caught exception in state: 3 with event: 1: internal-error: Sasl error: SASL(-4): no mechanism available: No worthy mechs found (/tmp/qpid/qpidc-0.22/src/qpid/SaslFactory.cpp:311)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
