[Java Broker 6.1.1, qpid-jms-client 0.20.0] Best match for SASL auth was: null

2017-03-10 Thread Dan Langford
*Software Versions* Java Broker 6.1.1 qpid-jms-client 0.20.0 *When my Authentication Provider assigned to my AMQP port is PlainPasswordFile then i am able to connect just fine:* *RemoteURI *amqp://:5672?amqp.vhost=default [AmqpProvider:(1):[amqp://:5672]] INFO org.apache.qpid.jms.sasl.SaslMecha

Re: [Qpid Proton] How mandatory is Cyrus for SASL

2017-03-10 Thread Ganesh Murthy
- Original Message - > From: "Alan Conway" > To: users@qpid.apache.org > Sent: Tuesday, February 7, 2017 2:56:20 PM > Subject: Re: [Qpid Proton] How mandatory is Cyrus for SASL > > On Tue, 2017-02-07 at 19:32 +0100, Rabih M wrote: > > Hello, > > > > I compiled qpid-proton 0.16.0 with "

Re: [VOTE] Release Apache Qpid JMS 0.21.0

2017-03-10 Thread Timothy Bish
+1 * Validated the signatures and checksums * Checked for license and notice files in the source and binary archives * Built from source and ran the tests. * Checked the binary archive for the proper files * Built an ActiveMQ 5.x broker against the staged bits and ran the AMQP tests. On 03/10/

[HEADS UP] qpid-cpp 1.37.0

2017-03-10 Thread Robbie Gemmell
There have been a number of changes made since 1.36.0 that it would be good to get out in a release, so I think its time to do qpid-cpp 1.37.0 soon. If you know of anything in the pipeline that should be considered waiting for, shout, otherwise I'll look toward doing this mid next week. Robbie -

Re: [VOTE] Release Apache Qpid JMS 0.21.0

2017-03-10 Thread Robbie Gemmell
On 10 March 2017 at 17:13, Robbie Gemmell wrote: > Hi folks, > > I have put together a spin for a 0.21.0 Qpid JMS client release, > please test it and vote accordingly. > > The source and binary archives can be grabbed from: > https://dist.apache.org/repos/dist/dev/qpid/jms/0.21.0-rc1/ > > (Note:

Re: [DISCUSS] release checksum filename extension

2017-03-10 Thread Robbie Gemmell
I decided to set the svn:mime-type to text/plain for the qpid-jms-0.21.0 release files I just added. It turns out that is what gets used on the main www.apache.org webserver once they are eventually released, and the issue only applies on the dist.apache.org webserver fronting the svn dist repo. R

[VOTE] Release Apache Qpid JMS 0.21.0

2017-03-10 Thread Robbie Gemmell
Hi folks, I have put together a spin for a 0.21.0 Qpid JMS client release, please test it and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/0.21.0-rc1/ (Note: the .sha files contain SHA512 checksums) The maven artifacts are

Re: [DISCUSS] release checksum filename extension

2017-03-10 Thread Robbie Gemmell
As noted in the vote thread, the webserver presenting the svn dist repo is seemingly mishhandling the .sha files and this leads to Firefox saving a gzip encoded version of the checksum. This is raised as https://issues.apache.org/jira/browse/INFRA-13629 Hopefully it can be fixed webserver side, bu

[RESULT] [VOTE] Release Apache Qpid Proton-J 0.18.0

2017-03-10 Thread Robbie Gemmell
There were 3 binding +1 votes, 1 non-binding +1 community vote, and no other votes received. The vote has passed. I will add the archives to the dist release repo and release the maven staging repo shortly. The website will be updated after the artifacts have had time to sync to the mirrors and ma

[AMQP] Link Pairing Working Draft 1 Uploaded

2017-03-10 Thread Rob Godfrey
All, for those who are interested, I've just uploaded to OASIS the first draft of a mechanism for doing direct request-response messaging over AMQP called "Link Pairing". The working draft is here: https://www.oasis-open.org/committees/document.php?document_id=60237&wg_abbrev=amqp If you have co