qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robbie Gemmell <robbie.gemm...@gmail.com>
Subject Re: QPID Proton SASL header mismatch: 'AMQP\x01\x01\x00\x0a'
Date Mon, 27 May 2013 15:55:36 GMT
Hi Pablo,

Hopefully some others with knowledge of the C++ broker and Proton-C can
help further, but I did pick up on this in your logs:

qpidd:
2013-05-27 12:06:04 [System] debug RECV [127.0.0.1:5672-127.0.0.1:57656]:
INIT(1-0)
2013-05-27 12:06:04 [System] debug SENT [127.0.0.1:5672-127.0.0.1:57656]:
INIT(0-10)

That suggests to me that the broker is not actually configured to use AMQP
1.0 and so has replied with a supported protocol version (0-10) instead
once the client begun connecting.

Robbie

On 27 May 2013 11:36, Pablo Rodríguez Rey <mr@xkr.es> wrote:

> Hello to all members,
>
> My name is Pablo. I'm working in the IT area of the University of Murcia in
> Spain, and I've just seen the Proton project, and I'm testing it to use as
> standard message queue interprocess in our applications. This is my first
> approach to message queue services.
>
> I've compiled with no issues QPID 0.20 C & QPID Proton 0.4 and generated
> and installed the PHP module (cproton).
>
> Also, I'm using latest QPID 0.20 C server, running on Ubuntu 10.04.04 with
> trace option (-t).
>
> Running the C examples seems to work fine:
>
> qpidc-0.20/examples/messaging$ ./client
> Twas brillig, and the slithy toves -> TWAS BRILLIG, AND THE SLITHY TOVES
> Did gire and gymble in the wabe. -> DID GIRE AND GYMBLE IN THE WABE.
> All mimsy were the borogroves, -> ALL MIMSY WERE THE BOROGROVES,
> And the mome raths outgrabe. -> AND THE MOME RATHS OUTGRABE.
>
> qpidc-0.20/examples/messaging$ ./server
> Processed request: Twas brillig, and the slithy toves -> TWAS BRILLIG, AND
> THE SLITHY TOVES
> Processed request: Did gire and gymble in the wabe. -> DID GIRE AND GYMBLE
> IN THE WABE.
> Processed request: All mimsy were the borogroves, -> ALL MIMSY WERE THE
> BOROGROVES,
> Processed request: And the mome raths outgrabe. -> AND THE MOME RATHS
> OUTGRABE.
>
> When I run the Proton C or PHP examples it throws the following output:
>
> $ ./send
> [0x9fe5990:0] ERROR[-2] SASL header mismatch: 'AMQP\x01\x01\x00\x0a'
>
> $ php send.php
> [0x95ae5f0:0] ERROR[-2] SASL header mismatch: 'AMQP\x01\x01\x00\x0a'
>
> qpidd:
> 2013-05-27 12:06:04 [System] debug RECV [127.0.0.1:5672-127.0.0.1:57656]:
> INIT(1-0)
> 2013-05-27 12:06:04 [System] debug SENT [127.0.0.1:5672-127.0.0.1:57656]:
> INIT(0-10)
>
> Sorry if the question is dumb, but I searched all along the web and looked
> sources but I don't know what I'm doing wrong.
>
> If I stop the QPID C Server it works:
>
> qpid-proton-0.4/examples/messenger/php$ php send.php
> sent: Hello World!
>
> qpid-proton-0.4/examples/messenger/c$ ./recv
> Address: amqp://0.0.0.0
> Subject: Hello World!
> Content: "this is a test"
>
> Is QPID Proton a server-alone library? Does it not support any QPID C
> server thing I'm not counting on?
>
> Thanks in advance.
>
>
> --
> Pablo Rodríguez Rey (http://mr.xkr.es)
> Area de Tecnologías de la Información y las Comunicaciones Aplicadas
> Edificio ATICA ~ Sección de Redes ~ Despacho B1.2.004 ~ Tel. 868 88 8209
> Universidad de Murcia, 30100 Campus de Espinardo (Murcia - Spain)
> "i've mapped my mind on my dick"
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message