Re: [VOTE] Release Qpid Proton 0.13.0

+1 to release 0.13.0 tested: pyngus unit tests oslo.messaging unit and functional tests rsyslog amqp 1.0 plugin-in - Original Message - > From: "Justin Ross" > To: users@qpid.apache.org > Sent: Tuesday, June 7, 2016 10:31:17 AM > Subject: [VOTE] Release

Re: [Qpid-dispatch] Duplication between sslProfile and connector options

Hi Adel, Can you please setup your listener like this - listener { host: 0.0.0.0 port: 10399 saslMechanisms: ANONYMOUS sslProfile: ssl-profile-name authenticatePeer: no# Use authenticatePeer instead of requirePeerAuth requireSsl: yes } Thanks. -

Re: [Qpid-dispatch] Duplication between sslProfile and connector options

Hi Adel, You can find the entire list of entities and attributes here - http://qpid.apache.org/releases/qpid-dispatch-master/man/qdrouterd.conf.html I will purge the book of dashed entity/attribute names on the master branch. I have entered a JIRA for this so it can be tracked -

Re: [VOTE] Release Qpid Proton 0.13.0

Oh, sorry! I had that in my buffer to send in the initial mail and totally forgot. On Fri, Jun 10, 2016 at 6:44 AM, Robbie Gemmell wrote: > On 7 June 2016 at 15:31, Justin Ross wrote: > > The artifacts proposed for release: > > > >

Re: [VOTE] Qpid Dispatch Router 0.6.0 (RC4)

On 6 June 2016 at 22:32, Ted Ross wrote: > This is the vote thread to approve RC4 as the final Dispatch Router 0.6.0. > > Given that this is a significant release in terms of features and > functionality, I think we should get it released. > > I understand that there are a

Re: [VOTE] Release Qpid Proton 0.13.0

On 7 June 2016 at 15:31, Justin Ross wrote: > The artifacts proposed for release: > > https://dist.apache.org/repos/dist/dev/qpid/proton/0.13.0-rc/ > > Please indicate your vote below. If you favor releasing the 0.13.0 RC bits > as 0.13.0 GA, vote +1. If you have

RE: [Qpid-dispatch] Duplication between sslProfile and connector options

One last section, where in the book can I find the fields for ssl-profile configuration? I searched in Configuration Entities and found everything except "ssl-profile" fields. > From: adelbout...@live.com > To: users@qpid.apache.org > Subject: RE: [Qpid-dispatch] Duplication between sslProfile

RE: [Qpid-dispatch] Duplication between sslProfile and connector options

Thank you Ganesh, Is this documented somewhere? Will the dashed properties be removed from the Book to avoid such confusion in the future? Regards,Adel > Date: Fri, 10 Jun 2016 08:30:15 -0400 > From: gmur...@redhat.com > To: users@qpid.apache.org > Subject: Re: [Qpid-dispatch] Duplication

Re: [VOTE] Release Qpid Proton 0.13.0

+1 I run my tests with C++ broker (latest trunk), Qpid JMS client, Qpid Messaging C++ API - all built with the 0.13.0 RC. All seems to work fine. On Thu, Jun 9, 2016 at 8:26 PM, Timothy Bish wrote: > +1 > > * Checked the signature and the checksums > * Checked the license

Re: [Qpid-dispatch] Duplication between sslProfile and connector options

Hi Adel, Going forward please use the camelCase and abandon using dashed properties (like cert-file). Following is an example of the *correct* way to use certFile sslProfile { certFile: /home/gmurthy/opensource/server-certificate.pem keyFile: