Re: Qpid Dispatch to ActiveMQ

2015-05-13 Thread Noel OConnor
Hi Ted, Did you get a chance to look at this ? cheers Noel On Thu, May 7, 2015 at 7:53 AM Noel OConnor noel.ocon...@gmail.com wrote: Hi Ted, Yep I'm using linkroutes from the dispatch router instances to the brokers. Config below. cheers Noel connector { name: broker1 role:

Create qpid-interop sub-project

2015-05-13 Thread Kim van der Riet
I would like to propose and start a vote on asking infa@ to create a Qpid subproject called qpid-interop. The requested infrastructure will be limited to a git repo qpid-interop and a JIRA. All mailing and other communication would be performed through regular users@ and dev@ mailing lists.

[VOTE] Release Qpid JMS client 0.2.0

2015-05-13 Thread Robbie Gemmell
Hi all, We have made a bunch of fixes and improvements since the previous client release, both in the client itself and also in Proton. It is time those were available via an updated client release, so I have put up an RC for folks to test and vote on. The source and binary archives can be

0.32 cpp broker sasl authentication no mechanism agreed

2015-05-13 Thread Matt Broadstone
Hi all, I've recently updated my development environment to run the 0.32 release of qpidd (on ubuntu 14.04), and PLAIN sasl authentication no longer seems to work. Trying to use qpid-config to simply list the exchanges now results in a message indicating no mechanism agreed. I've got the

Re: 0.32 cpp broker sasl authentication no mechanism agreed

2015-05-13 Thread Chuck Rolke
See https://issues.apache.org/jira/browse/QPID-6511 . You need: --connection-options {username:dummy} or --connection-options {sasl-mechanisms:ANONYMOUS} - Original Message - From: Matt Broadstone mbroa...@gmail.com To: users users@qpid.apache.org Sent: Wednesday, May 13, 2015

Re: 0.32 cpp broker sasl authentication no mechanism agreed

2015-05-13 Thread Matt Broadstone
On Wed, May 13, 2015 at 2:00 PM, Chuck Rolke cro...@redhat.com wrote: See https://issues.apache.org/jira/browse/QPID-6511 . You need: --connection-options {username:dummy} or --connection-options {sasl-mechanisms:ANONYMOUS} Hi Chuck, Thanks for the quick response. I should have mentioned

Re: [VOTE] Release Qpid JMS client 0.2.0

2015-05-13 Thread Timothy Bish
+1 I performed the following checks * Inspected the LICENSE and NOTICE files in both src and bin archives * Validated the signatures for both archives. * Built the project from the source archive and ran all tests (no failures). * Reviewed the included documentation. * Ran the example against an

Re: 0.32 cpp broker sasl authentication no mechanism agreed

2015-05-13 Thread Gordon Sim
On 05/13/2015 07:04 PM, Matt Broadstone wrote: Thanks for the quick response. I should have mentioned that I am indeed specifying a username and password to qpid-config: qpid-config -a test\password@localhost is what results in no mechanism agreed. That should be: qpid-config -a