Re: Struggling to undersand Qpid C++ message store

2017-11-03 Thread Aleksey Vorona
Thank you, that works. I just verified it with --durable yes on both the queue and the message and it survives the broker restart. FYI, I am going to run a test with a 10K durable queues, all with persistance and a configured RING size restriction. All the consumers will be in the browsing mode.

RE: Struggling to undersand Qpid C++ message store

2017-11-03 Thread Steve Huston
Try: qpidd --load-module /usr/local/lib/qpid/daemon/linearstore.so > -Original Message- > From: Aleksey Vorona [mailto:voron...@gmail.com] > Sent: Friday, November 03, 2017 6:06 PM > To: users@qpid.apache.org > Subject: Struggling to undersand Qpid C++ message store > > Dear all, > > I

Struggling to undersand Qpid C++ message store

2017-11-03 Thread Aleksey Vorona
Dear all, I am trying to configure the C++ broker with a message persistence plugin and I can not find the documentation. My current problem is that I see `make install` to place a lib at /usr/local/lib/qpid/daemon/linearstore.so and yet it fails: $ qpidd --load-module linearstore.so

Re: [VOTE] Release Apache Qpid JMS 0.27.0

2017-11-03 Thread Oleksandr Rudyy
+1 * built and ran tests successfully from sources * ran system tests for broker-j on master using 0.27.0

Re: [VOTE] Release of qpid-interop-test 0.1.0

2017-11-03 Thread Chuck Rolke
+1 * kit contents ** signature appears ok ** md5sum checks ok ** ?? I can't figure out how to deal with the binary .sha512 file? how does one test that? * functionality ** compiles and runs binary test against proton-python, proton-cpp, and amqpnetlite clients ** ran some large content tests

[VOTE] Release Qpid Broker-J 7.0.0 (RC1)

2017-11-03 Thread Oleksandr Rudyy
Hi all, A release candidate for the next release (7.0.0) of the Qpid Broker-J has been created. It brings the following major changes: * Improved AMQP 1.0 support * Support for AMQP JMS Mapping Version 1.0 WD09 * Support for JMS 2.0 shared subscriptions (QPIDJMS-220) * Improved message

[RESULT] [VOTE] Release Apache Qpid Proton 0.18.1

2017-11-03 Thread Robbie Gemmell
There were 6 binding +1 votes, and no other votes received. The vote has passed. I will add the files to the dist release repo and create the final tag shortly. The website will be updated after the release has had time to sync to the mirrors. Robbie

Plans for Qpid JMS AMQP 0-x release - 6.3.0

2017-11-03 Thread Keith W
Hi all, A release of the legacy Qpid JMS AMQP 0-x needs to be made to cleanly separate the component from Qpid Broker J on the Apache Qpid site (separate component pages etc). The release will be identified as 6.3.0. The bump in the minor release number (from 6.1.x to 6.3.x) signifies the

Re: python-qpid-proton 0.18.0 package available for testing

2017-11-03 Thread Ken Giusti
I've just published these packages to the official PyPI repository: https://pypi.python.org/pypi/python-qpid-proton enjoy, On Mon, Oct 30, 2017 at 12:21 PM, Ken Giusti wrote: > Folks, > > I've spun up the latest 0.18.0 python package for testing. > > I've uploaded it to

Re: [VOTE] Release Apache Qpid Proton 0.18.1

2017-11-03 Thread Chuck Rolke
+1 check checksums, build, run tests on: fedora 25, windows Visual Studio 2012 x64, Visual Studio 2017 x64 - Original Message - > From: "Robbie Gemmell" > To: users@qpid.apache.org > Sent: Tuesday, October 31, 2017 9:49:48 AM > Subject: [VOTE] Release Apache

Re: [VOTE] Release Apache Qpid JMS 0.27.0

2017-11-03 Thread Keith W
+1 * Validated signatures and checksums * ran system tests for qpid-broker-j (master) using 0.27.0 staged artefact * Manually tested QPIDJMS-335 against qpid-broker-j (master) On 1 November 2017 at 23:07, Clebert Suconic wrote: > +1 > > > On Wed, Nov 1, 2017 at 4:01 PM,

Re: [VOTE] Release of qpid-interop-test 0.1.0

2017-11-03 Thread Robbie Gemmell
Some issues needing fixed before any release: - The archive contains a directory with -rc4 in the name, it needs recreated without that. - The checksum file extensions have changed since previous RCs and need fixed. Something that should proably be fixed before any release: - The JMS tests dont