You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by qhappiny <fw...@aim.com> on 2015/12/21 13:55:11 UTC
QPID JMS example cannot connect to the broker
Hi,
I am new to QPID, and thus I am doing the examples as instructed in the
file. I set up a broker using command qpidd --no-data-dir --auth=no, and
then I played with the examples in CPP and Python. All the examples in both
languages worked fine. However, when I tried to run the example with
JAVA(apache-qpid-jms-0.6.0), it returned an error with "Transport connection
remotely closes" message.
I noticed in the example instruction file saying that I need to have a Queue
named queue ready so to play with the example, and I created the queue with
command qpid-config add queue queue, but it still doesn't help.
Somebody please help me with it. Thanks a lot.
Best regards,
Stein
--
View this message in context: http://qpid.2158936.n2.nabble.com/QPID-JMS-example-cannot-connect-to-the-broker-tp7635535.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: QPID JMS example cannot connect to the broker
Posted by Gordon Sim <gs...@redhat.com>.
On 12/23/2015 11:52 AM, Stein Wang wrote:
> After multiple trials, I still didn't get the amqp.so module. I had to
> install another virtual machine to build the QPID broker from scratch again.
> This time, I was lucky. I got the amqp.so module, and the JMS example
> finally said Hello.
>
> I don't understand why there is difference between the results of the two
> installation processes as I was acting exactly the same procedures. I'd like
> to learn it if someone knows the reason.
I don't understand it either. The only criteria I can think of that
affects whether amqp.so is built or not is whether the proton library
could be found by cmake. In your case it reported it did find it.
If you want to dig deeper perhaps we could compare the console output of
a build that compiled amqp.so and one that did not(?)
> Thanks again for those who have helped me, and sorry for bothering with this
> entry-level question.
No need to apologies, its a fair question, just one that I'm unable to
answer at present, sorry!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: QPID JMS example cannot connect to the broker
Posted by Stein Wang <fw...@aim.com>.
After multiple trials, I still didn't get the amqp.so module. I had to
install another virtual machine to build the QPID broker from scratch again.
This time, I was lucky. I got the amqp.so module, and the JMS example
finally said Hello.
I don't understand why there is difference between the results of the two
installation processes as I was acting exactly the same procedures. I'd like
to learn it if someone knows the reason.
Thanks again for those who have helped me, and sorry for bothering with this
entry-level question.
Best regards,
Stein
--
View this message in context: http://qpid.2158936.n2.nabble.com/QPID-JMS-example-cannot-connect-to-the-broker-tp7635535p7635630.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: QPID JMS example cannot connect to the broker
Posted by Stein Wang <fw...@aim.com>.
Yes, there are a lot of .so libs under src folder, but not the amqp.so one, and the build was successful without error. I kind of get lost...
Anyway, thank you all for the help. I will try to install QPID on another platform today, and let's see if I can get it right. Will let you know about the results.
Regards,
Stein
> On Dec 21, 2015, at 11:35 PM, Gordon Sim <gs...@redhat.com> wrote:
>
>> On 12/21/2015 02:00 PM, Stein Wang wrote:
>> Thanks a lot, Gordon. :)
>>
>> I built the CPP broker myself, but there is no amqp.so under src folder. I
>> was using the proton 0.11, and it printed out a warning " Qpid proton 0.11.0
>> is not a tested version and might not be compatible, 0.9 is highest tested;
>> build may not work". Then I downloaded the 0.9 version, and the warning was
>> gone.
>
> As Robbie says, that shouldn't actually be a problem and if the build completed without errors it should certainly have built the amqp 1.0 module.
>
>> I just tried to reinstall the broker exactly as the instruction. When I ran
>> the cmake command, it said that "Qpid proton found, amqp 1.0 support
>> enabled", like this:
>>
>> -- Could NOT find SASL (missing: FOUND_SASL_LIB FOUND_SASL_H)
>> -- No need to generate AMQP protocol sources
>> -- No need to generate Qpid Management Framework sources
>> -- Boost version: 1.54.0
>> -- Found the following Boost libraries:
>> -- program_options
>> -- system
>> -- checking for module 'nss'
>> -- package 'nss' not found
>> --* Qpid proton found, amqp 1.0 support enabled*
>> -- Legacystore requires BerkeleyDB for C++ which is absent.
>> -- Legacystore is excluded from build.
>> -- Linearstore requires BerkeleyDB for C++ which is absent.
>> -- Linearstore is excluded from build.
>> -- Building Python bindings
>> -- Building Ruby bindings
>> -- Building Perl bindings
>> -- Build type is "RelWithDebInfo" (has debug symbols)
>> -- Configuring done
>> -- Generating done
>>
>> But again, after the "sudo make install" command, there is still no file
>> amqp.so under src folder, and JMS example could not work.
>
> Not sure why not... Do you have any '.so' libs under src? (this is src under build).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: QPID JMS example cannot connect to the broker
Posted by Gordon Sim <gs...@redhat.com>.
On 12/21/2015 02:00 PM, Stein Wang wrote:
> Thanks a lot, Gordon. :)
>
> I built the CPP broker myself, but there is no amqp.so under src folder. I
> was using the proton 0.11, and it printed out a warning " Qpid proton 0.11.0
> is not a tested version and might not be compatible, 0.9 is highest tested;
> build may not work". Then I downloaded the 0.9 version, and the warning was
> gone.
As Robbie says, that shouldn't actually be a problem and if the build
completed without errors it should certainly have built the amqp 1.0 module.
> I just tried to reinstall the broker exactly as the instruction. When I ran
> the cmake command, it said that "Qpid proton found, amqp 1.0 support
> enabled", like this:
>
> -- Could NOT find SASL (missing: FOUND_SASL_LIB FOUND_SASL_H)
> -- No need to generate AMQP protocol sources
> -- No need to generate Qpid Management Framework sources
> -- Boost version: 1.54.0
> -- Found the following Boost libraries:
> -- program_options
> -- system
> -- checking for module 'nss'
> -- package 'nss' not found
> --* Qpid proton found, amqp 1.0 support enabled*
> -- Legacystore requires BerkeleyDB for C++ which is absent.
> -- Legacystore is excluded from build.
> -- Linearstore requires BerkeleyDB for C++ which is absent.
> -- Linearstore is excluded from build.
> -- Building Python bindings
> -- Building Ruby bindings
> -- Building Perl bindings
> -- Build type is "RelWithDebInfo" (has debug symbols)
> -- Configuring done
> -- Generating done
>
> But again, after the "sudo make install" command, there is still no file
> amqp.so under src folder, and JMS example could not work.
Not sure why not... Do you have any '.so' libs under src? (this is src
under build).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: QPID JMS example cannot connect to the broker
Posted by Robbie Gemmell <ro...@gmail.com>.
The message is just an advisory, the result of the qpid-cpp 0.34
release being older, with Proton 0.11 not having been released until
months later. I'm not aware of any particular issue using those
versions together and have done so a number of times, typically while
running the JMS client examples.
I'm not sure on why the module wouldnt be built if it is finding
proton, I'll need to defer to folks familiar with those bits.
Robbie
On 21 December 2015 at 14:00, Stein Wang <fw...@aim.com> wrote:
> Thanks a lot, Gordon. :)
>
> I built the CPP broker myself, but there is no amqp.so under src folder. I
> was using the proton 0.11, and it printed out a warning " Qpid proton 0.11.0
> is not a tested version and might not be compatible, 0.9 is highest tested;
> build may not work". Then I downloaded the 0.9 version, and the warning was
> gone.
>
> I just tried to reinstall the broker exactly as the instruction. When I ran
> the cmake command, it said that "Qpid proton found, amqp 1.0 support
> enabled", like this:
>
> -- Could NOT find SASL (missing: FOUND_SASL_LIB FOUND_SASL_H)
> -- No need to generate AMQP protocol sources
> -- No need to generate Qpid Management Framework sources
> -- Boost version: 1.54.0
> -- Found the following Boost libraries:
> -- program_options
> -- system
> -- checking for module 'nss'
> -- package 'nss' not found
> --* Qpid proton found, amqp 1.0 support enabled*
> -- Legacystore requires BerkeleyDB for C++ which is absent.
> -- Legacystore is excluded from build.
> -- Linearstore requires BerkeleyDB for C++ which is absent.
> -- Linearstore is excluded from build.
> -- Building Python bindings
> -- Building Ruby bindings
> -- Building Perl bindings
> -- Build type is "RelWithDebInfo" (has debug symbols)
> -- Configuring done
> -- Generating done
>
> But again, after the "sudo make install" command, there is still no file
> amqp.so under src folder, and JMS example could not work.
>
>
>
> --
> View this message in context: http://qpid.2158936.n2.nabble.com/QPID-JMS-example-cannot-connect-to-the-broker-tp7635535p7635544.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: QPID JMS example cannot connect to the broker
Posted by Stein Wang <fw...@aim.com>.
Thanks a lot, Gordon. :)
I built the CPP broker myself, but there is no amqp.so under src folder. I
was using the proton 0.11, and it printed out a warning " Qpid proton 0.11.0
is not a tested version and might not be compatible, 0.9 is highest tested;
build may not work". Then I downloaded the 0.9 version, and the warning was
gone.
I just tried to reinstall the broker exactly as the instruction. When I ran
the cmake command, it said that "Qpid proton found, amqp 1.0 support
enabled", like this:
-- Could NOT find SASL (missing: FOUND_SASL_LIB FOUND_SASL_H)
-- No need to generate AMQP protocol sources
-- No need to generate Qpid Management Framework sources
-- Boost version: 1.54.0
-- Found the following Boost libraries:
-- program_options
-- system
-- checking for module 'nss'
-- package 'nss' not found
--* Qpid proton found, amqp 1.0 support enabled*
-- Legacystore requires BerkeleyDB for C++ which is absent.
-- Legacystore is excluded from build.
-- Linearstore requires BerkeleyDB for C++ which is absent.
-- Linearstore is excluded from build.
-- Building Python bindings
-- Building Ruby bindings
-- Building Perl bindings
-- Build type is "RelWithDebInfo" (has debug symbols)
-- Configuring done
-- Generating done
But again, after the "sudo make install" command, there is still no file
amqp.so under src folder, and JMS example could not work.
--
View this message in context: http://qpid.2158936.n2.nabble.com/QPID-JMS-example-cannot-connect-to-the-broker-tp7635535p7635544.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: QPID JMS example cannot connect to the broker
Posted by Gordon Sim <gs...@redhat.com>.
On 12/21/2015 12:55 PM, qhappiny wrote:
> I am new to QPID, and thus I am doing the examples as instructed in the
> file. I set up a broker using command qpidd --no-data-dir --auth=no, and
> then I played with the examples in CPP and Python. All the examples in both
> languages worked fine. However, when I tried to run the example with
> JAVA(apache-qpid-jms-0.6.0), it returned an error with "Transport connection
> remotely closes" message.
You need to load the AMQP 1.0 support for the broker, if it is not
loaded by default. If you are running a broker you built yourself, from
the build directory, then you need to add --load-module ./src/amqp.so.
(If you install the broker then the module is added to the default
modules directory and so should be loaded by default.
If you don't have an amqp.so then your system couldn't find proton when
running cmake and 1.0 support (which relies on proton) could not be built.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org