qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From msingman <matt.sing...@indepth.com>
Subject RE: QPID: Connection failed when connecting to remote QPIDD
Date Wed, 12 Jul 2017 19:18:33 GMT
It was related to the qpidc.conf file in /etc/qpid. I must have uncommented that for some reason
and not noticed that it broke what I was trying to do.

Just for reference, the uncommented line was "protocol-defaults=amqp1.0,amqp0-10", so I also
don't know why it didn't try 0-10 after failing with 1.0

To prevent other people from having problems of this kind, are there any plans to update the
version of QPID on Ubuntu's repository? It's pretty heavily out of date from what I can see.

Thanks again for the help...

From: Gordon Sim [via Qpid] [mailto:ml+s2158936n7664743h63@n2.nabble.com]
Sent: Wednesday, July 12, 2017 15:05
To: Matt Singman <matt.singman@indepth.com>
Subject: Re: QPID: Connection failed when connecting to remote QPIDD

On 12/07/17 18:44, msingman wrote:

> Does the "INIT(0-0)" indicate that the message sender wants to use AMQP 1.0?
> Assuming that is the case, how can I get the C++ code I have to use 0-10
> (for what it's worth, qpid::messaging is being used)?
>
> On the documentation for QPID 1.36.0 (which is the version that is used on
> the host machine, not the container;
> http://qpid.apache.org/releases/qpid-cpp-1.36.0/messaging-api/book/connections.html#connection-options
> ), it states in Table 1.4 that 0-10 is the default version that is used.
> Further, when I attempt to manually set the protocol
> ("connection.setOption("protocol", "amqp0-10");"), the code compiles but I
> get the following runtime error:
>
> terminate called after throwing an instance of
> 'qpid::messaging::MessagingException'
>    what():  Invalid option: protocol not recognised
> (/builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/messaging/ConnectionOptions.cpp:140)
>
> Am I misreading the documentation in some way?

No, but it appears that the protocol option can only be set when
creating the connection, e.g. Connection("myhost",
"{protocol:amqp0-10}"). (qpid-send and qpid-receive take a
connection-options argument e.g. qpid-send --connection-options
'{protocol:amqp0-10}' --address foo etc).

The order the protocols are tried in can be controlled in the qpidc.conf
file or via QPID_PROTOCOLS env var. The default is actually to try 0-10
first, then 1.0, so I suspect in your environment the conf file entry to
reverse that is uncommented.

The 0.16 broker doesn't have 1.0 support. I can't quite understand why
the client is not retrying with 0-10 though.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=7664743&i=0>
For additional commands, e-mail: [hidden email]</user/SendEmail.jtp?type=node&node=7664743&i=1>


________________________________
If you reply to this email, your message will be added to the discussion below:
http://qpid.2158936.n2.nabble.com/QPID-Connection-failed-when-connecting-to-remote-QPIDD-tp7664740p7664743.html
To unsubscribe from QPID: Connection failed when connecting to remote QPIDD, click here<http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7664740&code=bWF0dC5zaW5nbWFuQGluZGVwdGguY29tfDc2NjQ3NDB8NTQ0MjMwNzQ2>.
NAML<http://qpid.2158936.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: http://qpid.2158936.n2.nabble.com/QPID-Connection-failed-when-connecting-to-remote-QPIDD-tp7664740p7664744.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message