Re: QPID: Connection failed when connecting to remote QPIDD

2017-07-13 Thread Ken Giusti
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

RE: QPID: Connection failed when connecting to remote QPIDD

2017-07-12 Thread msingman
nabble.com] Sent: Wednesday, July 12, 2017 15:05 To: Matt Singman <matt.sing...@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? >

Re: QPID: Connection failed when connecting to remote QPIDD

2017-07-12 Thread Gordon Sim
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

Re: QPID: Connection failed when connecting to remote QPIDD

2017-07-12 Thread msingman
nectionOptions.cpp:140) Am I misreading the documentation in some way? -- View this message in context: http://qpid.2158936.n2.nabble.com/QPID-Connection-failed-when-connecting-to-remote-QPIDD-tp7664740p7664742.html Sent from the Apache Qpid

Re: QPID: Connection failed when connecting to remote QPIDD

2017-07-12 Thread Steve Huston
Everything is the same… except for the version of qpid ;-) It may be that the Ubuntu version doesn’t support AMQP 1.0 and that’s what ActiveMQ is asking for. Qpid is responding with 0-10. -Steve > On Jul 12, 2017, at 12:55 PM, Matt Singman wrote: > > I have a QPID

QPID: Connection failed when connecting to remote QPIDD

2017-07-12 Thread Matt Singman
I have a QPID daemon running inside of a Docker container. I have C++ code that should connect to this daemon, and in the past, it was able to, but it suddenly stopped being able to connect when the C++ code was run on the host machine. Trying to connect to the daemon on the container from the