You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Rob Godfrey <ro...@gmail.com> on 2013/05/27 19:06:42 UTC
Re: QPID Proton SASL header mismatch: 'AMQP\x01\x01\x00\x0a'
Since this looks like an issue you are having with the Qpid C++ broker
rather than Proton per se, it's probably worth cross-possting this to the
Qpid User list
-- Rob
On 27 May 2013 18:11, Pablo Rodríguez Rey <mr...@xkr.es> wrote:
> Thanks Robbie Gemmel, that's what I suspected.
>
> I've found the problem thanks to a bug reported and fixed by Gordon Sim,
> AMQP 1.0 is not enabled and compiled by default:
>
> https://issues.apache.org/jira/browse/QPID-4545
>
> But I applied the patch and stills not work. Also found this thread:
>
>
> http://mail-archives.apache.org/mod_mbox/qpid-users/201301.mbox/%3C510A9A15.4000008@redhat.com%3E
>
> I compile it again but no amqpc.so is generated from anywhere to load as
> module.
>
> Also i tested using libqpid-proton.so as module, it works but nothing
> happens:
>
> ./qpidd --load-module libqpid-proton.so --data-dir /var/qpid
>
> I think Im not doing anything well to generate this module, so any help
> will be appreciated.
>
> Thanks again.
>
>
> On Mon, May 27, 2013 at 5:55 PM, Robbie Gemmell <robbie.gemmell@gmail.com
> >wrote:
>
> > 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"
> > >
> >
>
>
>
> --
> 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"
>
Re: QPID Proton SASL header mismatch: 'AMQP\x01\x01\x00\x0a'
Posted by Pablo Rodríguez Rey <mr...@xkr.es>.
Hello again,
I'm sorry for asking, but at the moment I was not able to compile qpidd
with AMQP 1.0 support, so I will resume all steps I'm doing for asking what
I'm missing.
I'm now using qpid-0.22, and I do this:
*$ export PROTON_CFLAGS=/usr/include/proton/
$ export PROTON_LIBS=/usr/lib/
$ ./configure --with-proton*
...
checking for PROTON... yes
...
And all is fine. Then:
*$ cmake .*
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- No AMQP spec... presume generated sources are included
-- Can't locate the help2man command; man pages will not be generated
-- *Qpid proton not found*, amqp 1.0 support not enabled
-- Legacystore is excluded from build.
-- lookign for config.h
-- Could NOT find Ruby (missing: RUBY_INCLUDE_DIR RUBY_LIBRARY)
-- Could NOT find PythonLibs (missing: PYTHON_LIBRARIES
PYTHON_INCLUDE_DIRS)
-- Could NOT find PerlLibs (missing: PERL_LIBRARY)
-- Configuring done
-- Generating done
-- Build files have been written to: /home/produccion/qpid/qpidc-0.22
If I check CMakeCache.txt, there is no AMQP support.
*$ grep "BUILD_AMQP" CMakeCache.txt*
BUILD_AMQP:BOOL=OFF
Then *make* and it compiles and works fine, but AMQP 1.0 is not enabled,
what I'm missing to enable it?
Thanks, and sorry for asking compiling basics, but it is beyond my
knowledge limits.
On Mon, May 27, 2013 at 7:19 PM, Gordon Sim <gs...@redhat.com> wrote:
> On 05/27/2013 06:06 PM, Rob Godfrey wrote:
>
>> Since this looks like an issue you are having with the Qpid C++ broker
>> rather than Proton per se, it's probably worth cross-possting this to the
>> Qpid User list
>>
>
>
>
> On 27 May 2013 18:11, Pablo Rodríguez Rey <mr...@xkr.es> wrote:
>>
>> Thanks Robbie Gemmel, that's what I suspected.
>>>
>>> I've found the problem thanks to a bug reported and fixed by Gordon Sim,
>>> AMQP 1.0 is not enabled and compiled by default:
>>>
>>> https://issues.apache.org/**jira/browse/QPID-4545<https://issues.apache.org/jira/browse/QPID-4545>
>>>
>>> But I applied the patch and stills not work. Also found this thread:
>>>
>>>
>>> http://mail-archives.apache.**org/mod_mbox/qpid-users/**
>>> 201301.mbox/%3C510A9A15.**4000008@redhat.com%3E<http://mail-archives.apache.org/mod_mbox/qpid-users/201301.mbox/%3C510A9A15.4000008@redhat.com%3E>
>>>
>>> I compile it again but no amqpc.so is generated from anywhere to load as
>>> module.
>>>
>>> Also i tested using libqpid-proton.so as module, it works but nothing
>>> happens:
>>>
>>> ./qpidd --load-module libqpid-proton.so --data-dir /var/qpid
>>>
>>
> The module for AMQP 1.0 support for the broker (i.e. qpidd) is amqp.so
> (amqpc.so is the module for adding AMQP 1.0 support to the c++
> implementation of the qpid::messaging API).
>
> I.e. you want: qpidd --load-module /path/to/amqp.so
>
> If you are using the cmake based build, the modules should be under src in
> the build tree. If they are not, that suggests that the proton dependency
> was not found. You should see something in the cmake output about that and
> yourCMakeCache.txt should contain something like:
>
> //Build with support for AMQP 1.0
> BUILD_AMQP:BOOL=ON
>
> If you are using the autoconf based build then you need to specify
> --with-proton to enable compilation of the 1.0 components (they will then
> be found in src/.libs in the build tree).
>
>
> I think Im not doing anything well to generate this module, so any help
>>> will be appreciated.
>>>
>>> Thanks again.
>>>
>>>
>>> On Mon, May 27, 2013 at 5:55 PM, Robbie Gemmell <
>>> robbie.gemmell@gmail.com
>>>
>>>> wrote:
>>>>
>>>
>>> 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 <http://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 <http://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"
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> 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"
>>>
>>>
>>
>
--
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"
Re: QPID Proton SASL header mismatch: 'AMQP\x01\x01\x00\x0a'
Posted by Gordon Sim <gs...@redhat.com>.
On 05/27/2013 06:06 PM, Rob Godfrey wrote:
> Since this looks like an issue you are having with the Qpid C++ broker
> rather than Proton per se, it's probably worth cross-possting this to the
> Qpid User list
> On 27 May 2013 18:11, Pablo Rodríguez Rey <mr...@xkr.es> wrote:
>
>> Thanks Robbie Gemmel, that's what I suspected.
>>
>> I've found the problem thanks to a bug reported and fixed by Gordon Sim,
>> AMQP 1.0 is not enabled and compiled by default:
>>
>> https://issues.apache.org/jira/browse/QPID-4545
>>
>> But I applied the patch and stills not work. Also found this thread:
>>
>>
>> http://mail-archives.apache.org/mod_mbox/qpid-users/201301.mbox/%3C510A9A15.4000008@redhat.com%3E
>>
>> I compile it again but no amqpc.so is generated from anywhere to load as
>> module.
>>
>> Also i tested using libqpid-proton.so as module, it works but nothing
>> happens:
>>
>> ./qpidd --load-module libqpid-proton.so --data-dir /var/qpid
The module for AMQP 1.0 support for the broker (i.e. qpidd) is amqp.so
(amqpc.so is the module for adding AMQP 1.0 support to the c++
implementation of the qpid::messaging API).
I.e. you want: qpidd --load-module /path/to/amqp.so
If you are using the cmake based build, the modules should be under src
in the build tree. If they are not, that suggests that the proton
dependency was not found. You should see something in the cmake output
about that and yourCMakeCache.txt should contain something like:
//Build with support for AMQP 1.0
BUILD_AMQP:BOOL=ON
If you are using the autoconf based build then you need to specify
--with-proton to enable compilation of the 1.0 components (they will
then be found in src/.libs in the build tree).
>> I think Im not doing anything well to generate this module, so any help
>> will be appreciated.
>>
>> Thanks again.
>>
>>
>> On Mon, May 27, 2013 at 5:55 PM, Robbie Gemmell <robbie.gemmell@gmail.com
>>> wrote:
>>
>>> 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"
>>>>
>>>
>>
>>
>>
>> --
>> 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"
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: QPID Proton SASL header mismatch: 'AMQP\x01\x01\x00\x0a'
Posted by Gordon Sim <gs...@redhat.com>.
On 05/27/2013 06:06 PM, Rob Godfrey wrote:
> Since this looks like an issue you are having with the Qpid C++ broker
> rather than Proton per se, it's probably worth cross-possting this to the
> Qpid User list
> On 27 May 2013 18:11, Pablo Rodríguez Rey <mr...@xkr.es> wrote:
>
>> Thanks Robbie Gemmel, that's what I suspected.
>>
>> I've found the problem thanks to a bug reported and fixed by Gordon Sim,
>> AMQP 1.0 is not enabled and compiled by default:
>>
>> https://issues.apache.org/jira/browse/QPID-4545
>>
>> But I applied the patch and stills not work. Also found this thread:
>>
>>
>> http://mail-archives.apache.org/mod_mbox/qpid-users/201301.mbox/%3C510A9A15.4000008@redhat.com%3E
>>
>> I compile it again but no amqpc.so is generated from anywhere to load as
>> module.
>>
>> Also i tested using libqpid-proton.so as module, it works but nothing
>> happens:
>>
>> ./qpidd --load-module libqpid-proton.so --data-dir /var/qpid
The module for AMQP 1.0 support for the broker (i.e. qpidd) is amqp.so
(amqpc.so is the module for adding AMQP 1.0 support to the c++
implementation of the qpid::messaging API).
I.e. you want: qpidd --load-module /path/to/amqp.so
If you are using the cmake based build, the modules should be under src
in the build tree. If they are not, that suggests that the proton
dependency was not found. You should see something in the cmake output
about that and yourCMakeCache.txt should contain something like:
//Build with support for AMQP 1.0
BUILD_AMQP:BOOL=ON
If you are using the autoconf based build then you need to specify
--with-proton to enable compilation of the 1.0 components (they will
then be found in src/.libs in the build tree).
>> I think Im not doing anything well to generate this module, so any help
>> will be appreciated.
>>
>> Thanks again.
>>
>>
>> On Mon, May 27, 2013 at 5:55 PM, Robbie Gemmell <robbie.gemmell@gmail.com
>>> wrote:
>>
>>> 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"
>>>>
>>>
>>
>>
>>
>> --
>> 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"
>>
>