Re: Qpid AMQP 1.0 - How does it all hang together? - was Re: Qpid Dispatch Router component

2013-10-10 Thread Rob Godfrey
This is an excellent post which I think highlights the need for us to properly define the scopes of our current components, their roadmaps, and the vision we have for Qpid and AMQP 1.0. I know some people have already replied in thread, but would it seem like a good idea if we used these

Re: Qpid Dispatch Router component

2013-10-10 Thread Gordon Sim
On 10/10/2013 09:38 AM, Rob Godfrey wrote: My main concern is that I believe that Qpid should be primarily directed at implementing AMQP standards, and building resuable toolkits and components that fit into any AMQP network. I'd be very concerned if we were inventing alternative management

Re: Qpid Dispatch Router component

2013-10-10 Thread Rob Godfrey
On 10 October 2013 12:46, Gordon Sim g...@redhat.com wrote: On 10/10/2013 10:58 AM, Rob Godfrey wrote: I think the point of Qpid (vs. any other messaging implementation at Apache or elsewhere) is to implement the AMQP specification. I have no disagreement when the AMQP specification is

RE: Unable to connect to broker via Qpid JMS-over-AMQP client

2013-10-10 Thread Branden Smith
Makes sense; thank you for your help. Branden -Original Message- From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com] Sent: Wednesday 2013.10.09 17:43 To: users@qpid.apache.org Subject: Re: Unable to connect to broker via Qpid JMS-over-AMQP client The 1.0 client has no built in

Coaxing an error message out of qpid-cpp - unable to connect

2013-10-10 Thread Graham Leggett
Hi all, I am currently trying to swap in qpid-cpp v0.18 to replace an unreliable activemq server installation. The connection is protected with client certificates. When the client tries the connect, the qpid-client v0.24 reports a java.net.SocketException: Broken pipe and then hangs solid,

Re: Coaxing an error message out of qpid-cpp - unable to connect

2013-10-10 Thread Gordon Sim
On 10/10/2013 05:08 PM, Graham Leggett wrote: More investigation has shown that someone had hard coded the qpid ampq v1.0 driver directly into the code, which was taking precedence. With that removed we're now getting further, but still not out of the woods: javax.jms.JMSException: Failed to

Re: Qpid Dispatch Router component

2013-10-10 Thread Ted Ross
On 10/10/2013 11:20 AM, Rob Godfrey wrote: On 10 October 2013 15:35, Ted Ross tr...@redhat.com wrote: On 10/10/2013 04:38 AM, Rob Godfrey wrote: My main concern is that I believe that Qpid should be primarily directed at implementing AMQP standards, and building resuable toolkits and

RE: Qpid Dispatch Router component

2013-10-10 Thread Steve Huston
Hi guys, -Original Message- From: Rob Godfrey [mailto:rob.j.godf...@gmail.com] Sent: Thursday, October 10, 2013 11:21 AM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router component On 10 October 2013 15:35, Ted Ross tr...@redhat.com wrote: On 10/10/2013 04:38 AM,

Re: Coaxing an error message out of qpid-cpp - unable to connect

2013-10-10 Thread Graham Leggett
On 10 Oct 2013, at 6:36 PM, Gordon Sim g...@redhat.com wrote: Yes it does, but the configuration is entirely different between these two clients. In particular I don't believe the 0.8/0-9-1/0-10 client uses 'amqps' to indicate ssl is to be used: