Re: Struggling to undersand Qpid C++ message store

[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. So that there will be more or less
constant on-disk size (all messages are of the same size as well).

If there are any persistence layer options which make sense in this
scenario, please let me know. I am new to qpid.

-- Aleksey

On 11/3/17, Steve Huston  wrote:
> 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 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
>> 2017-11-03 15:04:07 [Broker] critical Unexpected error:
>> linearstore.so: cannot open shared object file: No such file or
>> directory: linearstore.so
>> (/media/data/source/qpid-cpp/src/qpid/sys/posix/Shlib.cpp:35)
>>
>> I have tried to change the LDPATH but it did not seem to help.
>>
>> I feel that I am missing a section in the documentation, as I can not find
>> any
>> documentation on configuring message store with the C++ broker.
>>
>> Could you help me, please?
>>
>> -- Aleksey
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional
>> commands, e-mail: users-h...@qpid.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

RE: Struggling to undersand Qpid C++ message store

[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 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
> 2017-11-03 15:04:07 [Broker] critical Unexpected error:
> linearstore.so: cannot open shared object file: No such file or
> directory: linearstore.so
> (/media/data/source/qpid-cpp/src/qpid/sys/posix/Shlib.cpp:35)
> 
> I have tried to change the LDPATH but it did not seem to help.
> 
> I feel that I am missing a section in the documentation, as I can not find any
> documentation on configuring message store with the C++ broker.
> 
> Could you help me, please?
> 
> -- Aleksey
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional
> commands, e-mail: users-h...@qpid.apache.org

Struggling to undersand Qpid C++ message store

[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
2017-11-03 15:04:07 [Broker] critical Unexpected error:
linearstore.so: cannot open shared object file: No such file or
directory: linearstore.so
(/media/data/source/qpid-cpp/src/qpid/sys/posix/Shlib.cpp:35)

I have tried to change the LDPATH but it did not seem to help.

I feel that I am missing a section in the documentation, as I can not
find any documentation on configuring message store with the C++
broker.

Could you help me, please?

-- Aleksey

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 0.27.0

[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

[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 OK with same clients

When things go wrong in this test environment it is not easy figuring out what 
happened.
There are so many places for things to fail: Client protocol error, client out 
of memory or
other process error, broker protocol or memory or process issue, zombie 
processes causing
broker to hold onto hundreds of megabytes of memory and that prevents the next 
test from
starting, actual interoperability errors, etc. That said, this is still a 
useful framework.


- Original Message -
> From: "Kim van der Riet" 
> To: users@qpid.apache.org
> Sent: Friday, October 27, 2017 2:32:49 PM
> Subject: [VOTE] Release of qpid-interop-test 0.1.0
> 
> This is the first official release of the test tool qpid-interop-test.
> 
> I have provided a release candidate at:
> https://dist.apache.org/repos/dist/dev/qpid/interop-test/0.1.0-rc4/
> 
> Instructions for building and installation are in QUICKSTART.md.
> 
> Please test and vote.
> 
> Thanks,
> Kim van der Riet
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

[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 conversion for applications using different AMQP
protocols
* Improved direct memory management

The list of new features, defect fixes and improvements can be found in
Jira:
https://issues.apache.org/jira /issues/?jql=project%20%3D%
20QPID%20AND%20fixVersion%20% 
3D%20qpid-java-broker-7.0.0

The source and binary archives can be grabbed from here:
https://dist.apache.org/repos/

dist/dev/qpid/broker-j/7.0.0-rc1


Those files and the other maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1119

Please test and vote accordingly.

Kind regards

P.S. If you want to test it out using maven (e.g with the examples src,
or your own things), you can temporarily add this to your poms to access
the staging repo:

  

  staging
  https://repository.apache.org/content/repositories/orgapacheqpid-
1119

  

[RESULT] [VOTE] Release Apache Qpid Proton 0.18.1

[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

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Plans for Qpid JMS AMQP 0-x release - 6.3.0

[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 separation from
Broker J, rather than a functional enhancement

There will be scope to include small defect fixes into this release.
This anyone has any such need, please discuss here.

cheers, Keith.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Accumulation of Links from global shared durable subscriptions (JMS 2.0)

[Rob Godfrey]

On 1 November 2017 at 10:16, Lorenz Quack  wrote:

> Hi,
>
> We noticed a potential problem with the way JMS 2.0 global shared
> durable subscriptions are implemented in the JMS client.  The
> implementation was designed, discussed, and implemented in QPIDJMS-220
> [1].
>
> When a consumer of a subscription closes the underlying AMQP link is
> not closed but merely detached since the closing of a subscription
> link is used as the signal to unsubscribe the subscription.  These
> subscription links remain on the broker until the subscription is
> unsubscribed (detach with close=true) at which point the broker
> discards all links associated with the subscription.
>
> For non-global subscriptions this does not seem to be a problem since
> the clientId is used as the container-id and links are reused if
> possible.
>
> For global subscription on the other hand the client uses a random
> UUID associated with the connection as its own container-id.  This
> means that on every new connection a new link is being estblished
> rather than recovering an existing one.  Over time these subscription
> links would accumulate on the broker until the subscription is
> unsubscribed.
>
> Since shared durable subscriptions are expected to be long lived this
> raises some concerns with regards to resource exhaustion on the
> broker.  An application that would spin up a connection do some work
> on a shared durable global subscription and then disconnect again
> would be "leaking" links.
>
> Due to this concern we plan on disabling shared durable global
> subscriptions for the initial v7 release of Qpid Broker-J.  There will
> be a context variable to enable the feature.
>
>
It seems to me a real shame that we are disabling this feature of JMS 2.0
because of the fact that from an AMQP point of view the link *may* be
resumed, but in practice, with JMS, will never be.  Would it not be better
to have a context variable which affects the behaviour of such links to
shared durable subscriptions such that if the context variable returns
"true" the links are removed from the link registry at the time of
connection closure, and if the context value is false, then the current
behaviour is maintained.  We could then later add functionality to the
client to specify (via some flag) the behaviour it desires (thus ultimately
removing the need for the context variable)?

-- Rob


>
> Thoughts, comments, discuss!
>
> Kind regards,
> Lorenz
>
>
> [1] https://issues.apache.org/jira/browse/QPIDJMS-220
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>
>

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

[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 TestPyPI for now.  If no problems are reported
> I'll move it to the official PyPI server by the end of the week.
>
> Try it out and let me know,
>
> $ pip install --index-url https://test.pypi.org/simple/ python-qpid-proton
>
> --
> -K



-- 
-K

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid Proton 0.18.1

[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 Qpid Proton 0.18.1
> 
> Hi folks,
> 
> I have put together a spin for a Qpid Proton 0.18.1 release, please
> give it a test out and vote accordingly.
> 
> The source archive can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.18.1-rc1/
> 
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12342056
> 
> It is tagged as 0.18.1-rc1.
> 
> Regards,
> Robbie
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 0.27.0

[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, Timothy Bish  wrote:
>> On 11/01/2017 12:37 PM, Robbie Gemmell wrote:
>>>
>>> Hi folks,
>>>
>>> I have put together a spin for a 0.27.0 Qpid JMS client release, please
>>> give it a test out and vote accordingly.
>>>
>>> The source and binary archives can be grabbed from:
>>> https://dist.apache.org/repos/dist/dev/qpid/jms/0.27.0-rc1/
>>>
>>> The maven artifacts are also staged for now at:
>>> https://repository.apache.org/content/repositories/orgapacheqpid-1118
>>>
>>> The JIRAs currently assigned are:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12341712
>>>
>>> Regards,
>>> Robbie
>>>
>>> P.S. If you want to test it out using maven (e.g with the examples src, or
>>> your own things), you can temporarily add this to your poms to access the
>>> staging repo:
>>>
>>>
>>>  
>>>staging
>>>
>>> https://repository.apache.org/content/repositories/orgapacheqpid-1118
>>>  
>>>
>>>
>>> The dependency for the client itself would then be:
>>>
>>>
>>>  org.apache.qpid
>>>  qpid-jms-client
>>>  0.27.0
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>>> For additional commands, e-mail: users-h...@qpid.apache.org
>>>
>>>
>> +1
>> * Validated signatures and checksums
>> * Checked for presence of license and notice files
>> * Ran mvn apache-rat:check to scan for missing license headers, none found.
>> * Built from source and ran tests
>> * Built ActiveMQ 5.x and ActiveMQ Artemis using staged bits and ran tests
>> * Inspected binary release for expected libraries and documentation.
>>
>> --
>> Tim Bish
>> twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

[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 work when JAVA_HOME is set, as the value is
misused and it ends up trying to run java in the wrong place due to
lacking the bin dir (which is traditionally not part of JAVA_HOME).
This was a bit annoying to figure out, as the tests didnt print any
error at the time, seeming to wait until the end, but the tests hung
awaiting messages that wouldnt arrive. I couldnt see any logs. I
changed this bit
https://github.com/apache/qpid-interop-test/blob/0.1.0-rc4/src/python/qpid_interop_test/shims.py#L213-L214
not to expect the bin dir in JAVA_HOME. If it cant find JAVA_HOME it
should probably just be using java from the path rather than guessing
where it is.

Some more general improvements for any time:
- Its only using QpidJMS 0.25.0 by default when 0.26.0 is out as noted
at RC3 (technically 0.27.0 could even be used with some temporary
testing instructions to access the staging repo until the vote closes)
- In the README it starts with the below. Making the title simply
"Qpid Interop Test Suite" might be nicer, then the content description
isn't particularly accurate, and I'd say the licence note can probably
just be removed as thats really what the LICENCE file is for
detailing.
"# Qpid Client Interoperability Test Suite

This directory contains the Qpid Proton Client API test suite.

All files in this directory are under the Apache License - see
[LICENSE](file:LICENSE) for
details."

Robbie

On 27 October 2017 at 19:32, Kim van der Riet  wrote:
> This is the first official release of the test tool qpid-interop-test.
>
> I have provided a release candidate at:
> https://dist.apache.org/repos/dist/dev/qpid/interop-test/0.1.0-rc4/
>
> Instructions for building and installation are in QUICKSTART.md.
>
> Please test and vote.
>
> Thanks,
> Kim van der Riet
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org