Re: [VOTE] Release Qpid Dispatch Router 1.5.0 (RC1)

2018-12-20 Thread Chuck Rolke
+1 [Note] * Built with proton master@ffe4915 * Self tests pass on Fedora 27 * Runs local network tests on F27 and F29 [Note] * One self test fails with Fedora 29. This is an issue with the ssl libraries on Fedora 29 as the kit works fine on Fedora 27. I do not think this is a regression. 49

Re: [VOTE] Release Qpid Dispatch Router 1.5.0 (RC1)

2018-12-20 Thread Michael Goulish
+1 I used this release, with proton 0.26, in my testing system with 3 interior routers, one edge router, 1 receiver, 1000 senders, and a sender getting killed every second. Nothing blew up. On Thu, Dec 20, 2018 at 11:14 AM Robbie Gemmell wrote: > On Wed, 19 Dec 2018 at 22:00, Ganesh Murthy

Re: [VOTE] Release Qpid Dispatch Router 1.5.0 (RC1)

2018-12-20 Thread Robbie Gemmell
On Wed, 19 Dec 2018 at 22:00, Ganesh Murthy wrote: > > Hello All, > > Please cast your vote on this thread to release RC1 as the > official Qpid Dispatch Router version 1.5.0. > > RC1 of Qpid Dispatch Router version 1.5.0 can be found here: > > https://dist.apache.org/repos/dist/dev/qpid

[RESULT][VOTE] Release Apache Qpid JMS 0.40.0

2018-12-20 Thread Robbie Gemmell
There were 5 binding +1 votes and 1 community +1 vote, with no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly. The website will be updated once the artifacts have had time to sync to the mirrors and maven central.

Re: [VOTE] Release Qpid Dispatch Router 1.5.0 (RC1)

2018-12-20 Thread Ganesh Murthy
+1 * Validated signatures and checksums * Checked for presence of LICENSE and NOTICE files * Ran mvn apache-rat:check, no files with missing license headers found. * Built from source against Proton 0.26.0 in Fedora 27 and ran system tests. All tests passed On Wed, Dec 19, 2018 at 5:00 PM Ganesh

Re: [VOTE] Release Qpid Broker-J 7.1.0

2018-12-20 Thread Robbie Gemmell
On Wed, 19 Dec 2018 at 17:09, Oleksandr Rudyy wrote: > > Hi folks, > > I built release artefacts for Qpid Broker-J version 7.1.0 RC1. > Please, give them a test out and vote accordingly. > > The source and binary archives can be grabbed from: > https://dist.apache.org/repos/dist/dev/qpid/broker-j/

Re: [VOTE] Release Qpid Broker-J 7.1.0

2018-12-20 Thread Gordon Sim
On 19/12/18 17:02, Oleksandr Rudyy wrote: Hi folks, I built release artefacts for Qpid Broker-J version 7.1.0 RC1. Please, give them a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.1.0-rc1/ +1 * verif

Re: [VOTE] Release Qpid Dispatch Router 1.5.0 (RC1)

2018-12-20 Thread Gordon Sim
On 19/12/18 22:00, Ganesh Murthy wrote: Hello All, Please cast your vote on this thread to release RC1 as the official Qpid Dispatch Router version 1.5.0. RC1 of Qpid Dispatch Router version 1.5.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.5.0-rc1/ +

Re: Can I expose Java properties set in the Qpid broker server via JMX or the REST API?

2018-12-20 Thread Robbie Gemmell
I dont know about the more general question (but I see Alex answered before I finished this), though on this item specifically... What you are asking about is from an MBean created by the JVM within its Platform MBeanServer, so the broker itself actually has nothing to do with it. If you fired up

Re: Can I expose Java properties set in the Qpid broker server via JMX or the REST API?

2018-12-20 Thread Oleksandr Rudyy
Hi Brian, You can add a suffix to the Apache Qpid version which is exposed via Broker attribute 'productVersion'. For example, if version of Qpid Broker is 7.0.6 and suffix is set to 'MY-CORP-1.3', the product version would be '7.0.6;MY-CORP-1.3'. This can be achieved by adding into broker lib fol

Re: Can I expose Java properties set in the Qpid broker server via JMX or the REST API?

2018-12-20 Thread Rob Godfrey
Hi Brian, On Wed, 19 Dec 2018 at 23:18, Brian O'Shea wrote: > Looking at jconsole (connected to the running Qpid broker), it appears that > it exposes a Map under java.lang -> Runtime -> Attributes > -> > SystemProperties. Is this something that I can depend on always being > available? This i