Re: [VOTE] Release Apache Qpid JMS 0.48.0

[Jakub Scholz]

+1 ... I used the staged artifacts and run them against different versions
of the C++ broker - all seemed to be fine and working.

On Fri, Dec 6, 2019 at 6:39 PM Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.48.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.48.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1188
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12346475
>
> 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-1188
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.48.0
>   
>
> -
> 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.47.0

[Jakub Scholz]

+1 ... I used the staged JARs and run tests against different versions of
the C++ broker and all seems fine.

On Fri, Nov 1, 2019 at 8:41 PM Gordon Sim  wrote:

> On 01/11/2019 12:37 pm, Robbie Gemmell wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.47.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.47.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1185
> >
> > The JIRAs assigned are:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12346264
>
> +1
>
> (verified checksum and signature, built from source including running
> tests, ran example against c++ broker and router).
>
>
> -
> 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.46.0

[Jakub Scholz]

+1 ... I used the staged JARs and run tests against different versions of
Qpid C++ broker

Jakub

On Tue, Sep 24, 2019 at 11:00 PM Timothy Bish  wrote:

> On 9/24/19 1:47 PM, Robbie Gemmell wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.46.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.46.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1183
> >
> > The JIRAs assigned are:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12346054
> >
> > 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-1183
> 
> >  
> >
> >
> > The dependency for the client itself would then be:
> >
> >
> >  org.apache.qpid
> >  qpid-jms-client
> >  0.46.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 license and notice files in archives
> * Checked source for license headers using Apache rat maven plugin
> * Built from source and ran all tests
> * Built ActiveMQ 5.x master using staged artifacts and ran the AMQP tests
> * Built ActiveMQ Artemis master using staged artifacts and ran the AMQP
> tests
>
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Welcome Ben Hardesty as an Apache Qpid committer

[Jakub Scholz]

Welcome Ben ...

On Mon, Sep 23, 2019 at 11:59 AM Robbie Gemmell 
wrote:

> The Qpid PMC have voted to grant commit rights to Ben Hardesty in
> recognition of continued contributions to the project.
>
> Welcome, Ben!
>
> -
> 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.45.0

[Jakub Scholz]

+1 ... I run tests using the staged JARs against different versions of
Qpidd and all seems to work well.

On Thu, Aug 22, 2019 at 10:56 AM Oleksandr Rudyy  wrote:

> +1
>
> * Built from source bundle and ran all tests
> * Verified signatures and checksums
> * Ran successfully Qpid Broker-J integration tests on master branch using
> staged artefacts
>
>
> On Wed, 21 Aug 2019 at 16:28, Robbie Gemmell 
> wrote:
>
> > Hi folks,
> >
> > I have put together a spin for a 0.45.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.45.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1182
> >
> > The JIRAs assigned are:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12345706
> >
> > 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-1182
> > 
> > 
> >   
> >
> > The dependency for the client itself would then be:
> >
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 0.45.0
> >   
> >
> > -
> > 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 AMQP 0-x 6.3.4

[Jakub Scholz]

+1 ... used the staging repo and run the client against C++ broker.

On Tue, May 14, 2019 at 3:21 PM Oleksandr Rudyy  wrote:

> Hi,
> I built a candidate release for version 6.3.4 of Qpid JMS for AMQP 0-x.
> The release makes legacy JMS client compatible with java 11. It also
> incorporate a number of defect fixes.
> Please, test and vote accordingly.
>
> The source and binary bundles can be taken from:
> https://dist.apache.org/repos/dist/dev/qpid/jms-amqp-0-x/6.3.4-RC1
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1175
>
> The JIRAs currently assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12345142
>
> Regards,
> Alex
>
> P.S. If you want to test it out using maven, you can temporarily add this
> to your project pom to access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1175
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-client
> 6.3.4
>   
>
> -
> 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.42.0

[Jakub Scholz]

+1. I used the staged jars and run the client against different versions of
the C++ broker.


On Thu, May 9, 2019 at 4:59 AM Keith W  wrote:

> +1
>
> * Verified signatures and checksums
> * Checked for LICENCE and NOTICE files in the archives.
> * ran apache rat-check
> * built from source distribution artefact and ran all tests (mvn
> verify with Java 1.8.0_191 and 11.0.2 on Mac OS X 10.13.6)
> * ran Broker-J's JMS integration test suite (mvn clean verify
> -DskipTests=true -DskipITs=false) against the staged Maven artefacts
>
> On Wed, 8 May 2019 at 12:35, Gordon Sim  wrote:
> >
> > On 07/05/2019 6:38 pm, Robbie Gemmell wrote:
> > > Hi folks,
> > >
> > > I have put together a spin for a 0.42.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.42.0-rc1/
> >
> > +1
> >
> > * verified signature and checksum, built from source including tests
> > * ran helloworld example against
> >- proton-python example broker
> >- qpid-cpp broker
> >- dispatch router
> >
> > -
> > 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.41.0

[Jakub Scholz]

+1. I used the staging repo and run the client against different versions
of the C++ broker.

On Wed, Apr 3, 2019 at 9:21 PM Timothy Bish  wrote:

> On 4/3/19 1:17 PM, Robbie Gemmell wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.41.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.41.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1171
> >
> > The JIRAs assigned are:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12344648
> >
> > 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-1171
> 
> >  
> >
> >
> > The dependency for the client itself would then be:
> >
> >
> >  org.apache.qpid
> >  qpid-jms-client
> >  0.41.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
> * Verified archives contained license and notice files
> * Checked source files for license headers using 'mvn apache-rat:check'
> * Built from source and ran all tests.
> * Built ActiveMQ 5 master using staged bits and ran all AMQP tests
> * Built ActiveMQ Artemis master using staged bits and ran the AMQP
> integration tests.
>
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Welcome Jiri Danek as an Apache Qpid committer

[Jakub Scholz]

Welcome, Jiri, Great to have you here.

On Fri, Mar 1, 2019 at 11:12 AM Robbie Gemmell 
wrote:

> The Qpid PMC have voted to grant commit rights to Jiri Danek in
> recognition of continued contributions to the project.
>
> Welcome, Jiri!
>
> Robbie
>
> -
> 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.40.0

[Jakub Scholz]

+1 ... I run the client against different versions of the C++ broker and
all seems to be ok. (I used the staging repository)

On Mon, Dec 17, 2018 at 12:47 PM Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.40.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.40.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1164
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12344573
>
> 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-1164
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.40.0
>   
>
> -
> 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.39.0

[Jakub Scholz]

+1 ... I used the staging repo and run the client against different
versions of the C++ broker.

On Wed, Nov 28, 2018 at 2:37 PM Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.39.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.39.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1163
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=1233
>
> 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-1163
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.39.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Welcome Roddie Kieley as an Apache Qpid committer

[Jakub Scholz]

Congrats and welcome to the community ... and thanks for all your
contributions Roddie!

Jakub

On Tue, Nov 27, 2018 at 3:38 PM Robbie Gemmell 
wrote:

> The Qpid PMC have voted to grant commit rights to Roddie Kieley in
> recognition of continued contributions to the project.
>
> Welcome, Roddie!
>
> Robbie
>
> -
> 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.38.0

[Jakub Scholz]

+1 ... I used the staging repo and run the client against Qpid C++ broker.

On Mon, Nov 12, 2018 at 7:43 PM Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.38.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.38.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1161
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12344251
>
> 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-1161
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.38.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid Dispatch Router 1.4.1 (RC3)

[Jakub Scholz]

+1 ... built from source on CentOS7 and checked against AQM 1.0 clients.

On Thu, Oct 25, 2018 at 4:00 PM Ganesh Murthy  wrote:

> Hello All,
>
>  Please cast your vote on this thread to release RC3 as the
> official Qpid Dispatch Router version  1.4.1.
>
> RC3 of Qpid Dispatch Router version 1.4.1 can be found here:
>
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.4.1-rc3/
>
> The following bugs are fixed in 1.4.1:
>
> DISPATCH-1148 - auth plugin should indicate version in open properties
> DISPATCH-1149 - authz plugin can no longer override conf file policy
> DISPATCH-1151 - Revert to gulp version 3 for console build
> DISPATCH-1157 - auth plugin leaks memory
>
> Thanks
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Apache Qpid C++ 1.39.0

[Jakub Scholz]

+1 ... I have built it from source on CentOS and run tests with different
clients against it.

On Mon, Oct 22, 2018 at 2:47 PM Justin Ross  wrote:

> Hi, everyone.  Please test this release candidate and vote based on what
> you find.
>
> Source archive and signatures:
> https://dist.apache.org/repos/dist/dev/qpid/cpp/1.39.0-rc1/
>
> Issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12342978
>
> Tag:
> 1.39.0-rc1
>

Re: [VOTE] Release Apache Qpid JMS 0.37.0

[Jakub Scholz]

+1 ... I used the staging repository and run my tests against the C++
broker. All seems to work fine.

On Sun, Sep 30, 2018 at 11:21 PM Oleksandr Rudyy  wrote:

> +1
>
> * Verified signatures and checksums
> * Built and ran tests from source bundle
> * Ran Qpid Broker-J integration tests on master using staged 0.37.0
> artifacts
>
> On Fri, 28 Sep 2018 at 18:32, Robbie Gemmell 
> wrote:
> >
> > Hi folks,
> >
> > I have put together a spin for a 0.37.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.37.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1159
> >
> > The JIRAs assigned are:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12343889
> >
> > 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-1159
> 
> > 
> >   
> >
> > The dependency for the client itself would then be:
> >
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 0.37.0
> >   
> >
> > -
> > 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.36.0

[Jakub Scholz]

+1 ... I used the staging repo and tried it against Qpid C++ broker. All
seems to work fine.

On Thu, Aug 16, 2018 at 1:13 PM Oleksandr Rudyy  wrote:

> +1
>
> I performed the following tests:
> * verified checksums and signatures
> * built and ran tests from source bundle
> * ran Qpid Broker-J integration tests on master branch using staged
> 0.36 artefacts, overridden netty version 4.1.28.Final and profiles
> java-bdb.1-0/java-mms.1-0
> On Wed, 15 Aug 2018 at 19:19, Robbie Gemmell 
> wrote:
> >
> > I have put together a spin for a 0.36.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.36.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1157
> >
> > The JIRAs assigned are:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12343767
> >
> > 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-1157
> 
> > 
> >   
> >
> > The dependency for the client itself would then be:
> >
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 0.36.0
> >   
> >
> > -
> > 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 AMQP 0-x 6.3.3

[Jakub Scholz]

+1 ... I used the staged artifacts with AMQP 0-10 and run some of my tests
against Qpid C++ broker.

On Mon, Aug 13, 2018 at 7:22 PM Oleksandr Rudyy  wrote:

> Hi,
>
> I built a candidate release for version 6.3.3 of Qpid JMS AMQP 0-x.
> Please test and vote accordingly.
>
> The source and binary bundles can be taken from:
> https://dist.apache.org/repos/dist/dev/qpid/jms-amqp-0-x/6.3.3-RC1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1156
>
> The JIRAs currently assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12343821
>
> Regards,
> Alex
>
> P.S. If you want to test it out using maven, you can temporarily add this
> to your project pom to access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1156
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-client
> 6.3.3
>   
>
> -
> 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.35.0

[Jakub Scholz]

+1 ... Used the staged JARs against different versions of Qpid C++ broker.
All seems to work fine.

On Fri, Jul 20, 2018 at 12:10 PM Robbie Gemmell 
wrote:

> I have put together a spin for a 0.35.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.35.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1150
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12343545
>
> 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-1150
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.35.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid Dispatch Router 1.2.0 (RC2)

[Jakub Scholz]

+1 ... build from source on CentOS 7 and used with different clients.

On Mon, Jul 2, 2018 at 6:19 PM Robbie Gemmell 
wrote:

> +1
>
> I checked things out as follows:
>  - Verified the signature and checksum files.
>  - Checked for LICENCE+NOTICE files in the archive.
>  - Ran mvn apache-rat:check to verify the licence headers.
>  - Built the router against Proton 0.24.0 and ran all the tests.
>  - Ran the JMS client 0.34.0 HelloWorld example against the router.
>
> Robbie
>
> On 29 June 2018 at 20:21, Ganesh Murthy  wrote:
> > Hello All,
> >
> >  Please cast your vote on this thread to release RC2 as the
> > official Qpid Dispatch Router version  1.2.0.
> >
> > RC2 of Qpid Dispatch Router version 1.2.0 can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.2.0-rc2/
> >
> > The following features, improvements, and bug fixes are introduced in
> 1.2.0:
> >
> > Features -
> > DISPATCH-970 - Add a chord view of message flow to console
> > DISPATCH-980 - Allow address translation on link routes
> > DISPATCH-1014 - Visualize link congestion on topology page
> >
> > Improvements -
> > DISPATCH-965 - Python 3 compatibiliy
> > DISPATCH-982 - Handle small form-factor screens
> > DISPATCH-1002 - Animate message flow on the console's topology page.
> > DISPATCH-1013 - Enable vhost policies to be used in the router
> > config file (not just through separate JSON files)
> > DISPATCH-1015 - Improve visualization of connection and link info
> > on console's topology page.
> > DISPATCH-1016 - Consolidate console style sheets to improve load time
> > DISPATCH-1017 - Use a javascript build system for the console
> > DISPATCH-1020 - Detach expiring links with closed=true when peer
> > connectivity lost
> > DISPATCH-1024 - Latest version of qpid-proton is causing build
> > issues on Travis, to system tests using incorrect url with user and
> > password
> > DISPATCH-1049 - Add console tests
> > DISPATCH-1053 - Allow deliveries to be constrained to
> > router-control links by address state
> >
> > Bug fixes -
> > DISPATCH-969 - Dropdown menu doesn't work when browser is narrow
> > DISPATCH-976 - Allow policy for sources and targets to handle
> > multiple wildcards
> > DISPATCH-979 - self test mock policy manager does not forward
> > policy warnings
> > DISPATCH-984 - Json config file processing clobbers files with '#'
> > character in strings
> > DISPATCH-985 - Policy username substitution token is documented
> incorrectly
> > DISPATCH-988 - Documentation of policy default vhost is wrong
> > DISPATCH-990 - Use patterns for policy vhost hostnames
> > DISPATCH-998 - Parse tree does not have remove function that takes
> > a string pattern
> > DISPATCH-1003 - Enable console support for connecting to listener
> > configured with saslMechanisms other than ANONYMOUS
> > DISPATCH-1008 - Router should preserve original connection
> > information when attempting to make failover connections
> > DISPATCH-1011 - Policy username substitution fails to match
> > certain user names
> > DISPATCH-1025 - User token not being replaced properly on a vhost
> > policy when defined in the prefix or suffix
> > DISPATCH-1026 - Router crashing when using
> > sourcePattern/targetPattern with multiple patterns and one of them
> > being user token when trying to open an unauthorized address
> > DISPATCH-1029 - State is not retained on Entities tree for console
> > DISPATCH-1030 - Empty table on Entities page of console
> > DISPATCH-1031 - Remove the links associated with a console from
> > the console's overview page
> > DISPATCH-1033 - Incorrect location for legend on Message flow page
> > in console
> > DISPATCH-1034 - saslPlugin option does not work with http option in
> listener
> > DISPATCH-1036 - Dropdown lists on the Entity page are the wrong color
> > DISPATCH-1037 - Listeners with http enabled are not being shutdown
> > after they are deleted
> > DISPATCH-1041 - Add new test to validate global delivery counts
> > provided by the router
> > DISPATCH-1043 - In a two router network, qdstat -g is showing
> > non-zero values for "Ingress Count" even when no messages are sent
> > DISPATCH-1044 - Link routed deliveries not included in the global
> > transit and egress counts
> > DISPATCH-1045 - Sometimes close connetion after releasing partial
> > multi-frame messsage
> > DISPATCH-1046 - system_tests_policy fail in python3 environment
> > DISPATCH-1047 - system_tests_ssl fail when running under python3
> environment
> > DISPATCH-1048 - system_tests_http fail when run under python3
> environment
> > DISPATCH-1050 - sasl delegation plugin should set SNI to match auth
> address
> > DISPATCH-1051 - Python memory leak via PyLong_FromLong
> > DISPATCH-1052 - minor lock leak in policy code
> > DISPATCH-1056 - Build fails making docs on python-3-only 

Re: [VOTE] Release Apache Qpid JMS 0.33.0

[Jakub Scholz]

+1 ... I used the staging repo and run the client against different
versions of Qpid C++ broker. All seems to work fine.

On Mon, Jun 11, 2018 at 7:32 PM Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.33.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.33.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1143
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12343151
>
> 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-1143
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.33.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC6)

[Jakub Scholz]

+1 ... build from source on CentOS7 and used with different AMQP 1.0
clients.

On Thu, Jun 7, 2018 at 11:02 PM Ganesh Murthy  wrote:

> Hello All,
>
>  Please cast your vote on this thread to release RC6 as the
> official Qpid Dispatch Router version  1.1.0.
>
> RC6 of Qpid Dispatch Router version 1.1.0 can be found here:
>
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc6/
>
> The following features, improvements, and bug fixes are introduced in
> 1.1.0:
>
> Features -
> DISPATCH-89 - Model the legacy topic exchange behavior of qpidd
> DISPATCH-834 - Create config tool to create/read/update/delete
> router config files
> DISPATCH-856 - Return router's hostname as a read-only attribute
> on the router entity
> DISPATCH-892 - Support code coverage testing
> DISPATCH-911 - Add link and address level counters at the global
> router level
> DISPATCH-932 - Provide per-ingress router counts for deliveries on
> egress links
>
> Improvements -
> DISPATCH-859 - Introduce SYSTEMD and SYSVINIT cmake switches to
> install files accordingly
> DISPATCH-861 - Update to recent rhea.js
> DISPATCH-864 - Remove the SYSTEMD and SYSVINIT flags introduced by
> DISPATCH-859
> DISPATCH-872 - Add a counter for dropped-presettleds on links
> DISPATCH-878 - qdrouterd should log real port if port 0 was
> specified for the listener port property in qdrouterd.conf
> DISPATCH-884 - Add schema property to allow configurable TLS
> protocol versions
> DISPATCH-885 - Modify qd_compose_insert_[string,symbol,binary] to
> add zero-length [string, symbol, binary] for null input
> DISPATCH-888 - Balanced distribution algorithm visits each link to
> determine the best_eligible_link
> DISPATCH-901 - add authz support to auth service plugin
> DISPATCH-904 - Add charts to overview page
> DISPATCH-918 - Improve router config consistency and metadata
> DISPATCH-921 - Install console dependencies with npm during make
> install
> DISPATCH-923 - Clean up javascript to pass eslint tests without errors
> DISPATCH-925 - Doc: Update anchor name format
> DISPATCH-938 - Doc: Remove the "Configuration Reference"
> DISPATCH-942 - allow resumable link routes to be refused
> DISPATCH-946 - Detect if npm install needs to be executed and
> display a message
> DISPATCH-951 - log details for the proton found during build
> DISPATCH-963 - Router crash during shutdown in
> system_tests_distribution
> DISPATCH-971 - Revert DISPATCH-744 - Don't reject unsettled multicasts
> DISPATCH-972 - Dispatch Router doc should be consistent with "sudo"
> usage
> DISPATCH-1012 - Release undeliverable deliveries, don't hold them
>
> Bug fixes -
> DISPATCH-580 - Log stats should be graphable
> DISPATCH-590 - List of log modules on the overview page is
> occationally doubled
> DISPATCH-801 - Stand-alone version of the console does not open at
> all when running offline
> DISPATCH-831 - Change conntector.cost default value to 1 instead of '1'
> DISPATCH-869 - Multiple brokers in a topology are displayed as a
> single broker
> DISPATCH-875 - Document address and link route wildcards
> DISPATCH-876 - config file linkRoute should use connection instead
> of connector
> DISPATCH-877 - Document how to configure TLS ciphers
> DISPATCH-879 - Document how Dispatch Router uses alternate failover
> URLs
> DISPATCH-880 - Document how Dispatch Router disconnects connections
> DISPATCH-886 - Console does not properly escape HTML in entity names
> DISPATCH-891 - Router incref assert in system_tests_delivery_abort
> DISPATCH-893 - Compile fails using libwebsockets 7
> DISPATCH-894 - Unable to run system tests on CentOS 6 (Python 2.6)
> DISPATCH-902 - Intermittent crash with link to broker when broker
> closed
> DISPATCH-905 - Dispatch Router not failing over to slave broker
> when master broker goes away
> DISPATCH-907 - cannot set address phase via qdmanage tool
> DISPATCH-910 - Inter-router connections with dir 'in' have no host name
> DISPATCH-912 - system_tests_user_id_proxy and system_tests_policy
> failing
> DISPATCH-915 - connection rhost  not calculated soon enough
> DISPATCH-916 - qdmanage get-attributes and get-operations not
> taking into account passed in type
> DISPATCH-919 - Display a warning when running Dispatch tests if
> python-unittest2 is not installed
> DISPATCH-922 - Subsecond timestamps improperly formatted
> DISPATCH-927 - detach not echoed back on multi-hop link route
> DISPATCH-928 - calling map_destination for 'undefined' address
> causes segfault
> DISPATCH-931 - Syntax error and missing dependencies in docker files
> DISPATCH-940 - When running qdrouterd with -c and -d combined,
> configuration file is reporting as not found
> DISPATCH-941 - Router is returning incorrect files from http get
> requests.
> DISPATCH-943 - segfault 

Re: Proposal to deprecate qpid legacystore

[Jakub Scholz]

Sounds reasonable to me. The linearstore is around long enough and works
well.

Jakub

On Wed, Jun 6, 2018 at 4:21 PM Kim van der Riet 
wrote:

> I would like to propose that the qpid legacystore be deprecated. It has
> been replaced by the linearstore, which is built by default. This has
> been the case for more than 3 years now.
>
> I suggest that we place a deprecation notice into the build and on
> startup into the logs at warning level. After six months or so, we can
> remove it from the source tree.
>
> Suggestions, comments?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC4)

[Jakub Scholz]

+1 ... I build it from source on CentOS7 and used with different AMQP 1.0
clients.

On Fri, May 25, 2018 at 11:45 PM Ganesh Murthy  wrote:

> Hello All,
>
>  Please cast your vote on this thread to release RC4 as the
> official Qpid Dispatch Router version  1.1.0.
>
> RC4 of Qpid Dispatch Router version 1.1.0 can be found here:
>
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc4/
>
> The following features, improvements, and bug fixes are introduced in
> 1.1.0:
>
> Features -
> DISPATCH-89 - Model the legacy topic exchange behavior of qpidd
> DISPATCH-834 - Create config tool to create/read/update/delete
> router config files
> DISPATCH-856 - Return router's hostname as a read-only attribute
> on the router entity
> DISPATCH-892 - Support code coverage testing
> DISPATCH-911 - Add link and address level counters at the global
> router level
> DISPATCH-932 - Provide per-ingress router counts for deliveries on
> egress links
>
> Improvements -
> DISPATCH-859 - Introduce SYSTEMD and SYSVINIT cmake switches to
> install files accordingly
> DISPATCH-861 - Update to recent rhea.js
> DISPATCH-864 - Remove the SYSTEMD and SYSVINIT flags introduced by
> DISPATCH-859
> DISPATCH-872 - Add a counter for dropped-presettleds on links
> DISPATCH-878 - qdrouterd should log real port if port 0 was
> specified for the listener port property in qdrouterd.conf
> DISPATCH-884 - Add schema property to allow configurable TLS
> protocol versions
> DISPATCH-885 - Modify qd_compose_insert_[string,symbol,binary] to
> add zero-length [string, symbol, binary] for null input
> DISPATCH-888 - Balanced distribution algorithm visits each link to
> determine the best_eligible_link
> DISPATCH-901 - add authz support to auth service plugin
> DISPATCH-904 - Add charts to overview page
> DISPATCH-918 - Improve router config consistency and metadata
> DISPATCH-921 - Install console dependencies with npm during make
> install
> DISPATCH-923 - Clean up javascript to pass eslint tests without errors
> DISPATCH-925 - Doc: Update anchor name format
> DISPATCH-938 - Doc: Remove the "Configuration Reference"
> DISPATCH-942 - allow resumable link routes to be refused
> DISPATCH-946 - Detect if npm install needs to be executed and
> display a message
> DISPATCH-951 - log details for the proton found during build
> DISPATCH-963 - Router crash during shutdown in
> system_tests_distribution
> DISPATCH-971 - Revert DISPATCH-744 - Don't reject unsettled multicasts
> DISPATCH-972 - Dispatch Router doc should be consistent with "sudo"
> usage
>
> Bug fixes -
> DISPATCH-580 - Log stats should be graphable
> DISPATCH-590 - List of log modules on the overview page is
> occationally doubled
> DISPATCH-801 - Stand-alone version of the console does not open at
> all when running offline
> DISPATCH-831 - Change conntector.cost default value to 1 instead of '1'
> DISPATCH-869 - Multiple brokers in a topology are displayed as a
> single broker
> DISPATCH-875 - Document address and link route wildcards
> DISPATCH-876 - config file linkRoute should use connection instead
> of connector
> DISPATCH-877 - Document how to configure TLS ciphers
> DISPATCH-879 - Document how Dispatch Router uses alternate failover
> URLs
> DISPATCH-880 - Document how Dispatch Router disconnects connections
> DISPATCH-886 - Console does not properly escape HTML in entity names
> DISPATCH-891 - Router incref assert in system_tests_delivery_abort
> DISPATCH-893 - Compile fails using libwebsockets 7
> DISPATCH-894 - Unable to run system tests on CentOS 6 (Python 2.6)
> DISPATCH-902 - Intermittent crash with link to broker when broker
> closed
> DISPATCH-905 - Dispatch Router not failing over to slave broker
> when master broker goes away
> DISPATCH-907 - cannot set address phase via qdmanage tool
> DISPATCH-910 - Inter-router connections with dir 'in' have no host name
> DISPATCH-912 - system_tests_user_id_proxy and system_tests_policy
> failing
> DISPATCH-915 - connection rhost  not calculated soon enough
> DISPATCH-916 - qdmanage get-attributes and get-operations not
> taking into account passed in type
> DISPATCH-919 - Display a warning when running Dispatch tests if
> python-unittest2 is not installed
> DISPATCH-922 - Subsecond timestamps improperly formatted
> DISPATCH-927 - detach not echoed back on multi-hop link route
> DISPATCH-928 - calling map_destination for 'undefined' address
> causes segfault
> DISPATCH-931 - Syntax error and missing dependencies in docker files
> DISPATCH-940 - When running qdrouterd with -c and -d combined,
> configuration file is reporting as not found
> DISPATCH-943 - segfault in remote_sasl
> DISPATCH-944 - remote_sasl plugin leaving connections open
> DISPATCH-945 - Crash on shutdown when a http+websocket 

Re: [VOTE] Release Apache Qpid JMS AMQP 0-x 6.3.1

[Jakub Scholz]

+1 ... I used the staging repo and run my tests against different versions
of C++ broker with AMQP 0-10. All seems to work for me.

On Wed, May 16, 2018 at 5:44 PM Timothy Bish  wrote:

> On 05/15/2018 07:36 AM, Oleksandr Rudyy wrote:
> > Hi folks,
> >
> > I built a candidate release for version 6.3.1 of Qpid JMS AMQP 0-x.
> >
> > Please test and vote accordingly.
> >
> > The source and binary bundles can be taken from:
> > https://dist.apache.org/repos/dist/dev/qpid/jms-amqp-0-x/6.3.1/
> >
> > The maven artifacts are also staged at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1140
> >
> > The JIRAs currently assigned are:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12342207
> >
> > Regards,
> > Alex
> >
> > P.S. If you want to test it out using maven, you can temporarily add this
> > to your project pom to access the staging repo:
> >
> >
> >  
> >staging
> >
> > https://repository.apache.org/content/repositories/orgapacheqpid-1140
> 
> >  
> >
> >
> > The dependency for the client itself would then be:
> >
> >
> >  org.apache.qpid
> >  qpid-client
> >  6.3.1
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
>
> +1
>
> * Verified signatures and checksums
> * Verified Licensee and NOTICE files were present in the archives
> * Built from source and ran the unit tests
> * Ran mvn apache-rat:check to validate license headers
>
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC2)

[Jakub Scholz]

Ups ... I run my tests but forgot the vote :-).

+1 ... I build it from source on CentOS 7 and used with different AMQP 1.0
clients.

On Mon, May 7, 2018 at 7:28 PM, Ganesh Murthy  wrote:

> The vote is being extended for a couple more days to give time for people
> to test. Thanks.
>
> On Tue, May 1, 2018 at 4:39 PM, Ganesh Murthy  wrote:
>
> > Hello All,
> >
> >  Please cast your vote on this thread to release RC2 as the
> > official Qpid Dispatch Router version  1.1.0.   RC2 of Qpid Dispatch
> > Router version 1.1.0 can be found here -
> >
> > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc2/
> >
> > The following features, improvements, and bug fixes are introduced in
> > 1.1.0:
> >
> > Features -
> > DISPATCH-89 - Model the legacy topic exchange behavior of qpidd
> > DISPATCH-834 - Create config tool to create/read/update/delete
> > router config files
> > DISPATCH-856 - Return router's hostname as a read-only attribute
> > on the router entity
> > DISPATCH-892 - Support code coverage testing
> > DISPATCH-911 - Add link and address level counters at the global
> > router level
> > DISPATCH-932 - Provide per-ingress router counts for deliveries on
> > egress links
> >
> > Improvements -
> > DISPATCH-859 - Introduce SYSTEMD and SYSVINIT cmake switches to
> > install files accordingly
> > DISPATCH-861 - Update to recent rhea.js
> > DISPATCH-864 - Remove the SYSTEMD and SYSVINIT flags introduced by
> > DISPATCH-859
> > DISPATCH-872 - Add a counter for dropped-presettleds on links
> > DISPATCH-878 - qdrouterd should log real port if port 0 was
> > specified for the listener port property in qdrouterd.conf
> > DISPATCH-884 - Add schema property to allow configurable TLS
> > protocol versions
> > DISPATCH-885 - Modify qd_compose_insert_[string,symbol,binary] to
> > add zero-length [string, symbol, binary] for null input
> > DISPATCH-888 - Balanced distribution algorithm visits each link to
> > determine the best_eligible_link
> > DISPATCH-901 - add authz support to auth service plugin
> > DISPATCH-904 - Add charts to overview page
> > DISPATCH-918 - Improve router config consistency and metadata
> > DISPATCH-921 - Install console dependencies with npm during make
> > install
> > DISPATCH-923 - Clean up javascript to pass eslint tests without
> errors
> > DISPATCH-925 - Doc: Update anchor name format
> > DISPATCH-938 - Doc: Remove the "Configuration Reference"
> > DISPATCH-942 - allow resumable link routes to be refused
> > DISPATCH-946 - Detect if npm install needs to be executed and
> > display a message
> > DISPATCH-951 - log details for the proton found during build
> > DISPATCH-963 - Router crash during shutdown in
> > system_tests_distribution
> > DISPATCH-971 - Revert DISPATCH-744 - Don't reject unsettled
> multicasts
> > DISPATCH-972 - Dispatch Router doc should be consistent with "sudo"
> > usage
> >
> > Bug fixes -
> > DISPATCH-580 - Log stats should be graphable
> > DISPATCH-590 - List of log modules on the overview page is
> > occationally doubled
> > DISPATCH-801 - Stand-alone version of the console does not open at
> > all when running offline
> > DISPATCH-831 - Change conntector.cost default value to 1 instead of
> '1'
> > DISPATCH-869 - Multiple brokers in a topology are displayed as a
> > single broker
> > DISPATCH-875 - Document address and link route wildcards
> > DISPATCH-876 - config file linkRoute should use connection instead
> > of connector
> > DISPATCH-877 - Document how to configure TLS ciphers
> > DISPATCH-879 - Document how Dispatch Router uses alternate failover
> > URLs
> > DISPATCH-880 - Document how Dispatch Router disconnects connections
> > DISPATCH-886 - Console does not properly escape HTML in entity names
> > DISPATCH-891 - Router incref assert in system_tests_delivery_abort
> > DISPATCH-893 - Compile fails using libwebsockets 7
> > DISPATCH-894 - Unable to run system tests on CentOS 6 (Python 2.6)
> > DISPATCH-902 - Intermittent crash with link to broker when broker
> > closed
> > DISPATCH-905 - Dispatch Router not failing over to slave broker
> > when master broker goes away
> > DISPATCH-907 - cannot set address phase via qdmanage tool
> > DISPATCH-910 - Inter-router connections with dir 'in' have no host
> name
> > DISPATCH-912 - system_tests_user_id_proxy and system_tests_policy
> > failing
> > DISPATCH-915 - connection rhost  not calculated soon enough
> > DISPATCH-916 - qdmanage get-attributes and get-operations not
> > taking into account passed in type
> > DISPATCH-919 - Display a warning when running Dispatch tests if
> > python-unittest2 is not installed
> > DISPATCH-922 - Subsecond timestamps improperly formatted
> > DISPATCH-927 - detach not echoed back on multi-hop link route
> > DISPATCH-928 

Re: [VOTE] Release Apache Qpid JMS 0.32.0

[Jakub Scholz]

+1 ... I used the staging repo and run the new version against different
versions of the C++ broker. All seems to work fine.

On Mon, Apr 30, 2018 at 5:19 PM, Timothy Bish  wrote:

> On 04/30/2018 09:12 AM, Robbie Gemmell wrote:
>
>> Hi folks,
>>
>> I have put together a spin for a 0.32.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.32.0-rc1/
>>
>> The maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1139
>>
>> The JIRAs assigned are:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12314524=12342986
>>
>> 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-1139
>>  
>>
>>
>> The dependency for the client itself would then be:
>>
>>
>>  org.apache.qpid
>>  qpid-jms-client
>>  0.32.0
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>>
>>
> +1
>
> * Verified signatures and checksums
> * Verified license and notice files in the archives
> * Ran mvn apache-rat:check to scan for missing license headers
> * Reviewed the updated documentation
> * Build from source and ran the tests
> * Built Artemis master using staged binaries and ran all AMQP tests
> * Built ActiveMQ 5.x master using staged binaries and ran the
> 'activemq-amqp' modules test goal
> * Built the examples and ran them against ActiveMQ Artemis
>
>
> --
> Tim Bish
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Apache Qpid C++ 1.38.0

[Jakub Scholz]

+1 ... I build it from source on CentOS 7 and checked it against different
clients.

On Fri, Mar 23, 2018 at 3:40 PM, Timothy Bish  wrote:

> +1
>
> * Validated signatures and checksums
> * Built from source and ran the tests
>
>
> On 03/23/2018 08:45 AM, Robbie Gemmell wrote:
>
>> On 22 March 2018 at 12:33, Justin Ross  wrote:
>>
>>> Hi, all.  Please test this release candidate and indicate your vote on
>>> this
>>> thread.
>>>
>>> Source archive and signatures:
>>> https://dist.apache.org/repos/dist/dev/qpid/cpp/1.38.0-rc1/
>>>
>>> Issues:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>>> ctId=12310520=12340228
>>>
>>> Tag:
>>> 1.38.0-rc1
>>>
>> +1
>>
>> Checked thigns out as follows:
>> - Verified signature and checksum files.
>> - Checked for LICENCE+NOTICE files.
>> - Ran the source build against proton-0.21.0, ran the tests, all passed.
>> - Ran the qpid-jms 0.31.0 (RC1) HelloWorld example against the built
>> broker.
>>
>> Robbie
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>>
>>
> --
> 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
>
>

Re: [VOTE] Release Apache Qpid Proton 0.21.0

[Jakub Scholz]

+1. I have build it from source and used it with C++ broker and different
clients.

On Sun, Mar 4, 2018 at 4:37 AM, Roddie Kieley  wrote:

> +1 (advisory)
>
> - checked out the tag 0.21.0-rc1
> - Built on OSX 10.11.6 w/Xcode 7.3.1 command line tools without ruby or
> valgrind
> -- Tested with go-test failure related to open PROTON-1695 and potentially
> closed PROTON-1655
> - Built and Installed using updated Portfile for MacPorts net/qpid-proton
> -- Built installed c examples; ran receive and send successfully
> -- Built installed cpp examples; ran simple_recv and simple_send
> successfully
>
> On Wed, Feb 28, 2018 at 4:03 PM, Robbie Gemmell 
> wrote:
>
> > Hi folks,
> >
> > I have put together a spin for a Qpid Proton 0.21.0 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.21.0-rc1/
> >
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12313720=12342274
> >
> > It is tagged as 0.21.0-rc1.
> >
> > Regards,
> > Robbie
> >
> > -
> > 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.30.0

[Jakub Scholz]

+1 ... I used the staging repo and run tests against different versions of
the C++ broker (including master)

On Mon, Feb 26, 2018 at 1:18 PM, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.30.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.30.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1131
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12314524=12342544
>
> 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-1131
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.30.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

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

[Jakub Scholz]

+1 ... I built it from source on CentOS 7 and run it against different AMQP
clients.

On Tue, Feb 20, 2018 at 9:27 PM, Ted Ross  wrote:

> Please vote on this thread to release qpid-dispatch 1.0.1-rc1 as the
> official 1.0.1.
>
> The release can be found here:
>
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.0.1-rc1/
>
> The following defects were fixed in this release:
>
> DISPATCH-874 - unable to load .json or .woff2 files from local
> file system from http port
> DISPATCH-881 - Inbound pre-settled messages causes memory leak of
> deliveries
> DISPATCH-882 - router buffers messages for slow presettled receiver
> DISPATCH-883 - Router crashes when it processes management request
> for connections
> DISPATCH-887 - Dispatch reestablishes connection inspite of
> deleting the connector
> DISPATCH-889 - linkRoute patterns beginning with #/string match
> substrings after the /
> DISPATCH-895 - qpid-dispatch crashes with a SEGFAULT in libqpid-proton
> DISPATCH-900 - Memory leak when repeatedly opening and closing
> connections
> DISPATCH-908 - Router loses dispositions over receive link on
> qpid-interop-test 2-node test
> DISPATCH-914 - qd_connector_t leaks mutexes
> DISPATCH-920 - Enabled policy blocks inter-router links
>
> -
> 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.20.0

[Jakub Scholz]

+1 ... I build it from source and used it with C++ broker and Dispatch.

On Sun, Jan 28, 2018 at 11:36 PM, Keith Wall  wrote:

> +1
>
> 1) Built from source bundle and ran unit tests on Ubuntu 16.04.3 (VM)
> 2) Executed cpp command line examples against Broker-J (master)
>
>
> On 26 January 2018 at 16:53, Ken Giusti  wrote:
> > +1
> >
> > Tested on Ubuntu 16.04 VM:
> >
> > 1) build and unit test pass
> > 2) oslo.messaging unit and functional tests pass (qpidd and qdrouterd)
> > 3) pyngus unit tests pass
> >
> >
> > On Thu, Jan 25, 2018 at 7:46 AM, Robbie Gemmell <
> robbie.gemm...@gmail.com>
> > wrote:
> >
> >> Hi folks,
> >>
> >> I have put together a spin for a Qpid Proton 0.20.0 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.20.0-rc1/
> >>
> >> The JIRAs currently assigned are:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> projectId=12313720=12342219
> >>
> >> It is tagged as 0.20.0-rc1.
> >>
> >> Regards,
> >> Robbie
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> >> For additional commands, e-mail: users-h...@qpid.apache.org
> >>
> >>
> >
> >
> > --
> > -K
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: qpid-tool (QMF) filters

[Jakub Scholz]

Hi Jan,

This is an example which I found in my notes:
call 120 queueMoveMessages SrcQueue DstQueue 10
{"filter_type":"header_match_str","filter_params":{"header_key":"qpid.subject","header_value":"key1"}}

I haven't used it for some time, but give it a try, I think it should still
work.

Thanks & Regards
Jakub

On Wed, Jan 24, 2018 at 5:39 PM, Jan Bares, WOOD & Co. 
wrote:

> Hi,
>
> I need some pointers on what I can write into filter parameter of
> qpid-tool call. I am able to list all methods with "schema xy". I want to
> "call reroute" or "call queueMoveMessages" with filter.
>
> Many thanks, Jan
>
> Jan Bares
> Calypso / Java Lead Developer
>
> Hradecka 10
> Czech Republic
> Mobile: +420 776 333 676
>
> In association with
> WOOD & Company Financial Services, a.s.
> http://www.wood.cz
>
>
>
> DISCLAIMER
> 
>  WOOD & Company Financial Services, a.s. and its branches are
> authorized and regulated by the CNB as Home State regulator and in Poland
> by the KNF, in Slovakia by the NBS, in Italy by the CONSOB and in the UK by
> the FCA as Host State regulators. For further information about WOOD & Co.,
> its investment services, financial instruments and associated risks,
> safeguard client assets (incl. compensation schemes) and contractual
> relationship please see our website at www.wood.com
> under section Corporate Governance.
>  Unless otherwise stated, this transmission is neither an offer
> nor the solicitation of an offer to sell or purchase any investment. All
> estimates, opinions and other information contained herein are subject to
> change without notice and are provided in good faith but without legal
> responsibility or liability. Opinion may be personal to the author and may
> not reflect the opinions of WOOD & Co. Communications from sales persons,
> sales traders or traders should not be regarded as investment research and
> may contain opinions or trading ideas which are different from WOOD & Co.
> investment research opinions.
>  This e-mail and any attachments are confidential and may be
> privileged or otherwise protected from disclosure. If you are not a named
> addressee you must not use, disclose, distribute, copy, print or rely on
> this e-mail and any of its attachments. Please notify the sender that you
> have received this email by mistake by replying to the email, and then
> delete the email and any copies of it. Although WOOD & Co. routinely
> screens e-mails for viruses, addressees should scan this e-mail and any
> attachments for viruses. WOOD & Co. makes no representation or warranty as
> to the absence of viruses in this e-mail or any attachments. Please note
> that to ensure regulatory compliance and for the protection of our clients
> and business, we may monitor and read e-mails sent to and from our
> server(s).
> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: C++ broker QMF GUI

[Jakub Scholz]

Hi Jan,

The QMF GUI source code can be found here:
https://github.com/apache/qpid/tree/trunk/qpid/tools/src/java

I think it should still work, but I think it wasn't touched for quite a
long time.

Regards
Jakub

On Thu, Jan 18, 2018 at 11:27 AM, Jan Bares, WOOD & Co. 
wrote:

> Hi,
>
> There used to be javascript single page QMF GUI for C++ broker some years
> ago, is it still in development? Where can I find it? The Java broker has
> its management console, but it seems to be baked into the broker.
>
> Kind regards, Jan
>
> Jan Bares
> Calypso / Java Lead Developer
>
> Hradecka 10
> Czech Republic
> Mobile: +420 776 333 676
>
> In association with
> WOOD & Company Financial Services, a.s.
> http://www.wood.cz
>
>
>
> DISCLAIMER
> 
>  WOOD & Company Financial Services, a.s. and its branches are
> authorized and regulated by the CNB as Home State regulator and in Poland
> by the KNF, in Slovakia by the NBS, in Italy by the CONSOB and in the UK by
> the FCA as Host State regulators. For further information about WOOD & Co.,
> its investment services, financial instruments and associated risks,
> safeguard client assets (incl. compensation schemes) and contractual
> relationship please see our website at www.wood.com
> under section Corporate Governance.
>  Unless otherwise stated, this transmission is neither an offer
> nor the solicitation of an offer to sell or purchase any investment. All
> estimates, opinions and other information contained herein are subject to
> change without notice and are provided in good faith but without legal
> responsibility or liability. Opinion may be personal to the author and may
> not reflect the opinions of WOOD & Co. Communications from sales persons,
> sales traders or traders should not be regarded as investment research and
> may contain opinions or trading ideas which are different from WOOD & Co.
> investment research opinions.
>  This e-mail and any attachments are confidential and may be
> privileged or otherwise protected from disclosure. If you are not a named
> addressee you must not use, disclose, distribute, copy, print or rely on
> this e-mail and any of its attachments. Please notify the sender that you
> have received this email by mistake by replying to the email, and then
> delete the email and any copies of it. Although WOOD & Co. routinely
> screens e-mails for viruses, addressees should scan this e-mail and any
> attachments for viruses. WOOD & Co. makes no representation or warranty as
> to the absence of viruses in this e-mail or any attachments. Please note
> that to ensure regulatory compliance and for the protection of our clients
> and business, we may monitor and read e-mails sent to and from our
> server(s).
> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Status monitoring

[Jakub Scholz]

How do you plan to implement this: "Before the shutdown the sensor remove
its entry from the queue."?

If you plan to have large amount of sensors (= a lot of messages in the
StatusOverview queue) which would shutdown often, finding and accepting the
particular message might not be the optimal way to do this. So maybe you
can instead send a message which would contain in the properties or body
the information that the sensor is shutting down. It would overwrite the
previous status and later expire and be removed automatically.

Regards
Jakub

On Sun, Jan 14, 2018 at 2:46 PM, Daniel Gavrila <d.gavr...@icloud.com>
wrote:

>
> These are good news!
> I think I'm able now to translate the use case scenario in "AMQP  language"
>
> Each sensor publish a durable message with TTL=N seconds to the LVQ
> durable queue StatusOverview  every N seconds.
> Each GUI  client read the queue OverviewStatus in browse mode.
> Before the shutdown the sensor remove its entry from the queue.
> If a abnormal exit occurs the queue will remove the entry after maxim N
> seconds
>
> I have one more general question. Which relation is between qpid-config
> and the qpid::messaging API ? Everything that can be done with qpid-config
> can be done also with the API ?
>
> Best regards,
> Daniel
>
>
> > On 13.01.2018, at 17:23, Jakub Scholz <ja...@scholz.cz> wrote:
> >
> > The LVQ queue is able to persist these messages to disk like any other
> > queue. So they can survive restart.
> >
> > Jakub
> >
> > On Sat, Jan 13, 2018 at 4:55 PM, Daniel Gavrila <d.gavr...@icloud.com>
> > wrote:
> >
> >> Hello Andreas,
> >>
> >> Thanks for the suggestion.From what I read from documentation, indeed a
> >> last value queue should cover a signifiant part of use case
> >> scenario.Remains the question if the values from a LVQ could be make
> >> persistent, so that will be recovered after a broker restart?
> >>
> >> Best regards,
> >> Daniel
> >>
> >>
> >>> On 13.01.2018, at 12:55, Andreas Welchlin <andr...@welchlin.de> wrote:
> >>>
> >>> Hello Daniel,
> >>>
> >>> this should work using a last value queue.
> >>>
> >>> Kind Regards,
> >>> Andreas
> >>>
> >>> Am 13. Januar 2018 12:19:57 MEZ schrieb Daniel Gavrila <
> >> d.gavr...@icloud.com>:
> >>>>
> >>>>
> >>>> Hello,
> >>>>
> >>>> My environment is:
> >>>> C++ Proton v. 0.19
> >>>> C++ Broker v.1.37 configured with AMQP 1.0
> >>>>
> >>>> I have to implement the following use case scenario. The network
> >> contains N publishers(sensors) . When one sensor starts it publish to
> the
> >> queue OverviewStatus one message that contains some data: sensor
> >> name,type,internal status etc. One GUI program has to display the
> >> information from the queue OverviewStatus. Everytime the sensor changes
> its
> >> internal status he needs to update the status in the queue.Before the
> >> shutdown , the sensor has to remove its entry from the queue.
> >>>> If the sensor exits anormaly the event should be catched and the
> sensor
> >> status modified accordingly. By restarting the broker, all the sensors
> >> status information should be recovered.
> >>>>
> >>>> Is it possibly to implement such use case in the above mentioned
> >> environment? Any suggestions are welcomed !
> >>>>
> >>>> Many thanks,
> >>>> Daniel
> >>
>

Re: Status monitoring

[Jakub Scholz]

The LVQ queue is able to persist these messages to disk like any other
queue. So they can survive restart.

Jakub

On Sat, Jan 13, 2018 at 4:55 PM, Daniel Gavrila 
wrote:

> Hello Andreas,
>
> Thanks for the suggestion.From what I read from documentation, indeed a
> last value queue should cover a signifiant part of use case
> scenario.Remains the question if the values from a LVQ could be make
> persistent, so that will be recovered after a broker restart?
>
> Best regards,
> Daniel
>
>
> > On 13.01.2018, at 12:55, Andreas Welchlin  wrote:
> >
> > Hello Daniel,
> >
> > this should work using a last value queue.
> >
> > Kind Regards,
> > Andreas
> >
> > Am 13. Januar 2018 12:19:57 MEZ schrieb Daniel Gavrila <
> d.gavr...@icloud.com>:
> >>
> >>
> >> Hello,
> >>
> >> My environment is:
> >>  C++ Proton v. 0.19
> >>  C++ Broker v.1.37 configured with AMQP 1.0
> >>
> >> I have to implement the following use case scenario. The network
> contains N publishers(sensors) . When one sensor starts it publish to the
> queue OverviewStatus one message that contains some data: sensor
> name,type,internal status etc. One GUI program has to display the
> information from the queue OverviewStatus. Everytime the sensor changes its
> internal status he needs to update the status in the queue.Before the
> shutdown , the sensor has to remove its entry from the queue.
> >> If the sensor exits anormaly the event should be catched and the sensor
> status modified accordingly. By restarting the broker, all the sensors
> status information should be recovered.
> >>
> >> Is it possibly to implement such use case in the above mentioned
> environment? Any suggestions are welcomed !
> >>
> >> Many thanks,
> >> Daniel
> >>
> >>
> >>
>

Re: [VOTE] Release Apache Qpid JMS 0.28.0

[Jakub Scholz]

+1 ... I used the staging repo and run my tests against different version
of the C++ broker (including master).

On Mon, Dec 11, 2017 at 8:30 PM, Robbie Gemmell 
wrote:

> On 11 December 2017 at 18:21, Robbie Gemmell 
> wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.28.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.28.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1126
> >
> > The JIRAs currently assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12314524=12342125
> >
> > 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-1126
> > 
> >   
> >
> > The dependency for the client itself would then be:
> >
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 0.28.0
> >   
>
> +1
>
> I checked things over as follows:
> - Verified the signature and checksum files.
> - Checked the LICENCE+NOTICE files in src + bin archives.
> - Ran mvn apache-rat:check to verify licence headers in the src archive.
> - Ran the source build and tests, no issues.
> - Built the examples using the staging repo and ran HelloWorld against
>   Qpid Broker-J, Qpid Dispatch, and ActiveMQ 5 built from master.
> - Used Qpid Broker-J master to run the joram tests using the staging repo.
> - Used the staging repo with the ActiveMQ 5 + Artemis master builds +
> tests.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Apache Qpid Python 1.37.0

[Jakub Scholz]

+1 ... I run my tests against different versions of Qpid C++ broker

On Wed, Nov 22, 2017 at 9:10 PM, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a Qpid Python 1.37.0 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/python/1.37.0-rc1/
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310520=12339780
>
> It is tagged as 1.37.0-rc1.
>
> Regards,
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Are senders anonymous using AMQP 1.0 through a broker?

[Jakub Scholz]

In that case it depends mainly on your clients which are sending the
messages. The broker doesn't set this field. It only validates it in case
it is set by the client. So depending on your client library there might be
some on/off switch or you might be able to set the user-id property to null
etc. For example in Qpid JMS client the setting "jms.populateJMSXUserID"
should do the trick (switched off by default).

JAkub

On Wed, Nov 22, 2017 at 9:04 AM, andi welchlin <andi.welch...@gmail.com>
wrote:

> Hello Jakub,
>
> thank you for your answer.
>
> My use case is the other way around. I would like senders to be anonymous.
> The idea is to communicate via an exchange but it should not be possible -
> even with a network sniffer - to identify the sender.
>
> Kind Regards
> Andreas
>
>
>
> On Tue, Nov 21, 2017 at 6:23 PM, Jakub Scholz <ja...@scholz.cz> wrote:
>
> > AFAIK the AMQP message has a property called user-id. This can be set by
> > the client and the broker would verify that if it is set it contains the
> > user-id of the connected user and not some other user-id. So you can use
> it
> > to identify the sender. However, some clients simply leave it empty (and
> > sometimes it is not trivial to know the identity under which you are
> > connected to the broker). So in some cases the sender would need to set
> it
> > explicitely.
> >
> > I personally always tried to configure the brokers in a way that the
> > messages from different users never crossed their path - they always used
> > different queues, exchanges etc. Thanks to that I was able to identify
> the
> > sender of the message for example based on the queue from which my
> received
> > got the message. But this trick can be used only in some scenarios.
> >
> > I never used federation, so I cannot help with the second case.
> >
> > What is your use case for knowing the sender user id? Do you need it for
> > some security purposes?
> >
> > Jakub
> >
> > On Tue, Nov 21, 2017 at 5:48 PM, andi welchlin <andi.welch...@gmail.com>
> > wrote:
> >
> > > Hello all,
> > >
> > > I was asking myself if the messages which go through QPID brokers are
> > > anonymous so that you can not find out who the sender was.
> > >
> > > I speak about AMQP 1.0.
> > >
> > > First Case (one broker):
> > > If a producer sends a message to a QPID broker and a consumer is
> > receiving
> > > it. Is it possible for the consumer to see who the publisher of the
> > message
> > > was? Any ip-address or something like this? Are there any sender
> specific
> > > application properties?
> > >
> > > Second Case (broker federation):
> > > If there was a federation of two brokers: Would a consumer of a message
> > on
> > > the second broker be able to see that the message came through the
> first
> > > broker?
> > >
> > > Kind Regards,
> > > Andreas
> > >
> >
>

Re: [VOTE] Release Apache Qpid CPP 1.37.0

[Jakub Scholz]

+1 ... I built it from source and run different AMQP 0-10 and 1.0 clients
against the broker. All seems to work fine.

On Tue, Nov 21, 2017 at 10:51 PM, Timothy Bish  wrote:

> On 11/21/2017 01:20 PM, Robbie Gemmell wrote:
>
>> Hi folks,
>>
>> I have put together a spin for a Qpid CPP 1.37.0 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/cpp/1.37.0-rc1/
>>
>> The JIRAs currently assigned are:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12310520=12338808
>>
>> It is tagged as 1.37.0-rc1.
>>
>> Regards,
>> Robbie
>>
>> -
>> 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 valid license and notice files
> * Built from source and installed the result
> * Ran the broker and executed some of the samples as well as some other
> client tests against it
> * Ran some of the client examples against an ActiveMQ Artemis broker
>
>
> --
> 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
>
>

Re: Are senders anonymous using AMQP 1.0 through a broker?

[Jakub Scholz]

AFAIK the AMQP message has a property called user-id. This can be set by
the client and the broker would verify that if it is set it contains the
user-id of the connected user and not some other user-id. So you can use it
to identify the sender. However, some clients simply leave it empty (and
sometimes it is not trivial to know the identity under which you are
connected to the broker). So in some cases the sender would need to set it
explicitely.

I personally always tried to configure the brokers in a way that the
messages from different users never crossed their path - they always used
different queues, exchanges etc. Thanks to that I was able to identify the
sender of the message for example based on the queue from which my received
got the message. But this trick can be used only in some scenarios.

I never used federation, so I cannot help with the second case.

What is your use case for knowing the sender user id? Do you need it for
some security purposes?

Jakub

On Tue, Nov 21, 2017 at 5:48 PM, andi welchlin 
wrote:

> Hello all,
>
> I was asking myself if the messages which go through QPID brokers are
> anonymous so that you can not find out who the sender was.
>
> I speak about AMQP 1.0.
>
> First Case (one broker):
> If a producer sends a message to a QPID broker and a consumer is receiving
> it. Is it possible for the consumer to see who the publisher of the message
> was? Any ip-address or something like this? Are there any sender specific
> application properties?
>
> Second Case (broker federation):
> If there was a federation of two brokers: Would a consumer of a message on
> the second broker be able to see that the message came through the first
> broker?
>
> Kind Regards,
> Andreas
>

Re: [VOTE] Release Qpid Dispatch Router 1.0.0 (RC3)

[Jakub Scholz]

+1 ... I built it from source and run some of my tests with different AMQP
1.0 clients as well as against the Qpid C++ broker.

Jakub

On Tue, Nov 14, 2017 at 2:01 PM, Ted Ross  wrote:

> Please cast your vote on this thread to release RC3 as the official Qpid
> Dispatch Router version 1.0.0.
>
> Qpid Dispatch Router 1.0.0 RC3 can be found here:
>
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.0.0-rc3/
>
> The following issues have been fixed since RC1:
>
> DISPATCH-767 - Message Cut-Through/Streaming for efficient handling of
> large messages
> DISPATCH-847 - Fix issues discovered by Coverity
> DISPATCH-858 - Simplify hard to follow LICENSE file
> DISPATCH-865 - Segmentation fault while running 2-node Artemis tests
> DISPATCH-867 - Messages stuck going through link route
> DISPATCH-870 - connection improperly reopened from closed connector
> DISPATCH-873 - new routes calculated wrongly after connector deletion
>
> The following features, improvements, and bug fixes are introduced in
> 1.0.0:
>
> Features:
>
> DISPATCH-390 - New pn_proactor-based IO driver
> DISPATCH-731 - Support wildcard tenant vhosts in address prefix
> configuration
> DISPATCH-767 - Message Cut-Through/Streaming for efficient handling of
> large messages
> DISPATCH-775 - allow authentication against a remote server
> DISPATCH-803 - refuse attach to undefined addresses
> DISPATCH-813 - Support wildcard format for link-routes
> DISPATCH-818 - Honor failoverList provided by connected brokers
> DISPATCH-844 - Make TLS cipher suites configurable
>
> Improvements:
>
> DISPATCH-209 - Three+ router test is needed in the system test suite.
> DISPATCH-525 - What are proper names and units for protocol
> configuration settings?
> DISPATCH-551 - disconnect connections that do not complete initial
> protocol handshake within a given time
> DISPATCH-584 - Large, highly redundant router networks generate
> excessive inter-router message traffic
> DISPATCH-744 - Reject unsettled deliveries to multicast addresses by
> default
> DISPATCH-770 - Show error if creating an entity using web console fails
> DISPATCH-771 - Mark mandatory fields when creating a new entity in the
> web console
> DISPATCH-788 - Create peer linkage for presettled deliveries so we can
> use this to handle muticast dispositions
> DISPATCH-795 - Sort entity names on Schema page to make them easier to
> find
> DISPATCH-796 - The Python and the C management agents do not have an
> AMQP header in their responses.
> DISPATCH-809 - Add options to enable Sanitizers to CMake build
> DISPATCH-827 - Large message discard buffer too small
> DISPATCH-828 - Discarded message processing does not close callback
> window
> DISPATCH-839 - Improve the batching of allocated objects
> DISPATCH-858 - Simplify hard to follow LICENSE file
>
> Bugs Fixed:
>
> DISPATCH-421 - Toasts messages are not logged in the rolldown "logging
> console"
> DISPATCH-430 - Cursor snaps way above peaks in a rate chart
> DISPATCH-571 - Driver spins when a listener accepts a socket while FDs
> are all in use
> DISPATCH-737 - qdstat and qdmanage always force sasl exchange
> DISPATCH-741 - Coverity scan reported errors in Qpid Dispatch master
> DISPATCH-743 - Intermittent SSL Failure
> DISPATCH-747 - Console does not handle connection errors well
> DISPATCH-748 - Error message shown when rapidly clicking treeview on
> left side of hawtio console: Uncaught TypeError: Cannot read property
> 'height' of null
> DISPATCH-749 - unmapping all link-routing addresses leaves half of
> addresses mapped
> DISPATCH-750 - Missing icons and bad rendering of dynatree treeviews in
> Microsoft Edge 14
> DISPATCH-752 - With more than one outbound SSL connections, failure in
> one affects all others
> DISPATCH-753 - Neither version of console is usable on Internet
> Explorer 10 or 11
> DISPATCH-754 - Output of qdstat shows authentication on client SSL
> connections as anonymous (x.509)
> DISPATCH-756 - Fix Fedora and Ubuntu docker files to use libuv and
> libwebsockets
> DISPATCH-757 - Qpid Dispatch does not compile under Ubuntu
> DISPATCH-758 - test_listen_error() in system_tests_one_router.py and
> system_tests_http.py hang inside a docker environment
> DISPATCH-759 - Core thread consumed deleting deliveries
> DISPATCH-761 - Router crash on abrupt close of sender/receiver
> connections
> DISPATCH-762 - Hawtio console does not show details about a connection
> whereas stand-alone console does
> DISPATCH-763 - Router crashes when config file defines listener { addr:
> } instead of { host: }
> DISPATCH-765 - Three unit tests failing under travis on trusty
> DISPATCH-766 - Update Dockerfile-ubuntu to include libwebsockets
> DISPATCH-768 - On topology page, show connections that go to more than
> one router
>  

Re: [VOTE] Release Apache Qpid JMS AMQP 0-x 6.3.0

[Jakub Scholz]

+1 ... I used the staging repo and run my tests against different versions
of Qpid C++ broker.

Jakub

On Wed, Nov 15, 2017 at 4:59 PM, Oleksandr Rudyy  wrote:

> Hi all,
>
> I built a candidate release for version 6.3.0 of Qpid JMS AMQP 0-x.
>
> Please test and vote accordingly.
>
> The source and binary archives can be taken from:
> https://dist.apache.org/repos/dist/dev/qpid/jms-amqp-0-x/6.3.0/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1123
>
> The JIRAs currently assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12339957
>
> Regards,
> Alex
>
> 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-1123
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-client
> 6.3.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

Re: ACL rules for Qpid C++ Broker

[Jakub Scholz]

Hi Andreas,

The problem is that in qpidd you never publish directly to queue or read
directly from an exchange. You always publish to exchange and read from a
queue. In reality what you see as publishing directly to an queue is
sending the message to an exchange named "" (as in empty string) with a
routing key which should be the name of your queue. The same when you try
to read directly from an exchange the client acutally creates a queue and a
binding to the exchange for you. That is why the ACL rules such as "publish
queue" or "consume exchange" do not exist.

In your case ... if your group wants to publish to queue name QU1, you
should add a rule which looks something like this:
acl allow group1 publish exchange name=amq.default routingkey=QU1
where the exchange name "amq.default" will be substituted for the exchange
without name (as per https://issues.apache.org/jira/browse/QPID-4727)

To read directly from an exchange you need several ACL rights:
- to create a queue
acl allow group1 create queue name=*
- to delete a queue when you are closing the connection
acl allow group1 delete queue name=*
- to consume from the queue
acl allow group1 consume queue name=*
- to bind the exchange
acl allow group1 bind exchange name=EX1

Depending on your client you might be able to specify the queue name in
more detail. For example the qpid-receive client (using the old Qpid C++
API) would create the queue named similar to
"EX1_8f4ea08f-d211-41c0-97cf-652cd5ef9a11". But different clients might do
it differently.

Hope this helps.

Jakub


On Fri, Nov 10, 2017 at 3:46 PM, andi welchlin 
wrote:

> Hello everyone,
>
> I looked into ACL documentation of Qpid C++ broker (1.36.0) and tested it a
> bit.
>
>
> I would like to allow for one usergroup to write to a queue with a specific
> name, but deny it for all other users.
>
> But I saw that i can not do the following:
>
> acl allow group1 publish queue name=QU1
>
>
> I understood that the publish keyword can only be used for exchanges.
>
>
> I also would like to restrict reading from an exchange with a specific name
> and allow it only for one usergroup.
>
> But the following seems also not to be allowed:
>
> acl allow group1 consume exchange name=EX1
>
>
> "consume" is only allowed for queues.
>
>
> How can I reach these two requirements?
>
>
> Kind Regards,
> Andreas
>

Re: [VOTE] Release Apache Qpid JMS 0.27.0

[Jakub Scholz]

+1 ... I used the staging repo and run my tests against different versions
of Qpid C++ broker.

On Wed, Nov 1, 2017 at 6:56 PM, Robbie Gemmell 
wrote:

> On 1 November 2017 at 16:37, 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=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
> >   
>
> +1
>
> I tested things as follows:
> - Verified the signature and checksum files.
> - Checked LICENCE+NOTICE files in the src and bin archives.
> - Used mvn apache-rat:check to verify licence headers in the src archive.
> - Ran the source build and tests.
> - Built the examples using the staging repo and ran HelloWorld against
> Qpid Dispatch master, Qpid CPP master, and ActiveMQ 5 master.
> - Ran the ActiveMQ 5 master build and AMQP tests using the staging repo
> bits.
>
> Robbie
>
> -
> 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.0

[Jakub Scholz]

+1. I build it from source code and used it with Qpid C++ broker (master)
and Qpid Dispatch (1.0.0 RC1) and run my tests against them. All seems to
work fine.

On Wed, Oct 18, 2017 at 7:29 PM, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a first spin for a Qpid Proton 0.18.0 release,
> please test it and vote accordingly.
>
> The source archive can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.18.0-rc1/
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12313720=12338903
>
> It is tagged as 0.18.0-rc1.
>
> Regards,
> Robbie
>
> -
> 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.26.0

[Jakub Scholz]

+1. I used the staged jars and run them against different versions of the
C++ broker (master, 1.36, 1.35 and 0.34). All looks OK.

On Wed, Oct 4, 2017 at 10:12 PM, Gordon Sim  wrote:

> On 04/10/17 12:35, Robbie Gemmell wrote:
>
>> I have put together a spin for a 0.26.0 Qpid JMS client release, please
>> give it a test out and vote accordingly.
>>
>
> +1
>
> (Built binary tarball from source including running tests, installed and
> ran example against both brokers and the router).
>
>
> -
> 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.25.0

[Jakub Scholz]

+1 ... used the staged artifacts and run my tests against different
versions of Qpid C++ broker (including the latest master).

On Mon, Sep 18, 2017 at 9:02 PM, Timothy Bish  wrote:

> On 09/18/2017 12:45 PM, Robbie Gemmell wrote:
>
>> Hi folks,
>>
>> I have put together a spin for a 0.25.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.25.0-rc1/
>>
>> The maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1115
>>
>> The JIRAs currently assigned are:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12314524=12341292
>>
>> 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-1115
>>  
>>
>>
>> The dependency for the client itself would then be:
>>
>>
>>  org.apache.qpid
>>  qpid-jms-client
>>  0.25.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 bin and src archives for proper license and notice files
> * Built from source and ran the tests
> * Checked for license issues using 'mvn apache-rat:check'
> * Used the staged artifacts in ActiveMQ 5.x to build and run all AMQP tests
> * Used the staged artifacts in Artemis to build and run all AMQP tests
> * Ran the example from the src archive against a running 5.x broker.
>
>
> --
> 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
>
>

Re: Address options grammar

[Jakub Scholz]

Yeah, you are right. If you use the constructor the type from options is
ignored. Looking at the code it seems this is because the constructor first
uses the options and afterwards overwrites the type with the empty string
passed as a type (see
https://github.com/apache/qpid-cpp/blob/49e3afbc62f6fbb361e830b1e4baa77a046ac718/src/qpid/messaging/Address.cpp#L45-L47).
So if yo want to use the constructor you can do so, but don't specify the
type in the options but use the type field for it instead. That seems to
work fine.

I think this can be easily fixed by creating second constructor without the
type.

Jakub

On Sat, Aug 26, 2017 at 10:02 PM, Chris Richardson <c...@fourc.eu> wrote:

> I was using the Address constructor
>
> Address(const std::string& name, const std::string& subject,
>const qpid::types::Variant::Map& options,
> const std::string& type = "");
>
> to provide the name and options. It seems the behaviour is not the same
> though as your method also works for me. Problem solved, thanks very much
> :)
>
> C
>
> On 26 August 2017 at 14:30, Jakub Scholz <ja...@scholz.cz> wrote:
>
> > How exactly do you create the address and what do you have in you client
> /
> > broker log?
> >
> > When I try to do something like this:
> > Address myAddress;
> > Variant::Map options;
> > Variant::Map selector;
> > selector["selector"] = "color='blue'";
> > options["link"] = selector;
> > Variant::Map node_type;
> > node_type["type"] = "queue";
> > options["node"] = node_type;
> > options["assert"] = "always";
> > myAddress.setOptions(options);
> > myAddress.setName("myTest");
> >
> > For me it seems to work properly. The client log correctly creates the
> > address:
> > 2017-08-26 13:28:14 [Client] debug treating source address as queue:
> > myTest;{assert:always, link:{selector:color='blue'}, node:{type:queue}}
> > The client sends only QueueDeclare and QueueQuery and the only ACL right
> > needed seem to be queue/access and queue/consume.
> >
> > Regards
> > Jakub
> >
> > On Sat, Aug 26, 2017 at 1:08 PM, Chris Richardson <c...@fourc.eu> wrote:
> >
> > > Hi,
> > >
> > > Using the qpid-cpp-1.36 broker/client I am trying to specify two
> clauses
> > on
> > > a receiver node (queue) address; one is a selector and looks something
> > like
> > > this:
> > >
> > > Variant::Map options;
> > > Variant::Map selector;
> > > selector["selector"] = "";
> > > options["link"] = selector;
> > >
> > > the other is a node type specification and looks like
> > >
> > > Variant::Map node_type;
> > > node_type["type"] = "queue";
> > > options["node"] = node_type; // using "options" from previous example
> > > options["assert"] = "always";
> > >
> > > Either one of these works on their own, but when combined the second
> > clause
> > > seems to be ignored and an attempt to access the queue name as an
> > exchange
> > > is made, which gets denied by the ACL.
> > >
> > > Am I doing something nonsensical like trying to combine
> > > AMQP-0.10/AMQP-1.0/JMS grammar? Ref:
> > > https://qpid.apache.org/releases/qpid-cpp-1.36.0/
> > > messaging-api/book/section-addresses.html,
> > > it appears that the "selector" keyword does not exist at all - my use
> of
> > > this is based on this previous question
> > > http://qpid.2158936.n2.nabble.com/Property-names-in-
> > > subscription-selectors-td7625162.html#a7625166
> > > (and nested links).
> > >
> > > Some clarification would be much appreciated!
> > >
> > > Chris
> > >
> > > --
> > >
> > > *Chris Richardson*, System Architect
> > > c...@fourc.eu
> > >
> > >
> > > *FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller,
> > Norwaywww.fourc.eu
> > > <http://www.fourc.eu/>*
> > >
> > > *Follow us on LinkedIn <http://bit.ly/fourcli>, Facebook
> > > <http://bit.ly/fourcfb>, Google+ <http://bit.ly/fourcgp> and Twitter
> > > <http://bit.ly/fourctw>!*
> > >
> >
>
>
>
> --
>
> *Chris Richardson*, System Architect
> c...@fourc.eu
>
>
> *FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu
> <http://www.fourc.eu/>*
>
> *Follow us on LinkedIn <http://bit.ly/fourcli>, Facebook
> <http://bit.ly/fourcfb>, Google+ <http://bit.ly/fourcgp> and Twitter
> <http://bit.ly/fourctw>!*
>

Re: Address options grammar

[Jakub Scholz]

How exactly do you create the address and what do you have in you client /
broker log?

When I try to do something like this:
Address myAddress;
Variant::Map options;
Variant::Map selector;
selector["selector"] = "color='blue'";
options["link"] = selector;
Variant::Map node_type;
node_type["type"] = "queue";
options["node"] = node_type;
options["assert"] = "always";
myAddress.setOptions(options);
myAddress.setName("myTest");

For me it seems to work properly. The client log correctly creates the
address:
2017-08-26 13:28:14 [Client] debug treating source address as queue:
myTest;{assert:always, link:{selector:color='blue'}, node:{type:queue}}
The client sends only QueueDeclare and QueueQuery and the only ACL right
needed seem to be queue/access and queue/consume.

Regards
Jakub

On Sat, Aug 26, 2017 at 1:08 PM, Chris Richardson  wrote:

> Hi,
>
> Using the qpid-cpp-1.36 broker/client I am trying to specify two clauses on
> a receiver node (queue) address; one is a selector and looks something like
> this:
>
> Variant::Map options;
> Variant::Map selector;
> selector["selector"] = "";
> options["link"] = selector;
>
> the other is a node type specification and looks like
>
> Variant::Map node_type;
> node_type["type"] = "queue";
> options["node"] = node_type; // using "options" from previous example
> options["assert"] = "always";
>
> Either one of these works on their own, but when combined the second clause
> seems to be ignored and an attempt to access the queue name as an exchange
> is made, which gets denied by the ACL.
>
> Am I doing something nonsensical like trying to combine
> AMQP-0.10/AMQP-1.0/JMS grammar? Ref:
> https://qpid.apache.org/releases/qpid-cpp-1.36.0/
> messaging-api/book/section-addresses.html,
> it appears that the "selector" keyword does not exist at all - my use of
> this is based on this previous question
> http://qpid.2158936.n2.nabble.com/Property-names-in-
> subscription-selectors-td7625162.html#a7625166
> (and nested links).
>
> Some clarification would be much appreciated!
>
> Chris
>
> --
>
> *Chris Richardson*, System Architect
> c...@fourc.eu
>
>
> *FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu
> *
>
> *Follow us on LinkedIn , Facebook
> , Google+  and Twitter
> !*
>

Re: Multiple connections with ssl client auth does not work as expected

[Jakub Scholz]

I did some more digging through my old work emails. We had a customer with
this kind of problem in June 2015. At that time I was able to reproduce
this behaviour on Linux (I believe they were Windows users, so it should
have affected also Windows). The problem was exactly the same as described
by Chris.

I was able to find a very primitive workaround at that time ... the
"caching" was done based on hostname. So when two different hostnames were
used the caching did not happen and the connections worked fine. So the
workaround was to 1) create for each connection an artificial /etc/hosts
record to which will route to the same broker, 2) Disable SSL hostname
verification and 3) open each connection through a different hostname. Hey
it was ugly and a bit insecure ... but it worked as a quick fix :-).

Later the customer got back to us with following info:
"After much investigation and experimentation, we have identified a
potential issue with the Qpid library implementation of SSL connections,
where the SSL session id might occasionally be "cached" or "reused". We
believe this is the cause of the ACL exceptions, since when the session Id
is cached and reused in an application that connects with multiple SSL
client certificates, the previously used client certificate information of
that previous SSL session might be reused as well for the next SSL
connection attempt. We have implemented a fix in our Qpid library and
application (by essentially disabling the caching of SSL session id for
each SSL connection attempt), and deployed them in our UAT environment
(user acceptance test). It seems to be working, as our application is able
to run with multiple SSL certificates now."

I asked them to provide the patch to the Qpid community. But I'm not sure
they ever did - at least I cannot find anything. I'm not sure why I didn't
raised a QPID JIRA for it my self. :-(

I probably haven't tried it since 2015. So if it works for Gordon it might
be already fixed in master.

Regards
Jakub

On Mon, Aug 21, 2017 at 11:18 PM, Jakub Scholz <ja...@scholz.cz> wrote:

> This is definitely not new in 1.36. I think this is present "since the
> beginning". :-(
>
> If I remember correctly the problem was that the NSS library which handles
> the SSL certificates is initialised only once even when you create multiple
> connections. I was quite sure this was already discussed in some issue or
> on the mailing list but I have problems finding it now - I will keep
> looking.
>
> Regards
> Jakub
>
> On Mon, Aug 21, 2017 at 10:46 PM, Chris Richardson <c...@fourc.eu> wrote:
>
>> Hi,
>>
>> I've encountered an issue with the C++ broker (1.36) where it appears
>> that multiple connections within the same process using SSL client
>> auth do not use the "ssl-cert-name" property provided when the
>> connection instance is created. Rather, it appears the second
>> connection will use auth details of the first connection.
>>
>> Is this expected behaviour?
>>
>> Setup to show this happening is rather involved so I've created a jira
>> issue with some attached material to demonstrate the problem:
>> https://issues.apache.org/jira/browse/QPID-7894.
>>
>> Regards
>>
>> --
>> Chris Richardson, System Architect
>> c...@fourc.eu
>>
>> FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norway
>> www.fourc.eu
>>
>> Follow us on LinkedIn, Facebook, Google+ and Twitter!
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>>
>

Re: Multiple connections with ssl client auth does not work as expected

[Jakub Scholz]

This is definitely not new in 1.36. I think this is present "since the
beginning". :-(

If I remember correctly the problem was that the NSS library which handles
the SSL certificates is initialised only once even when you create multiple
connections. I was quite sure this was already discussed in some issue or
on the mailing list but I have problems finding it now - I will keep
looking.

Regards
Jakub

On Mon, Aug 21, 2017 at 10:46 PM, Chris Richardson  wrote:

> Hi,
>
> I've encountered an issue with the C++ broker (1.36) where it appears
> that multiple connections within the same process using SSL client
> auth do not use the "ssl-cert-name" property provided when the
> connection instance is created. Rather, it appears the second
> connection will use auth details of the first connection.
>
> Is this expected behaviour?
>
> Setup to show this happening is rather involved so I've created a jira
> issue with some attached material to demonstrate the problem:
> https://issues.apache.org/jira/browse/QPID-7894.
>
> Regards
>
> --
> Chris Richardson, System Architect
> c...@fourc.eu
>
> FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norway
> www.fourc.eu
>
> Follow us on LinkedIn, Facebook, Google+ and Twitter!
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Welcome Adel Boutros as an Apache Qpid committer

[Jakub Scholz]

Welcome Adel. Great to have you here!

On Thu, Aug 10, 2017 at 11:31 AM, Oleksandr Rudyy  wrote:

> Welcome Adel!
>
> On 9 August 2017 at 11:49, Robbie Gemmell 
> wrote:
>
> > The Qpid PMC have voted to grant commit rights to Adel Boutros in
> > recognition of continued contributions to the project.
> >
> > Welcome, Adel!
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
> >
>

Re: [qpid C++] Problems addinng externally signed cert and key to certutil (NSS) database

[Jakub Scholz]

I think that if you want the broker to present the whole chain you have to
load the chain into the certutil database. You can download the
intermediate certificate here:
https://letsencrypt.org/certs/lets-encrypt-x3-cross-signed.pem.txt
And simply add it to the certutil database:
certutil -A -t ",," -n LE -i lets-encrypt-x3-cross-signed.pem.txt

I tried it only briefly, so I'm not 100% sure whether the order of steps
matters - i.e. whether you have to load the intermediate before loading
your own public key / private key. I guess it should not. But it should
give you the whole chain as you want:

CONNECTED(0003)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = auth.dave.dbg-devops.com
verify return:1
140040324691784:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad
certificate:s3_pkt.c:1257:SSL alert number 42
140040324691784:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake
failure:s23_lib.c:184:
---
Certificate chain
 0 s:/CN=auth.dave.dbg-devops.com
   i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
   i:/O=Digital Signature Trust Co./CN=DST Root CA X3
---

Regards
JAkub



On Wed, Jul 12, 2017 at 7:11 AM, Morgan Lindqvist <
morgan.lindqv...@ericsson.com> wrote:

> Hi All,
>
> Up till now I have used a own CA and signed the server and client
> certificates for my QPID C++ installation, this is working as it should
> from
> both the client and the server side.
>
> A new requirement have now been added which is that the root CA for the
> server certificate must be a trusted CA, not one that I made my self.
>
> I have been trying to adapt my procedure for adding the certificates so
> that
> I can add a certificate and key that is created by a trusted CA to the
> certutil (NSS) database but I am failing misserably.
>
> I am using the script below to add the server certificate and create the
> client certificate. The server certificate is created by Lets Encrypt and
> the client certificates is still created and signed by my own CA.
>
> 
> #!/bin/bash
>
> SERVER_CERT_DIR=serverTrusted
> CERT_PW_FILE=${SERVER_CERT_DIR}/cert_pw.txt
>
> #Create directory if missing
> mkdir -p ${SERVER_CERT_DIR}
>
> echo "# Create the password file to access the certificate DB"
> echo "# Use urandom for password generation"
> cat /dev/urandom | head -c 20 | base64 | md5sum | cut -d' ' -f1 >
> ${CERT_PW_FILE}
> chmod go-rwx ${CERT_PW_FILE}
>
> echo "# Create good quality noise"
> dd bs=256 count=1 if=/dev/urandom of=noise
>
> echo "# Create the Certificate and Key Database (-f is the password for
> database access)"
> certutil -N -d ${SERVER_CERT_DIR} -f ${CERT_PW_FILE}
>
> # CA
> echo "# Creating CA Certificate and store it in the database"
> certutil -S -n CA -d ${SERVER_CERT_DIR} -s "CN=MyOwnCA" -x -t "T,," -m 0 -v
> 21 -f  ${CERT_PW_FILE} -z noise -2 "CA:TRUE"
> echo "# Extract ca.cert file from the database"
> certutil -L -n CA -d ${SERVER_CERT_DIR} -a -o ${SERVER_CERT_DIR}/ca.cert
>
> #server
> echo "# Convert PEM format from Lets Encrypt"
> sudo openssl x509 -outform pem -in
> /etc/letsencrypt/live/qpid.myDomain.com/cert.pem -out
> ${SERVER_CERT_DIR}/production.cert
> sudo chown ubuntu:ubuntu ${SERVER_CERT_DIR}/production.cert
>
> echo "# Add the trusted server certificate to the database (trusted peer)"
> certutil -A -n development -d ${SERVER_CERT_DIR} -i
> ${SERVER_CERT_DIR}/production.cert -t 'P,,' -f ${CERT_PW_FILE}
>
> echo "# Convert the key and add to database"
> sudo openssl rsa -outform der -in
> /etc/letsencrypt/live/qpid.myDomain.com/privkey.pem -out
> ${SERVER_CERT_DIR}/production.key
> sudo chown ubuntu:ubuntu ${SERVER_CERT_DIR}/production.key
> openssl rsa -inform DER -outform PEM -in ${SERVER_CERT_DIR}/production.key
> -out ${SERVER_CERT_DIR}/production-key.pem
>
> echo "# Create p12 key"
> openssl pkcs12 -export -inkey ${SERVER_CERT_DIR}/production-key.pem  -in
> ${SERVER_CERT_DIR}/production.cert -out
> ${SERVER_CERT_DIR}/production-key.p12 -nodes -password pass:`cat
> ${CERT_PW_FILE}`
> echo "# Add server key to database"
> pk12util -d ${SERVER_CERT_DIR} -i ${SERVER_CERT_DIR}/production-key.p12 -w
> ${CERT_PW_FILE} -k ${CERT_PW_FILE}
>
> #client
> function createClient {
>   echo "# Generate the client certificate"
>   certutil -S -n $1 -d ${SERVER_CERT_DIR} -s "CN=$1" -c CA -t "P,," -v 21
> -f
> ${CERT_PW_FILE} -z noise
>
>   echo "# Export the key from the DB to a pkcs#12 file"
>   pk12util -n $1 -d ${SERVER_CERT_DIR} -o ${SERVER_CERT_DIR}/$1.p12 -k
> ${CERT_PW_FILE} -w ${CERT_PW_FILE}
>
>   echo "# Convert the key (nodes is no key encryption and passin is
> password
> input)"
>   openssl pkcs12 -in ${SERVER_CERT_DIR}/$1.p12 -out
> ${SERVER_CERT_DIR}/$1.key -nodes -passin pass:`cat ${CERT_PW_FILE}`
>
>   echo "# Export the certificate"
>   certutil -L -n $1 -d ${SERVER_CERT_DIR} -a -o 

Re: [VOTE] Release Qpid Java 6.0.8 (RC1)

[Jakub Scholz]

+1 ... I checked the Java broker and the 0-10 client. I also run the 0-10
client against the C++ broker.

On Fri, Jun 23, 2017 at 5:29 PM, Rob Godfrey 
wrote:

> +1
>
> Built from source and ran the system tests
> Started the broker and used the management console.
> Ran some ad hoc tests using the AMQP 0-x and AMQP 1.0 clients
>
> On 23 June 2017 at 16:53, Robbie Gemmell  wrote:
>
> > On 21 June 2017 at 16:10, Keith W  wrote:
> > > Hi all,
> > >
> > > A release candidate for the next release (6.0.8) of the Qpid Java
> > > Components has been created.
> > >
> > > The list of defect fixes can be found in Jira:
> > >
> > > https://issues.apache.org/jira/issues/?jql=project%20%
> > 3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.0.8
> > >
> > > Please test and vote accordingly.
> > >
> > > The source and binary archives can be grabbed from here:
> > > https://dist.apache.org/repos/dist/dev/qpid/java/6.0.8-rc1
> > >
> > > Those files and the other maven artifacts are also staged for now at:
> > >
> > > https://repository.apache.org/content/repositories/orgapacheqpid-1110
> > >
> > > 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-1110
> > > 
> > >   
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > > For additional commands, e-mail: users-h...@qpid.apache.org
> > >
> >
> > +1
> >
> > I checked things over as follows:
> > - Verified all the signatures and checksum files.
> >  -- The .md5 files in the binaries subdir don't contain the associated
> file
> > names, so they don't verify as easily with tools. The src .md5 does.
> > - Checked the LICENCE+NOTICE files present in each archive.
> > - Used "mvn apache-rat:check" to verify the headers in source release.
> > - Ran the source release build.
> > - Started the broker from the tar.gz binary, loaded the web management
> >   console and created a queue to use with client examples.
> > - Ran the Qpid JMS master HelloWorld example against the running broker.
> >
> > Robbie
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
> >
>

Re: [VOTE] Release Qpid Java 6.1.4 (RC1)

[Jakub Scholz]

+1 ... I checked the Java broker and the 0-10 client. I also run the 0-10
client against the C++ broker.

On Fri, Jun 23, 2017 at 10:47 PM, Oleksandr Rudyy  wrote:

> +1
>
> * verified checksums and signatures
> * built from sources and ran tests
> * started broker
> * created queue from web management console
> * ran examples ("hello world", Spout and Drain)
>
> On 21 June 2017 at 16:10, Keith W  wrote:
>
> > Hi all,
> >
> > A release candidate for the next release (6.1.4) of the Qpid Java
> > Components has been created.
> >
> > The list of defect fixes can be found in Jira:
> >
> > https://issues.apache.org/jira/issues/?jql=project%20%
> > 3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.1.4
> >
> > Please test and vote accordingly.
> >
> > The source and binary archives can be grabbed from here:
> > https://dist.apache.org/repos/dist/dev/qpid/java/6.1.4-rc1
> >
> > Those files and the other maven artifacts are also staged for now at:
> >
> > https://repository.apache.org/content/repositories/orgapacheqpid-1109
> >
> > 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-1109
> > 
> >   
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
> >
>

Re: [DISCUSSION] Queue Reject Policy Behaviour

[Jakub Scholz]

This is lot easier in C++ broker where you cannot change the policy or the
limits once you create the queue :-). But as a user I would have
appreciated the possibility to change the limits on the fly many times, so
I'm not suggesting this is the way to go.

>From your possibilities B) would be what I would expect. I assume that it
is quite easy to change the limit and purge some messages in two steps if
the operator wants to do that.

I can also imagine another possibility, where you don't allow the operator
to set the limit below the actual queue size. I.e.:
- user can freely increase the limit
- If the queue has limit 1000 messages and 100 actual messages inside, user
can change the limit to 101 or 100. But not to 99.
This would ensure that the limit is always kept and leave the task to
decide what to delete or not to delete on the operator. But I guess this
might be also non-trivial to implement so that it doesn't run into any race
conditions etc.

Regards
Jakub


On Tue, Jun 13, 2017 at 11:21 AM, Lorenz Quack 
wrote:

> Hello all,
>
> QPID-7815 [1] proposes the addition of a Queue Overflow Reject Policy
> to the Qpid broker-j (aka Qpid Broker for Java) component.
>
> Queue's allow to define overflow limits (in term of number of messages
> and/or cumulative size of the messages).  If the limit is breached the
> overflow policy determines the behaviour.  There are three ways the
> limits can be breached.
>
>   1) A new message arrives at the queue pushing it over the limit.
>
>   2) An operator lowers the limit so that existing messages are in
>  breach of the limit.
>
>   3) An operator changes the policy.  For example from a No-op policy
>  to the reject policy under discussion.
>
> The behaviour of the proposed policy in case 1) is fairly straight
> forward and I think uncontroversial.  This discussion thread is to
> hash out the expected behaviour in case of operator intervention,
> i.e. case 2) and 3).
>
> I see two possible behaviours:
>
>   A) The policy silently deletes messages that are in breach of the
>  policy.
>
>   B) The policy ignores messages that are already on the queue and
>  only applies to messages that newly arrive.
>
>
> What would people expect the behaviour to be?
> Please discuss.
>
>
> Kind regards,
> Lorenz
>
>
> [1] https://issues.apache.org/jira/browse/QPID-7815
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Installing apache's qpid-proton project on OS X

[Jakub Scholz]

Hi,

Last time I built Qpid Proton on MacOS was about a month ago. I don't
really have a guide for you. But I don't remember doing anything special to
make it work (I was surprised my self that it simply worked). I used
homebrew to install all needed tools and dependencies, but they were not
that many (gcc, cmake, openssl ... maybe something more). For the record,
all I needed was the Proton libraries and the Go-lang binding. For that is
seemed to work fine. Perhaps it is not that easy if you need something more
(some other bindings etc.).

Can you share the details where exactly you got stuck? Maybe I will
remember something.

Thanks & Regards
Jakub

On Thu, May 25, 2017 at 6:22 PM, Yoalli Hidalgo Pontet 
wrote:

> Hi QPID users,
>
> I would love to use Apache's qpid project as part of another project I am
> working on. However the installation instructions I found don't provide the
> steps to install it on OS X (in my case, the version I use is OS X 10.12
> Sierra):
> https://github.com/apache/qpid-proton/blob/master/INSTALL.md
>
> I have been trying to look for the required packages on homebrew and
> macports (which are OS X's packet managers, like apt-get and yum on Linux),
> and online. I have found some of them and I am still looking for the rest,
> which is a bit hard because sometimes they a different name, or have old
> sub-dependencies, etc.
>
> If any of you has successfully installed it on OS X, could you please share
> the steps with me?
>
> Thank you in advance for your help with this request, I am really looking
> forward start using qpid! :D
>
> Yoalli
>
>  (\ /)
> (  . .)
> c('')('')
>

Re: Credit handling for sending messages to multicast addresses in Dispatch

[Jakub Scholz]

FYI: I raised it as DISPATCH-779 (
https://issues.apache.org/jira/browse/DISPATCH-779)

Thanks & Regards
Jakub

On Mon, May 22, 2017 at 9:14 PM, Jakub Scholz <ja...@scholz.cz> wrote:

> Hi Ted,
>
> Ok, thanks. I will try to collect some logs and raise a JIRA.
>
> Thanks & Regards
> Jakub
>
> On Mon, May 22, 2017 at 8:55 PM, Ted Ross <tr...@redhat.com> wrote:
>
>> Hi Jakub,
>>
>> I think your expected behavior should be the correct one for multicast.
>> This is a bug.
>>
>> -Ted
>>
>>
>> On 05/20/2017 05:20 PM, Jakub Scholz wrote:
>>
>>> Hi,
>>>
>>> In Dispatch, I can configure the multicast addresses:
>>> address {
>>>   prefix: /someAddress
>>>   distribution: multicast
>>> }
>>>
>>> My general expectation for such multicast address would be that:
>>> - The credit for sending messages is maintained by the router
>>> automatically
>>> independently on any receivers being attached
>>> - I can send message to such address even when there is no receiver
>>> connected to this address.
>>> - When there is no receiver connected the message is simply dropped by
>>> the
>>> router
>>> - When one or more receivers are connected, the message is sent to all of
>>> them
>>>
>>> However, currently it seems to behave a bit strangely:
>>> - When I connect my producer when no receiver is connected, I get no
>>> credit
>>> and therefore I cannot send any messages
>>> - When I connect a receiver, broker will automatically give credit to the
>>> sender. When I disconnect the receiver, the remaining credit is not taken
>>> away. So I can still send messages until I run out of credit although
>>> nobody is receiving them
>>>
>>> Even if in case original expectations were wrong, this seems to be still
>>> a
>>> bit inconsistent behaviour. So I'm wondering whether what is the expected
>>> behaviour in this case and whether this is some bug. It seems to behave
>>> the
>>> same both in 0.8.0 as well as in latest master. Can someone clarify it?
>>>
>>> Thanks & Regards
>>> Jakub
>>>
>>>
>> --
>> Ted Ross
>> Senior Principal Software Engineer
>> Red Hat
>> 314 Littleton Road
>> Westford, MA 01886
>> tr...@redhat.com T: +1-978-392-3950 M: +1-978-399-4122
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>>
>

Re: Credit handling for sending messages to multicast addresses in Dispatch

[Jakub Scholz]

Hi Ted,

Ok, thanks. I will try to collect some logs and raise a JIRA.

Thanks & Regards
Jakub

On Mon, May 22, 2017 at 8:55 PM, Ted Ross <tr...@redhat.com> wrote:

> Hi Jakub,
>
> I think your expected behavior should be the correct one for multicast.
> This is a bug.
>
> -Ted
>
>
> On 05/20/2017 05:20 PM, Jakub Scholz wrote:
>
>> Hi,
>>
>> In Dispatch, I can configure the multicast addresses:
>> address {
>>   prefix: /someAddress
>>   distribution: multicast
>> }
>>
>> My general expectation for such multicast address would be that:
>> - The credit for sending messages is maintained by the router
>> automatically
>> independently on any receivers being attached
>> - I can send message to such address even when there is no receiver
>> connected to this address.
>> - When there is no receiver connected the message is simply dropped by the
>> router
>> - When one or more receivers are connected, the message is sent to all of
>> them
>>
>> However, currently it seems to behave a bit strangely:
>> - When I connect my producer when no receiver is connected, I get no
>> credit
>> and therefore I cannot send any messages
>> - When I connect a receiver, broker will automatically give credit to the
>> sender. When I disconnect the receiver, the remaining credit is not taken
>> away. So I can still send messages until I run out of credit although
>> nobody is receiving them
>>
>> Even if in case original expectations were wrong, this seems to be still a
>> bit inconsistent behaviour. So I'm wondering whether what is the expected
>> behaviour in this case and whether this is some bug. It seems to behave
>> the
>> same both in 0.8.0 as well as in latest master. Can someone clarify it?
>>
>> Thanks & Regards
>> Jakub
>>
>>
> --
> Ted Ross
> Senior Principal Software Engineer
> Red Hat
> 314 Littleton Road
> Westford, MA 01886
> tr...@redhat.com T: +1-978-392-3950 M: +1-978-399-4122
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Credit handling for sending messages to multicast addresses in Dispatch

[Jakub Scholz]

Hi,

In Dispatch, I can configure the multicast addresses:
address {
 prefix: /someAddress
 distribution: multicast
}

My general expectation for such multicast address would be that:
- The credit for sending messages is maintained by the router automatically
independently on any receivers being attached
- I can send message to such address even when there is no receiver
connected to this address.
- When there is no receiver connected the message is simply dropped by the
router
- When one or more receivers are connected, the message is sent to all of
them

However, currently it seems to behave a bit strangely:
- When I connect my producer when no receiver is connected, I get no credit
and therefore I cannot send any messages
- When I connect a receiver, broker will automatically give credit to the
sender. When I disconnect the receiver, the remaining credit is not taken
away. So I can still send messages until I run out of credit although
nobody is receiving them

Even if in case original expectations were wrong, this seems to be still a
bit inconsistent behaviour. So I'm wondering whether what is the expected
behaviour in this case and whether this is some bug. It seems to behave the
same both in 0.8.0 as well as in latest master. Can someone clarify it?

Thanks & Regards
Jakub

Re: Misleading messages when starting up Qpid c++ 1.36.0 ?

[Jakub Scholz]

Could you try to start the broker like this:
 qpidd --no-module-dir --load-module amqp.so --load-module
linearstore.so --auth no
Does the warning message still appear?

There used to be the store.so module which wasn't really message store on
its own, but it was used for some SQL based message store (or something
like that). I think that was causing some strange messages like this. Could
you check your /usr/lib64/qpid/daemon/ path or where ever are the broker
modules stored in your installation to see what files does it contain? Does
it contain something like store.so?

JAkub

On Sat, May 20, 2017 at 1:14 PM, kristianraue 
wrote:

> qpidd --load-module amqp.so

Re: [VOTE] Release Apache Qpid JMS 0.23.0

[Jakub Scholz]

+1 ... I used the staging repo and run my tests against different versions
of Qpid C++ broker.

On Fri, May 12, 2017 at 7:07 PM, Robbie Gemmell 
wrote:

> On 12 May 2017 at 17:41, Robbie Gemmell  wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.23.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.23.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1106
> >
> > The JIRAs currently assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12314524=12340367
> >
> > 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-1106
> > 
> >   
> >
> > The dependency for the client itself would then be:
> >
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 0.23.0
> >   
>
> Adding my +1
>
> I checked things out as follows:
> - Verified the signature and checksum files.
> - Checked the LICENCE+NOTICE files are present/correct in src+bin archives.
> - Ran mvn apache-rat:check to check the licence headers in the src archive.
> - Ran the build+tests from the source release archive.
> - Built the examples from the binary release archive with Maven using the
>   staging repo and ran HelloWorld against Qpid Dispatch 0.8.0,
>   Qpid CPP master (both built against Proton 0.17.0), Qpid Broker-J master,
>   ActiveMQ 5 master, and ActiveMQ Artemis master.
> - Built the examples using javac manually and ran to verify required libs
>   were included in lib dir as expected.
> - Ran the Joram JMS tests against Qpid Broker-J master using the client
>   from the staging repo.
> - Ran the ActiveMQ 5 master build + AMQP tests with it.
> - Ran the ActiveMQ Artemis master build + AMQP tests with it.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: What package does recent versions of qpid-tools live in?

[Jakub Scholz]

The management tools should be now part of the C++ broker source tree:
https://github.com/apache/qpid-cpp/tree/master/management/python ... they
are also in the 1.36.0 release archives (management / python).

Jakub

On Sun, Apr 30, 2017 at 2:41 PM, Fraser Adams  wrote:

> Hello All,
>
> qpid-tools seems to have fallen off the face of the earth?
>
> Looking here http://archive.apache.org/dist/qpid/ there is an explicit
> release of qpid-tools from 0.10 onwards up until 0.32. Before 0.10 it
> doesn't look like there was an explicit qpid-tools release and it looks
> like it's necessary to pull the full tarball of everything to get the
> tools, but at least the tools seem to exist there, but after 0.32 there
> doesn't seem to be any update.
>
> after 0.32 cpp, java, python etc. are all more distinct components, which
> is fine, but assuming say qpid-cpp 1.36.0 in
> http://archive.apache.org/dist/qpid/cpp/1.36.0/ where would I find the
> most up to date version of say qpid-config to use with it.
>
>
> I appreciate that these tools aren't updated frequently and the versions
> in 0.32 most likely would be fine, but it's not something that seems to be
> covered in any of the recent docs in either https://qpid.apache.org/releas
> es/ or https://qpid.apache.org/download.html and I think the last time
> "C++ broker command-line tools" is mentioned is here:
> https://qpid.apache.org/releases/qpid-0.32/index.html
>
>
> Have I missed something?
>
> Cheers,
>
> Frase
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid Dispatch Router 0.8.0 (RC3)

[Jakub Scholz]

+1 ... I checked the RC against different clients and as well as against
the Qpid C++ broker

On Wed, Apr 26, 2017 at 2:15 PM, Ted Ross  wrote:

> Please cast your vote on this thread for releasing RC3 as the official
> 0.8.0.
>
> The following issue has been resolved since RC2:
>
> DISPATCH-742 - Prevent presettled deliveries from being dropped from a
> link-work record that is concurrently being processed by an IO thread.
>
> Build Artifacts:
>
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc3/
>
> Thanks,
>
> -Ted
>
>
> -
> 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.22.0

[Jakub Scholz]

+1 ... I used the staging repo and run my tests against different versions
of Qpid C++ and MRG-M brokers.

On Mon, Apr 17, 2017 at 7:34 PM, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.22.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.22.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1104
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12314524=12340042
>
> 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-1104
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.22.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Support for SASL EXTERNAL mechanism in Proton's Go language binding

[Jakub Scholz]

Hi,

I was playing over the weekend with Proton's binging for Go language (I was
using the Electron API). I works quite nicely, but I didn't managed to get
it connected to my broker using SASL EXTERNAL mechanism. When I configure
EXTERNAL in the AllowedMechs in ConnectionOptions, I always get following
error:
proton:io:sasl_error: SASL(-4): no mechanism available:  (Authentication
failed [mech=none])

At first I though that I was missing some library for the EXTERNAL support.
But it seems to work fine in the Python bindings, so I'm not sure about
that.

Anyone has some idea whether the Go language binding actually supports the
EXTERNAL mechanism?

Thanks & Regards
Jakub

PS: My client source can be found here ...
https://gist.github.com/scholzj/6434b7382bb21d2ae23f20195b47dd7c

Re: [VOTE] Release Qpid Dispatch Router 0.8.0 (RC2)

[Jakub Scholz]

+1

I built it from the source and ran Dispatch against different clients and
brokers.

On Fri, Apr 7, 2017 at 6:00 PM, Robbie Gemmell 
wrote:

> On 7 April 2017 at 15:34, Ted Ross  wrote:
> > Please cast your vote on this thread for releasing RC2 as the official
> > 0.8.0.
> >
> > Thanks,
> >
> > -Ted
> >
>
> +1
>
> I checked it over as follows:
> - Verified signature and checksums.
> - Checked LICENCE + NOTICE files present, look ok.
> - Ran RAT with and without the excludes file for comparison, output looked
> good.
> - Built against Proton 0.17.0, ran the tests, all passed.
> - Ran the qpid-jms master HelloWorld example against the router.
>
> The only thing I saw worth noting is that the TODO file could probably
> do with updating or preferably deleting.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Enabling AMQP 1.0 on Qpid C++ Broker

[Jakub Scholz]

I think that might depend on the OS etc. In my build on CentOS 7 it is in
/usr/lib64/qpid/daemon/ ...

$ ls /usr/lib64/qpid/daemon/
amqp.so  linearstore.so  xml.so

When the module is loaded, the broker log should print following message
when starting:
2017-03-31 18:23:12 [Broker] info Loaded protocol AMQP 1.0

Thanks & Regards
Jakub

On Fri, Mar 31, 2017 at 8:14 PM, mottese  wrote:

> around the qpid-cpp and qpid-proton source, build, install
> directories and was never able to find an amqp.so. It seems that I need
> this
> for AMQP 1.0 support to be enabled on the broker. Do you know where I'd
>

Re: Python qpid messaging api and amqp1.0 support

[Jakub Scholz]

Hi Mark,

Last time I used the Python binding against the C++ API on Ubuntu (I
actually use it against Qpid C++ broker and not against ActiveMQ, but with
AMQP 1.0) I had following packages installed from ppa:qpid/testing (+ some
SASL libraries for authentication etc.):
- libqpid-proton6
- libqpidclient2
- libqpidcommon2
- libqpidmessaging2
- libqpidtypes1
- python-qpid-messaging

That was probably few months ago, but maybe it still helps a bit.

Thanks & Regards
Jakub

On Thu, Mar 23, 2017 at 10:24 PM, Mark Blum  wrote:

> Hello all,
>
> I'm trying to get amqp1.0 support working in Python so I can interact with
> an ActiveMQ broker which supports amqp1.0.
>
> What I can't figure out is what magic combination of steps will get this
> working.
>
> Note I am trying to use the messaging API at this time, not the proton
> (reactor) API.
>
> So far I've determined that the qpid Python bindings don't support amqp1.0,
> but I get the impression that the python-cqpid bindings do.
> However, I can't get it to work right (hence this message).  If I leave the
> protocol option out when creating a new Connection object it defaults to
> amqp0-10 (and I get an unsupported version error when opening the
> connection
> to the ActiveMQ broker), and if I use the protocol option (e.g.
> cqpid.Connection(broker_url, protocol = 'amqp1.0'), I get "RuntimeError:
> Invalid option: protocol not recognised
> (qpid/client/amqp0_10/ConnectionImpl.cpp:160)" which is obvious that it is
> following an amqp0_10 code path.
>
> I'm trying all this on an Ubuntu 16.04 LTS server, and I've installed qpid
> via sudo apt-get install libqpid-proton2 python-cqpid python-qpid.
>
> I'm willing to install any other packages and/or manually build packages if
> it will help.
>
> If someone can point out what I'm missing to get this to work I would
> greatly appreciate it!
>
>
>
> --
> View this message in context: http://qpid.2158936.n2.nabble.
> com/Python-qpid-messaging-api-and-amqp1-0-support-tp7661439.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> -
> 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.21.0

[Jakub Scholz]

+1 ... I run my tests against different versions of Qpid C++ broker

On Fri, Mar 10, 2017 at 8:58 PM, Timothy Bish  wrote:

> +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/2017 12:13 PM, 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: the .sha files contain SHA512 checksums)
>>
>> The maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1102
>>
>> 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-1102
>>  
>>
>>
>> The dependency for the client itself would then be:
>>
>>
>>  org.apache.qpid
>>  qpid-jms-client
>>  0.21.0
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>>
>>
>
> --
> 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
>
>

Re: How to resize queue store in qpid-cpp-1.35.0

[Jakub Scholz]

With the older versions, when you created a queue, you had to specify
number of journal files which were backing the queue and their size. For
example 8 journal files, 1024 pages each (the default values were used when
you haven't specified anything). The journal files were created when you
created the queue and their number and size of these files determined how
many persistent messages can fit into the queue. When you wanted to change
this, you could have used the qpid-store-resize tool.

The linearstore in the new version works, the journal files are not created
only when the queue is being created. They are simply being created when
the queue needs more journal files - on demand. Therefore there is no fixed
number of journal files and you don't need the resize tool to change their
number. So there is no need for such tool.

Jakub


On Thu, Mar 9, 2017 at 3:29 PM, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:

> Jakub,
>
> in older versions there is a qpid/libexec/resize tool right, do we need and
> or have the similar or same tool in 1.35 version?
>
> Ram
>
> On Mar 9, 2017 3:33 AM, "Jakub Scholz" <ja...@scholz.cz> wrote:
>
> > Hi,
> >
> > What do you mean with resizing queue store? With linear store, the
> journal
> > files should be created "on demand", you don't have to do any resizing.
> The
> > only limits for your queue are the size and count limits. There are no
> > store limits like they used to be with the old legacy store.
> >
> > Jakub
> >
> > On Thu, Mar 9, 2017 at 12:17 AM, rammohan ganapavarapu <
> > rammohanga...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I dont see resize tool in linearstore, how do i resize queue store in
> > > qpid-cpp-1.35 version?
> > >
> > > Thanks,
> > > Ram
> > >
> >
>

Re: How to resize queue store in qpid-cpp-1.35.0

[Jakub Scholz]

Hi,

What do you mean with resizing queue store? With linear store, the journal
files should be created "on demand", you don't have to do any resizing. The
only limits for your queue are the size and count limits. There are no
store limits like they used to be with the old legacy store.

Jakub

On Thu, Mar 9, 2017 at 12:17 AM, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:

> Hi,
>
> I dont see resize tool in linearstore, how do i resize queue store in
> qpid-cpp-1.35 version?
>
> Thanks,
> Ram
>

Re: [qpid c++] ACL for writing to an exchange

[Jakub Scholz]

Hi Morgan,

You might be missing the exchange name. The publish rule should look
something like this:
acl allow producer publish exchange name=my_exchange routingkey=myRoutingKey

But without the logs it is just guessing.

Jakub

On Wed, Mar 1, 2017 at 8:13 PM, Morgan Lindqvist <
morgan.lindqv...@ericsson.com> wrote:

> Hi All,
>
> I have an issue that I can not get working
>
> Setup:
>
> I have one exchange and three queues connected to it with a filter between
> the exchange and each queue.
>
> The issue I have is to get the users write access to the exchange.
>
> acl allow producer access exchange name=nwEx
> acl allow producer access queue name=nwEx
> acl allow producer publish exchange routingkey=nwEx
>
> This does however not give the users in the "producer" group write access
> to
> the exchange. I have tried looking for documentation but failed. Any
> pointers or examples would be very much appreciated.
>
> I do not have the error message available now but it is something like that
> the user do not have write access to the queues connected to the exchange.
>
> /Morgan
>
>
>
> --
> View this message in context: http://qpid.2158936.n2.nabble.
> com/qpid-c-ACL-for-writing-to-an-exchange-tp7659852.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: C++ broker build not working: 'round' is not a member of 'std'

[Jakub Scholz]

Thanks a lot. All seems to work fine now.

Regards
JAkub

On Wed, Feb 15, 2017 at 10:23 PM, Kim van der Riet <kim.vdr...@redhat.com>
wrote:

> Doh!!!
>
> ... and it was on the same line I just fixed :-(
>
> Ok, checked in an additional fix on master.
>
>
> On 02/15/2017 02:33 PM, Jakub Scholz wrote:
>
>> Hi Kim,
>>
>> It looks like there is the same problem also with the log2 function. That
>> seems to be the last one - when I work around it the compilation succeeds.
>> So it looks like there is nothing else.
>>
>> Thanks & Regards
>> Jakub
>>
>> /root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/Me
>> ssageStoreImpl.cpp:
>> In static member function 'static uint32_t
>> qpid::linearstore::MessageStoreImpl::chkJrnlWrPageCacheSize(uint32_t,
>> const
>> string&)':
>> /root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/Me
>> ssageStoreImpl.cpp:85:36:
>> error: 'log2' is not a member of 'std'
>>  p = std::pow(2, std::floor(std::log2(p) + 0.5));
>> ^
>> /root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/Me
>> ssageStoreImpl.cpp:85:36:
>> note: suggested alternative:
>> In file included from /usr/include/features.h:375:0,
>>  from
>> /usr/include/c++/4.8.2/x86_64-redhat-linux/bits/os_defines.h:39,
>>  from
>> /usr/include/c++/4.8.2/x86_64-redhat-linux/bits/c++config.h:2097,
>>  from /usr/include/c++/4.8.2/string:38,
>>  from
>> /root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/broker/Persist
>> ableExchange.h:25,
>>  from
>> /root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/broker/MessageStore.h:24,
>>  from
>> /root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/Me
>> ssageStoreImpl.h:25,
>>  from
>> /root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/Me
>> ssageStoreImpl.cpp:22:
>> /usr/include/bits/mathcalls.h:145:1: note:   'log2'
>>  __MATHCALL (log2,, (_Mdouble_ __x));
>>  ^
>> At global scope:
>> cc1plus: error: unrecognized command line option
>> "-Wno-implicit-fallthrough" [-Werror]
>> cc1plus: all warnings being treated as errors
>> make[2]: ***
>> [src/CMakeFiles/linearstore.dir/qpid/linearstore/MessageStoreImpl.cpp.o]
>> Error 1
>> make[2]: Leaving directory `/root/rpmbuild/BUILD/qpid-cpp-1.37.0'
>> make[1]: *** [src/CMakeFiles/linearstore.dir/all] Error 2
>>
>>
>> On Wed, Feb 15, 2017 at 6:38 PM, Kim van der Riet <kim.vdr...@redhat.com>
>> wrote:
>>
>> My error.
>>>
>>> I have replaced the offending statement with a more traditional version
>>> that should not require c++11. See QPID-7676.
>>>
>>> Kim
>>>
>>>
>>> On 02/14/2017 05:18 PM, Jakub Scholz wrote:
>>>
>>> Hi Alan,
>>>>
>>>> Thanks for your help. The -std=c++11 flag indeed helps to work around
>>>> the
>>>> problem.
>>>>
>>>> Thanks & Regards
>>>> Jakub
>>>>
>>>>
>>>> On Mon, Feb 13, 2017 at 3:42 PM, Alan Conway <acon...@redhat.com>
>>>> wrote:
>>>>
>>>> On Fri, 2017-02-10 at 22:46 +0100, Jakub Scholz wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>>
>>>>>> I seem to be unable to build the latest master of Qpid C++ broker. It
>>>>>> seems
>>>>>> to complain about the round function not being in std (the complete
>>>>>> output
>>>>>> is below). It seems to be related to QPID-7666 / commit 34cfb7f.
>>>>>>
>>>>>> I'm compiling it on CentOS 7 with g++ version 4.8.5, Make version
>>>>>> 3.82 and
>>>>>> cmake 2.8.12.2. Is this some bug in the code? Or do I need some newer
>>>>>> compiler / some newer libraries?
>>>>>>
>>>>>>
>>>>> This should build if you do:
>>>>> cmake -DCMAKE_CXX_FLAGS=-std=c++11
>>>>>
>>>>> However qpid-cpp has always been buildable with c++03 so I think this
>>>>> is a regression that should be fixed. Kim, this was introduced in your
>>>>> commit:
>>>>>
>>>>> 34cfb7f0 QPID-7666: Added wcache-num-pages (and tpl-wcache-num-pages)
>>>>> to linearstore. Changed defaults for regular queues to wcache-page-
&g

Re: C++ broker build not working: 'round' is not a member of 'std'

[Jakub Scholz]

Hi Kim,

It looks like there is the same problem also with the log2 function. That
seems to be the last one - when I work around it the compilation succeeds.
So it looks like there is nothing else.

Thanks & Regards
Jakub

/root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/MessageStoreImpl.cpp:
In static member function 'static uint32_t
qpid::linearstore::MessageStoreImpl::chkJrnlWrPageCacheSize(uint32_t, const
string&)':
/root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/MessageStoreImpl.cpp:85:36:
error: 'log2' is not a member of 'std'
 p = std::pow(2, std::floor(std::log2(p) + 0.5));
^
/root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/MessageStoreImpl.cpp:85:36:
note: suggested alternative:
In file included from /usr/include/features.h:375:0,
 from
/usr/include/c++/4.8.2/x86_64-redhat-linux/bits/os_defines.h:39,
 from
/usr/include/c++/4.8.2/x86_64-redhat-linux/bits/c++config.h:2097,
 from /usr/include/c++/4.8.2/string:38,
 from
/root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/broker/PersistableExchange.h:25,
 from
/root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/broker/MessageStore.h:24,
 from
/root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/MessageStoreImpl.h:25,
 from
/root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/MessageStoreImpl.cpp:22:
/usr/include/bits/mathcalls.h:145:1: note:   'log2'
 __MATHCALL (log2,, (_Mdouble_ __x));
 ^
At global scope:
cc1plus: error: unrecognized command line option
"-Wno-implicit-fallthrough" [-Werror]
cc1plus: all warnings being treated as errors
make[2]: ***
[src/CMakeFiles/linearstore.dir/qpid/linearstore/MessageStoreImpl.cpp.o]
Error 1
make[2]: Leaving directory `/root/rpmbuild/BUILD/qpid-cpp-1.37.0'
make[1]: *** [src/CMakeFiles/linearstore.dir/all] Error 2


On Wed, Feb 15, 2017 at 6:38 PM, Kim van der Riet <kim.vdr...@redhat.com>
wrote:

> My error.
>
> I have replaced the offending statement with a more traditional version
> that should not require c++11. See QPID-7676.
>
> Kim
>
>
> On 02/14/2017 05:18 PM, Jakub Scholz wrote:
>
>> Hi Alan,
>>
>> Thanks for your help. The -std=c++11 flag indeed helps to work around the
>> problem.
>>
>> Thanks & Regards
>> Jakub
>>
>>
>> On Mon, Feb 13, 2017 at 3:42 PM, Alan Conway <acon...@redhat.com> wrote:
>>
>> On Fri, 2017-02-10 at 22:46 +0100, Jakub Scholz wrote:
>>>
>>>> Hi,
>>>>
>>>> I seem to be unable to build the latest master of Qpid C++ broker. It
>>>> seems
>>>> to complain about the round function not being in std (the complete
>>>> output
>>>> is below). It seems to be related to QPID-7666 / commit 34cfb7f.
>>>>
>>>> I'm compiling it on CentOS 7 with g++ version 4.8.5, Make version
>>>> 3.82 and
>>>> cmake 2.8.12.2. Is this some bug in the code? Or do I need some newer
>>>> compiler / some newer libraries?
>>>>
>>>
>>> This should build if you do:
>>> cmake -DCMAKE_CXX_FLAGS=-std=c++11
>>>
>>> However qpid-cpp has always been buildable with c++03 so I think this
>>> is a regression that should be fixed. Kim, this was introduced in your
>>> commit:
>>>
>>> 34cfb7f0 QPID-7666: Added wcache-num-pages (and tpl-wcache-num-pages)
>>> to linearstore. Changed defaults for regular queues to wcache-page-
>>> size=16 (kiB) and set wcache-num-pages default to 16. Added wcache-
>>> page-size and wcache-num-pages to qpid-config.
>>>
>>> Can you fix that and make sure we compile with -std=c++03? FYI
>>> cppreference.com is a good reference for checking which version of
>>> C/C++ things were introduced in - anything that doesn't have  an
>>> annotation like "(since C++11)" is safely c++03 or before.
>>>
>>> Cheers,
>>> Alan.
>>>
>>> Thanks & Regards
>>>> Jakub
>>>>
>>>> [ 79%] Building CXX object
>>>> src/CMakeFiles/linearstore.dir/qpid/linearstore/MessageStoreImpl.cpp.
>>>> o
>>>> /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp: In static member
>>>> function 'static uint32_t
>>>> qpid::linearstore::MessageStoreImpl::chkJrnlWrPageCacheSize(uint32_t,
>>>> const
>>>> string&)':
>>>> /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:85:25: error:
>>>> 'round'
>>>> is not a member of 'std'
>>>>  p = std::pow(2, std::round(std::log2(p)));
>>

Re: C++ broker build not working: 'round' is not a member of 'std'

[Jakub Scholz]

Hi Alan,

Thanks for your help. The -std=c++11 flag indeed helps to work around the
problem.

Thanks & Regards
Jakub


On Mon, Feb 13, 2017 at 3:42 PM, Alan Conway <acon...@redhat.com> wrote:

> On Fri, 2017-02-10 at 22:46 +0100, Jakub Scholz wrote:
> > Hi,
> >
> > I seem to be unable to build the latest master of Qpid C++ broker. It
> > seems
> > to complain about the round function not being in std (the complete
> > output
> > is below). It seems to be related to QPID-7666 / commit 34cfb7f.
> >
> > I'm compiling it on CentOS 7 with g++ version 4.8.5, Make version
> > 3.82 and
> > cmake 2.8.12.2. Is this some bug in the code? Or do I need some newer
> > compiler / some newer libraries?
>
> This should build if you do:
> cmake -DCMAKE_CXX_FLAGS=-std=c++11
>
> However qpid-cpp has always been buildable with c++03 so I think this
> is a regression that should be fixed. Kim, this was introduced in your
> commit:
>
> 34cfb7f0 QPID-7666: Added wcache-num-pages (and tpl-wcache-num-pages)
> to linearstore. Changed defaults for regular queues to wcache-page-
> size=16 (kiB) and set wcache-num-pages default to 16. Added wcache-
> page-size and wcache-num-pages to qpid-config.
>
> Can you fix that and make sure we compile with -std=c++03? FYI
> cppreference.com is a good reference for checking which version of
> C/C++ things were introduced in - anything that doesn't have  an
> annotation like "(since C++11)" is safely c++03 or before.
>
> Cheers,
> Alan.
>
> > Thanks & Regards
> > Jakub
> >
> > [ 79%] Building CXX object
> > src/CMakeFiles/linearstore.dir/qpid/linearstore/MessageStoreImpl.cpp.
> > o
> > /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp: In static member
> > function 'static uint32_t
> > qpid::linearstore::MessageStoreImpl::chkJrnlWrPageCacheSize(uint32_t,
> > const
> > string&)':
> > /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:85:25: error:
> > 'round'
> > is not a member of 'std'
> >  p = std::pow(2, std::round(std::log2(p)));
> >  ^
> > /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:85:25: note:
> > suggested
> > alternatives:
> > In file included from /usr/include/features.h:375:0,
> >  from
> > /usr/include/c++/4.8.2/x86_64-redhat-linux/bits/os_defines.h:39,
> >  from
> > /usr/include/c++/4.8.2/x86_64-redhat-linux/bits/c++config.h:2097,
> >  from /usr/include/c++/4.8.2/string:38,
> >  from /qpid-
> > cpp/src/qpid/broker/PersistableExchange.h:25,
> >  from /qpid-cpp/src/qpid/broker/MessageStore.h:24,
> >  from /qpid-
> > cpp/src/qpid/linearstore/MessageStoreImpl.h:25,
> >  from
> > /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:22:
> > /usr/include/bits/mathcalls.h:310:1: note:   'round'
> >  __MATHCALLX (round,, (_Mdouble_ __x), (__const__));
> >  ^
> > In file included from /usr/include/boost/math/tools/config.hpp:25:0,
> >  from
> > /usr/include/boost/math/special_functions/sign.hpp:16,
> >  from /usr/include/boost/lexical_cast.hpp:167,
> >  from /qpid-cpp/src/qpid/Options.h:33,
> >  from /qpid-
> > cpp/src/qpid/linearstore/MessageStoreImpl.h:27,
> >  from
> > /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:22:
> > /usr/include/boost/math/special_functions/detail/round_fwd.hpp:43:6:
> > note:
> >   'boost::math::round'
> > T round(const T& v);
> >   ^
> > /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:85:36: error:
> > 'log2' is
> > not a member of 'std'
> >  p = std::pow(2, std::round(std::log2(p)));
> > ^
> > /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:85:36: note:
> > suggested
> > alternative:
> > In file included from /usr/include/features.h:375:0,
> >  from
> > /usr/include/c++/4.8.2/x86_64-redhat-linux/bits/os_defines.h:39,
> >  from
> > /usr/include/c++/4.8.2/x86_64-redhat-linux/bits/c++config.h:2097,
> >  from /usr/include/c++/4.8.2/string:38,
> >  from /qpid-
> > cpp/src/qpid/broker/PersistableExchange.h:25,
> >  from /qpid-cpp/src/qpid/broker/MessageStore.h:24,
> >  from /qpid-
> > cpp/src/qpid/linearstore/MessageStoreImpl.h:25,
> >  from
> > /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:22:
> > /usr/include/bits/mathcalls.h:145:1: note:   'log2'
> >  __MATHCALL (log2,, (_Mdouble_ __x));
> >  ^
> > make[2]: ***
> > [src/CMakeFiles/linearstore.dir/qpid/linearstore/MessageStoreImpl.cpp
> > .o]
> > Error 1
> > make[1]: *** [src/CMakeFiles/linearstore.dir/all] Error 2
> > make: *** [all] Error 2
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

C++ broker build not working: 'round' is not a member of 'std'

[Jakub Scholz]

Hi,

I seem to be unable to build the latest master of Qpid C++ broker. It seems
to complain about the round function not being in std (the complete output
is below). It seems to be related to QPID-7666 / commit 34cfb7f.

I'm compiling it on CentOS 7 with g++ version 4.8.5, Make version 3.82 and
cmake 2.8.12.2. Is this some bug in the code? Or do I need some newer
compiler / some newer libraries?

Thanks & Regards
Jakub

[ 79%] Building CXX object
src/CMakeFiles/linearstore.dir/qpid/linearstore/MessageStoreImpl.cpp.o
/qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp: In static member
function 'static uint32_t
qpid::linearstore::MessageStoreImpl::chkJrnlWrPageCacheSize(uint32_t, const
string&)':
/qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:85:25: error: 'round'
is not a member of 'std'
 p = std::pow(2, std::round(std::log2(p)));
 ^
/qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:85:25: note: suggested
alternatives:
In file included from /usr/include/features.h:375:0,
 from
/usr/include/c++/4.8.2/x86_64-redhat-linux/bits/os_defines.h:39,
 from
/usr/include/c++/4.8.2/x86_64-redhat-linux/bits/c++config.h:2097,
 from /usr/include/c++/4.8.2/string:38,
 from /qpid-cpp/src/qpid/broker/PersistableExchange.h:25,
 from /qpid-cpp/src/qpid/broker/MessageStore.h:24,
 from /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.h:25,
 from
/qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:22:
/usr/include/bits/mathcalls.h:310:1: note:   'round'
 __MATHCALLX (round,, (_Mdouble_ __x), (__const__));
 ^
In file included from /usr/include/boost/math/tools/config.hpp:25:0,
 from /usr/include/boost/math/special_functions/sign.hpp:16,
 from /usr/include/boost/lexical_cast.hpp:167,
 from /qpid-cpp/src/qpid/Options.h:33,
 from /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.h:27,
 from
/qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:22:
/usr/include/boost/math/special_functions/detail/round_fwd.hpp:43:6: note:
  'boost::math::round'
T round(const T& v);
  ^
/qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:85:36: error: 'log2' is
not a member of 'std'
 p = std::pow(2, std::round(std::log2(p)));
^
/qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:85:36: note: suggested
alternative:
In file included from /usr/include/features.h:375:0,
 from
/usr/include/c++/4.8.2/x86_64-redhat-linux/bits/os_defines.h:39,
 from
/usr/include/c++/4.8.2/x86_64-redhat-linux/bits/c++config.h:2097,
 from /usr/include/c++/4.8.2/string:38,
 from /qpid-cpp/src/qpid/broker/PersistableExchange.h:25,
 from /qpid-cpp/src/qpid/broker/MessageStore.h:24,
 from /qpid-cpp/src/qpid/linearstore/MessageStoreImpl.h:25,
 from
/qpid-cpp/src/qpid/linearstore/MessageStoreImpl.cpp:22:
/usr/include/bits/mathcalls.h:145:1: note:   'log2'
 __MATHCALL (log2,, (_Mdouble_ __x));
 ^
make[2]: ***
[src/CMakeFiles/linearstore.dir/qpid/linearstore/MessageStoreImpl.cpp.o]
Error 1
make[1]: *** [src/CMakeFiles/linearstore.dir/all] Error 2
make: *** [all] Error 2

Re: [VOTE] Release Qpid Proton 0.17.0

[Jakub Scholz]

+1 ... I used the RC1 to build Qpid C++ broker and run my AMQP 1.0 tests
against it. All seems to be OK.

On Fri, Feb 3, 2017 at 6:35 PM, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a first spin for a 0.17.0 Qpid Proton release,
> please test it and vote accordingly.
>
> Note that Proton-J is now independently released, its vote is also under
> way.
>
> The source archive can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.17.0-rc1/
>
> The JIRAs currently assigned are [still in need of major cleanup]:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12313720=12338663
>
> It is tagged as 0.17.0-rc1.
>
> Regards,
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: SSL/TCL Cipher suite settings for the broker (not the client)

[Jakub Scholz]

I'm afraid that there are no detailed configuration options for TLS/SSL in
the C++ broker. You cannot configure the enabled / disabled cipher suites,
protocols and stuff like that.

J.

On Thu, Feb 2, 2017 at 9:40 PM,  wrote:

> Looking for a way to set the SSL/TLS transport options on the broker, not
> the client (I'm assuming it's the C++ broker as it's whatever Red Hat ships
> with (/usr/sbin/qpidd)).
> The client allows for this under SSL transport options (
> https://qpid.apache.org/releases/qpid-jms-0.3.0/docs/index.html) but the
> broker configuration is strangely quite on this point (
> https://qpid.apache.org/releases/qpid-0.30/cpp-broker/
> book/chap-Messaging_User_Guide-Security.html#sect-
> Messaging_User_Guide-Security-Encryption_using_SSL) .. the entire
> "security" section is about authorization but absolutely nothing on the
> encryption portion itself other than "we use SSL and it's better than
> SASL.  Set require-ecryption=yes".
> Thanks,
> -Peter

Re: [VOTE] Release Qpid JMS client 0.20.0

[Jakub Scholz]

+1 ... I used the staged artefacts and run my tests against the C++ broker.

On Tue, Jan 17, 2017 at 2:20 PM, Robbie Gemmell 
wrote:

> On 16 January 2017 at 18:38, Robbie Gemmell 
> wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.20.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.20.0-rc1/
> >
> > Those files and the other maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1097
> >
> > 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-1097
> > 
> >   
> >
> > The dependency for the client itself would then be:
> >
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 0.20.0
> >   
>
> Making my +1 explicit
>
> I tested things out as follows:
> - Verified the checksum and signature files.
> - Checked LICENCE+NOTICE files present/correct.
> - Ran mvn apache-rat:check to verify licence headers.
> - Ran the build+tests from the source release archive, no issues.
> - Built the examples from the binary release archive using maven and
> ran against Qpid Dispatch master, Qpid CPP master (both built against
> Qpid Proton master), Qpid for Java master, ActiveMQ 5 master, and
> ActiveMQ Artemis master.
> - Built the examples using javac manually and run to verify required
> libs included in lib dir.
> - Ran the Joram JMS tests against the Qpid for Java master using the
> staging repo.
> - Ran the ActiveMQ 5 master tests using the staging repo.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid for Java 6.1.1 (RC1)

[Jakub Scholz]

+1 ... I checked the broker and also the 0-10 client. All looks OK.

On Wed, Dec 21, 2016 at 11:56 AM, Keith W  wrote:

> +1.
>
> My testing was:
>
> 1) Verified the md5/sha checksums on all distribution artefacts
> 2) Verified signatures on all all distribution artefacts
> 3) Built/ran test profiles mms for 0-9 and 0-10 from source bundle
> 4) Ran hello world against staged maven artefacts against broker from
> binary distribution artefact
>
> No issues encountered.
>
> On 19 December 2016 at 15:43, Lorenz Quack  wrote:
> > +1
> >
> > In addition to what Alex did I also:
> >  * checked the md5 and sha1 checksums
> >  * created a simple query in the WMC
> >  * created a simple dashboard in the WMC
> >
> >
> > On 19/12/16 15:18, Oleksandr Rudyy wrote:
> >>
> >> +1
> >>
> >> I performed the following testing of Qpid for Java 6.1.1:
> >> * started the broker
> >> * using Web Management Console created and bound a test queue
> >> * ran successfully Hello and Spout/Drain example against 6.1.1 broker
> >>
> >>
> >> On 19 December 2016 at 15:13, Oleksandr Rudyy  wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I have built a release candidate for a 6.1.1 Qpid for Java. Please,
> test
> >>> it
> >>> and vote accordingly.
> >>>
> >>> The list of changes can be found in Jira:
> >>>
> >>> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.1.1
> >>>
> >>> The source and binary bundles can be downloaded from here:
> >>> https://dist.apache.org/repos/dist/dev/qpid/java/6.1.1-rc1
> >>>
> >>> Those files and all other maven artifacts are staged for now at:
> >>> https://repository.apache.org/content/repositories/orgapacheqpid-1095
> >>>
> >>> Kind regards
> >>>
> >>> P.S. For testing of release artifacts using maven, please temporarily
> add
> >>> the staging repo into maven project pom.xml:
> >>>
> >>> 
> >>>  
> >>>staging
> >>>
> >>>
> >>> https://repository.apache.org/content/repositories/orgapacheqpid-
> 1095
> >>>  
> >>> 
> >>
> >> -
> >> 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: qpid-tool - call ID methodName ?

[Jakub Scholz]

You can run "schema" command. It will show you list of all the different
QMF classes. Afterwards you can call "schema " ... e.g. "schema
queue" and it will list details about the class. That includes the
attributes as well as the methods and their arguments. The method has to
correspond to the object you are calling it at - so if your ID is from a
queue, you can use the methods from a queue.

Regards
Jakub

On Mon, Dec 12, 2016 at 8:28 PM, Scott McDugle  wrote:

> When I'm using qpid-tool, there's a command: 'call  
> [] '
>
> I know how to find the ID.  What are the methodNames and args and/or how
> do I find them?
>
> I'm using the C++ Broker 1.35.
>
> Thanks,
> Scott
>
>
>

Re: [VOTE] Release Qpid CPP 1.36.0

[Jakub Scholz]

+1 ... I run tests using different 0-10 and 1.0 clients, all seems to be OK.

On Fri, Dec 9, 2016 at 7:42 PM, Robbie Gemmell 
wrote:

> On 9 December 2016 at 18:01, Robbie Gemmell 
> wrote:
> > Hi folks,
> >
> > I have put together a first spin for a Qpid CPP 1.36.0 release, please
> > test it and vote accordingly.
> >
> > The source archive can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/cpp/1.36.0-rc1/
> >
> > The JIRAs currently assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310520=12338222
> >
> > It is tagged as 1.36.0-rc1 from the 1.36.x branch.
> >
> > Regards,
> > Robbie
>
> Adding my +1 explicitly.
>
> I checked the RC out as follows:
>  - Verified the sig and checksum files.
>  - Checked LICENCE+NOTICE files present.
>  - Ran the build and tests against Proton 0.16.0 RC1.
>  - Ran the master AMQP 1.0 JMS client HelloWorld example against the
> built broker.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid for Java 6.1.0 (RC2)

[Jakub Scholz]

+1 ... I focused mainly on the broker and the AMQP 0-10 client, which I
tested also against various versions of the Qpid C++ broker.

On Thu, Nov 10, 2016 at 7:13 PM, Oleksandr Rudyy  wrote:

> Hi folks,
>
> Qpid for Java 6.1.0 RC2 is available for testing.
>
> The  changes against the following JIRAs have been made since RC1:
> QPID-7352 : [Java Broker] Principal serialisation
> QPID-7409 : Support preview of maps/list message content
> QPID-7460 : [Java Broker] Improve performance of the Json Config store with
> large numbers of object
> QPID-7462 : [Java Broker] Add experimental "pull" consumers to the broker
> QPID-7469 : [Java Broker] Improve VirtualHost#publishMessage
> QPID-7470 : [Java Broker] Address javax.xml.bind.DatatypeConverter
> shortcomings
> QPID-7471 : [Java Broker] MessageConverter should respect mimeType
> QPID-7474 : [Java Broker] Guard against NPE in StatisticsReportingTask
> QPID-7477 : [Java Broker] Recovery of Broker preferences should happen
> without holding VirtualHostPrincipal
> QPID-7478 : Add managed operation to reset statistics
> QPID-7479 : [Java Broker] Memory estimation formula fails to account for
> objects that comprise a persistent messages
> QPID-7480 : Incorrect error message when editing "number of connection
> threads" of a virtual host
> QPID-7481 : Statistics gathering screen label uses wrong unit
> QPID-7482 : Heartbeat screen label uses wrong units
> QPID-7483 : [Java Broker, WMC] Address minor UI issues
> QPID-7485 : [Java Broker] Make the path attribute immutable on file based
> authentication/group providers
> QPID-7488 : [Java Broker, WMC] Clicking on any of dashboard widget titlebar
> icons (collapse pane, edit, goto, or close) triggers widget dragging in IE
> QPID-7489 : [Java Broker] Only return false from
> AbstractQueue#attemptDelivery if remaining messages on queue can actually
> be consumed
> QPID-7490 : [Java Broker] Stop CreditCreditManager from spuriously
> notifying subscribers of credit increases
>
> The full list of 6.1.0 JIRAs is available at:
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.1
>
> The release source and binary bundles are available from:
> https://dist.apache.org/repos/dist/dev/qpid/java/6.1.0-rc2/
>
> The release maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1092
>
> Kind regards
> Alex
>
> P.S. For testing of 6.1.0 maven artifacts please add the staging repo into
> your maven project as below:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1092
> 
> 
>   
>

Re: [VOTE] Release Qpid Dispatch Router 0.7.0 (RC2)

[Jakub Scholz]

+1 ... I have build it from source and run my tests with different clients
and Qpid C++ broker against the RC2.

On Thu, Nov 10, 2016 at 7:26 PM, Ted Ross  wrote:

> I have built RC2 for Qpid Dispatch Router 0.7.0.  Please give it a test
> and cast your votes.
>
> The build artifacts can found here:
>
>   https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.7.0-rc2/
>
> The list of issues resolved is here:
>
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%
> 20DISPATCH%20AND%20fixVersion%20%3D%20%270.7.0%27%20ORDER%
> 20BY%20status%20ASC%2C%20key%20DESC
>
> The issues that were fixed between RC1 and RC2 are:
>
> DISPATCH-532 - man pages installed in wrong directory (man.X)
> DISPATCH-533 - Router crash in the 6-node example
> DISPATCH-535 - Use correct lifecycle management for Proton objects
> DISPATCH-550 - Assertion failure in router in larger scale networks
> DISPATCH-558 - Remove assertions in the core agent that fail due to
> malformed requests
>
> Thanks,
>
> -Ted
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: connection not free when client crashed

[Jakub Scholz]

Do your connections use heartbeat? The heartbeat will make sure that when
the client doesn't communicate within two heartbeat intervals, the broker
will close the connection. I believe that without the heartbeat, the broker
has to rely on the TCP stack which is not always reliable and might behave
differently on Windows versus Linux.

J.

On Tue, Oct 25, 2016 at 10:00 AM, 634749...@qq.com <634749...@qq.com> wrote:

> oker running on linux,it seems not exist this phenomenon; you can
> reproduce this phenomenon by th
>

Re: qpid-cpp-1.35 broker crashed with resource-limit-exceeded

[Jakub Scholz]

Can you reproduce it?

Maybe you can try to increase the log levels in the broker to get some more
information about why it crashed (
http://qpid.apache.org/releases/qpid-cpp-1.35.0/cpp-broker/book/ch01.html#RASC-logging-options).
If the broker crashed, you can also try to get a core dump for further
analysis. Following our discussion from the previous thread, it might be
also interesting to check the system logs. When the broker is killed by the
kernel because of missing memory, it also doesn't print anything into the
log.

J.

On Mon, Oct 24, 2016 at 8:46 PM, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:

> on't know why it crashed but I don't see any other message in the log
> other than that and broker processes is not running, i can run it in debug
> mode and see if i can get any clue. So ideally if the queue siz
>

Re: qpid-cpp-1.35 broker crashed with resource-limit-exceeded

[Jakub Scholz]

Hi Ram,

This should normally not crash the broker. This error should be only sent
to the client which exceeded the max queue size limit and that particular
client might be kicked out. But the broker should continue running and
serving other clients. Why do you think the broker crashed because of this?

J.

On Mon, Oct 24, 2016 at 6:04 PM, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:

> -10-24 15:36:21 [Broker] warning Exchange ax-ex-eaxgroup002 cannot
> deliver to  queue ax-q-eaxgroup002-consumer-group-001:
> resource-limit-exceeded: Maximum depth exceeded on
> ax-q-eaxgroup002-consumer-group-001: current=[count: 5843, size:
> 1073740027], max=[count: 100, size: 1073741824]
> (/builddir/build/BUILD/qpid-cpp-1.35.0/src/qpid/broker/Queue.cpp
>

Re: How to enable persistent message store in qpid-cpp-1.35.0

[Jakub Scholz]

Yeah, I know what you are talking about from my own experience. I guess
0.28 might have still used the old message store. It a bit depends on the
exact scenario, but in many cases the linear store caused significant
improvements compared to the old store. It is still not immediate, it can
still take quite a lot of time, but in my use cases it is significantly
better.

J.

On Fri, Oct 21, 2016 at 8:18 PM, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:

> Jakub,
>
> Thanks for clearing my doubts, yes i wanted to limit the memory usage and
> survive messages on broker restart, in that case i will use option3.
>
> Yes, in java broker will be available right way upon restart and it does
> message recovery in the background. In the 0.28 cpp version we see broker
> will take lot of time to recover if i have lot of messages to recover from
> disk and some times it times out, i hope we new version will have faster
> recovery mechanism.
>
> Ram
>
> On Fri, Oct 21, 2016 at 11:12 AM, Jakub Scholz <ja...@scholz.cz> wrote:
>
> > These are two separate things.
> >
> > The linearstore is the persistent message store. When you create a queue
> as
> > durable (and your queues are durable in the email above) and send
> durable /
> > persistent messages into the queue, the linear store will store all these
> > messages to the disk for recovery in case of broker restart. However, the
> > linear store it self doesn't offload them from memory. So they stay both
> in
> > memory and on disk. When you stop and start the broker, it will read them
> > from the disk into the memory and use them. This is what you are seeing
> > right now.
> >
> > Paging will take the messages from the memory and offload some parts of
> the
> > memory to disk (it will use separate files for that - not the same files
> as
> > the linearstore). Paging it self will only make sure that your memory
> > consumption is under control. But when you stop and start the broker, the
> > paging files are deleted and no message will be recovered from them.
> >
> > Of course you can combine both features and use them together. So
> depending
> > on what is your usecase and what you actually want to achieve you have to
> > configure the broker and the queues, for example:
> > 1) "I want the messages to survive the broker restart, but I have more
> then
> > enough memory" -> Durable queues / linerstore ON && Paging OFF
> > 2) "I don't need that the messages survive the restart, but I want to use
> > only small amounts of memory for looot of messages" -> Durable
> queues /
> > Linearstore OFF && Paging ON
> > 3) "I want the messages to survive broker restart and limit the RAM
> usage"
> > -> Durable queues / Linear store ON && Paging ON.
> >
> > Right now you seem to have the option 1 configured.
> >
> > I'm not sure what does "background recovery" do in Java broker. Does it
> > mean that the broker is available already before loading all the
> messages?
> > In that case no, the C++ broker will always first read all the messages
> > from the disk and only once they are loaded, it will be available for
> > connections. However, the startup is much faster with the linearstore
> than
> > it used to be several releases ago with the old message store.
> >
> > J.
> >
> >
> >
> > On Fri, Oct 21, 2016 at 7:54 PM, rammohan ganapavarapu <
> > rammohanga...@gmail.com> wrote:
> >
> > > Jakub,
> > >
> > > If by default its not flowing to disk, every thing should be in memory
> > > right and if that is the case on broker restart i should loose messages
> > > right? but in my case i do see messages got persisted on broker
> restart.
> > >
> > >
> > > [root@broker1 ~]# ps -ef |grep linearstore
> > > qpidd 1935 1  0 Oct20 ?00:00:54 /usr/sbin/qpidd
> --config
> > > /etc/qpid/qpidd.conf --daemon --module-dir=/usr/lib64/qpid/daemon/
> > > --load-module=/usr/lib64/qpid/daemon/linearstore.so
> > > --load-module=/usr/lib64/liblinearstoreutils.so --data-dir=/data
> > > --close-fd
> > > 9 --pidfile /var/run/qpidd.pid
> > >
> > > root 21233 21143  0 17:43 pts/000:00:00 grep linearstore
> > > [root@broker1 ~]# qpid-stat -q
> > > Queues
> > >   queue dur  autoDel  excl  msg
> > > msgIn  msgOut  bytes  bytesIn  bytesOut  cons  bind
> > >
> > > ==

Re: How to enable persistent message store in qpid-cpp-1.35.0

[Jakub Scholz]

 5.47k
> 5.47k 01.07g  1.07g   0 0 2
>   ax-q-eaxgroup002-consumer-group-001-dlY  0
> 0  0   0  00 0 2
>
>
> If you observer above, i have 5.47k messages in queue before and after
> broker restart if they are not flowing to disk and keeping them only in
> RAM, on broker restart i those queues and messages should go away right? am
> i missing any thing here?. Below is my queue config looks like.
>
> [root@broker1 ~]# python26 /usr/bin/qpid-config queues
> Queue NameAttributes
> =
> a98385a7-2be9-45bb-a823-5d996e34222d:0.0  auto-del excl
> ax-q-eaxgroup002-consumer-group-001   --durable --file-size=5120
> --file-count=64 --max-queue-size=1073741824 --max-queue-count=100
> --limit-policy=flow-to-disk --argument no-local=False
> ax-q-eaxgroup002-consumer-group-001-dl--durable --file-size=6000
> --file-count=4 --max-queue-size=52428800 --max-queue-count=10
> --limit-policy=flow-to-disk --argument no-local=False
>
> One more question, is  background recovery feature available in cpp broker
> as well like in java broker?
>
> Thanks,
> Ram
>
>
> On Fri, Oct 21, 2016 at 12:16 AM, Jakub Scholz <ja...@scholz.cz> wrote:
>
> > I think the docs just list an example of what you might get when running
> > qpid-config --help. But your actual qpid-config from 1.35.0 should nto
> > contain flow-to-disk anymore.
> >
> > Jakub
> >
> > On Fri, Oct 21, 2016 at 12:45 AM, rammohan ganapavarapu <
> > rammohanga...@gmail.com> wrote:
> >
> > > From the docs i still see "--limit-policy [none | reject |
> flow-to-disk"
> > to
> > > configure queues but its not supported in V1.35.0?
> > >
> > >
> > > https://qpid.apache.org/releases/qpid-cpp-1.35.0/cpp-
> > > broker/book/chapter-Managing-CPP-Broker.html#MgmtC-2B-2B-
> Usingqpidconfig
> > >
> > > --durableQueue is durable
> > > --file-count N (8)   Number of files in queue's persistence journal
> > > --file-size  N (24)  File size in pages (64Kib/page)
> > > --max-queue-size N   Maximum in-memory queue size as bytes
> > > --max-queue-count N  Maximum in-memory queue size as a number of
> > > messages
> > > --limit-policy [none | reject | flow-to-disk | ring | ring-strict]
> > >      Action taken when queue limit is reached:
> > >  none (default) - Use broker's default
> policy
> > >  reject - Reject enqueued messages
> > >  flow-to-disk   - Page messages to disk
> > >  ring   - Replace oldest
> > > unacquired message with new
> > >  ring-strict- Replace oldest message,
> > > reject if oldest is acquired
> > >
> > >
> > >
> > > On Thu, Oct 20, 2016 at 3:20 PM, Jakub Scholz <ja...@scholz.cz> wrote:
> > >
> > > > Hi,
> > > >
> > > > Do you have the module installed in the path you mentioned? If yes,
> > then
> > > > you should be able to load the module using the option
> > > > "--load-module=/usr/lib64/qpid/daemon/linearstore.so" or by placing
> > > > "load-module=/usr/lib64/qpid/daemon/linearstore.so" into your config
> > > file.
> > > > However, I believe that usually the store should be loaded by default
> > > when
> > > > it is installed. That is unless you specified that you want to start
> > the
> > > > broker without any modules with the no-module-dir option. If the
> module
> > > is
> > > > loaded, you should see in your log file something like this:
> > > > 2016-10-20 22:15:25 [Store] notice Linear Store: Store module
> > > initialized;
> > > > store-dir=/var/lib/qpidd/store
> > > >
> > > > Additionally to loading the store, you need to have the queues
> created
> > as
> > > > durable and send the messages as durable/persistent. Otherwise the
> > > > queues/messages will not use the persistent message store.
> > > >
> > > > Flow to disk feature has been removed some time ago. The
> functionality
> > it
> > > > provided (offloading messages from memory to disk) is now provided by
> > the
> > > > queue paging feature. Strangely, I can't find it described anywhere
> in
> > > the
> > > > Qpid C++ broker documentation. But you can have a look at my answer
> in
> > > this
> > > > thread -
> > > > http://qpid.2158936.n2.nabble.com/How-do-I-create-a-queue-
> > > > larger-than-available-RAM-td7643861.html
> > > > - it describes how to configure it and it should be still valid in
> > > 1.35.0.
> > > >
> > > > Regards
> > > > Jakub
> > > >
> > > > On Thu, Oct 20, 2016 at 11:56 PM, rammohan ganapavarapu <
> > > > rammohanga...@gmail.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > How to enable persistent message store in qpid-cpp-1.35 do i have
> to
> > > > > install/load "/usr/lib64/qpid/daemon/linearstore.so"? also how to
> > > > > configure
> > > > > flow_to_disk policy?
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Ram
> > > > >
> > > >
> > >
> >
>

Re: How to enable persistent message store in qpid-cpp-1.35.0

[Jakub Scholz]

I think the docs just list an example of what you might get when running
qpid-config --help. But your actual qpid-config from 1.35.0 should nto
contain flow-to-disk anymore.

Jakub

On Fri, Oct 21, 2016 at 12:45 AM, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:

> From the docs i still see "--limit-policy [none | reject | flow-to-disk" to
> configure queues but its not supported in V1.35.0?
>
>
> https://qpid.apache.org/releases/qpid-cpp-1.35.0/cpp-
> broker/book/chapter-Managing-CPP-Broker.html#MgmtC-2B-2B-Usingqpidconfig
>
> --durableQueue is durable
> --file-count N (8)   Number of files in queue's persistence journal
> --file-size  N (24)  File size in pages (64Kib/page)
> --max-queue-size N   Maximum in-memory queue size as bytes
> --max-queue-count N  Maximum in-memory queue size as a number of
> messages
> --limit-policy [none | reject | flow-to-disk | ring | ring-strict]
>  Action taken when queue limit is reached:
>  none (default) - Use broker's default policy
>  reject - Reject enqueued messages
>  flow-to-disk   - Page messages to disk
>  ring   - Replace oldest
> unacquired message with new
>  ring-strict- Replace oldest message,
> reject if oldest is acquired
>
>
>
> On Thu, Oct 20, 2016 at 3:20 PM, Jakub Scholz <ja...@scholz.cz> wrote:
>
> > Hi,
> >
> > Do you have the module installed in the path you mentioned? If yes, then
> > you should be able to load the module using the option
> > "--load-module=/usr/lib64/qpid/daemon/linearstore.so" or by placing
> > "load-module=/usr/lib64/qpid/daemon/linearstore.so" into your config
> file.
> > However, I believe that usually the store should be loaded by default
> when
> > it is installed. That is unless you specified that you want to start the
> > broker without any modules with the no-module-dir option. If the module
> is
> > loaded, you should see in your log file something like this:
> > 2016-10-20 22:15:25 [Store] notice Linear Store: Store module
> initialized;
> > store-dir=/var/lib/qpidd/store
> >
> > Additionally to loading the store, you need to have the queues created as
> > durable and send the messages as durable/persistent. Otherwise the
> > queues/messages will not use the persistent message store.
> >
> > Flow to disk feature has been removed some time ago. The functionality it
> > provided (offloading messages from memory to disk) is now provided by the
> > queue paging feature. Strangely, I can't find it described anywhere in
> the
> > Qpid C++ broker documentation. But you can have a look at my answer in
> this
> > thread -
> > http://qpid.2158936.n2.nabble.com/How-do-I-create-a-queue-
> > larger-than-available-RAM-td7643861.html
> > - it describes how to configure it and it should be still valid in
> 1.35.0.
> >
> > Regards
> > Jakub
> >
> > On Thu, Oct 20, 2016 at 11:56 PM, rammohan ganapavarapu <
> > rammohanga...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > How to enable persistent message store in qpid-cpp-1.35 do i have to
> > > install/load "/usr/lib64/qpid/daemon/linearstore.so"? also how to
> > > configure
> > > flow_to_disk policy?
> > >
> > >
> > > Thanks,
> > > Ram
> > >
> >
>

Re: How to enable persistent message store in qpid-cpp-1.35.0

[Jakub Scholz]

AFAIK the paging is turned off by default. So without specifying the paging
when creating the queue, everything will be kept in RAM. And when you run
out of memory the broker will crash - on Linux it will be usually killed by
the system. The paging and the persistent message store are now completely
separated. So even when your messages are persisted to the disk, they are
still kept in the memory (unless you turn the paging on).
If your broker is stopped because it run out of memory, it might not be
trivial to start it again. Because in case your messages are persisted on
disk, the broker will try to load them again during start and will very
likely run again out of memory during the startup (unless you freed some
additional memory by stopping some other applications). So if you are not
sure that you will fit into memory, you should probably enable the paging
when creating the queues.

Regards
Jakub

On Oct 21, 2016 12:40 AM, "rammohan ganapavarapu" <rammohanga...@gmail.com>
wrote:

> Jakub,
>
> Thanks for pointing me to right docs, so is there any default settings for
> how much/many messages can be in RAM and then flush to disk if i don't give
> any options while creating queues? if i dont create queues with "paging"
> options what is behavior of broker?
>
> Thanks,
> Ram
>
> On Thu, Oct 20, 2016 at 3:20 PM, Jakub Scholz <ja...@scholz.cz> wrote:
>
> > Hi,
> >
> > Do you have the module installed in the path you mentioned? If yes, then
> > you should be able to load the module using the option
> > "--load-module=/usr/lib64/qpid/daemon/linearstore.so" or by placing
> > "load-module=/usr/lib64/qpid/daemon/linearstore.so" into your config
> file.
> > However, I believe that usually the store should be loaded by default
> when
> > it is installed. That is unless you specified that you want to start the
> > broker without any modules with the no-module-dir option. If the module
> is
> > loaded, you should see in your log file something like this:
> > 2016-10-20 22:15:25 [Store] notice Linear Store: Store module
> initialized;
> > store-dir=/var/lib/qpidd/store
> >
> > Additionally to loading the store, you need to have the queues created as
> > durable and send the messages as durable/persistent. Otherwise the
> > queues/messages will not use the persistent message store.
> >
> > Flow to disk feature has been removed some time ago. The functionality it
> > provided (offloading messages from memory to disk) is now provided by the
> > queue paging feature. Strangely, I can't find it described anywhere in
> the
> > Qpid C++ broker documentation. But you can have a look at my answer in
> this
> > thread -
> > http://qpid.2158936.n2.nabble.com/How-do-I-create-a-queue-
> > larger-than-available-RAM-td7643861.html
> > - it describes how to configure it and it should be still valid in
> 1.35.0.
> >
> > Regards
> > Jakub
> >
> > On Thu, Oct 20, 2016 at 11:56 PM, rammohan ganapavarapu <
> > rammohanga...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > How to enable persistent message store in qpid-cpp-1.35 do i have to
> > > install/load "/usr/lib64/qpid/daemon/linearstore.so"? also how to
> > > configure
> > > flow_to_disk policy?
> > >
> > >
> > > Thanks,
> > > Ram
> > >
> >
>

Re: How to enable persistent message store in qpid-cpp-1.35.0

[Jakub Scholz]

Hi,

Do you have the module installed in the path you mentioned? If yes, then
you should be able to load the module using the option
"--load-module=/usr/lib64/qpid/daemon/linearstore.so" or by placing
"load-module=/usr/lib64/qpid/daemon/linearstore.so" into your config file.
However, I believe that usually the store should be loaded by default when
it is installed. That is unless you specified that you want to start the
broker without any modules with the no-module-dir option. If the module is
loaded, you should see in your log file something like this:
2016-10-20 22:15:25 [Store] notice Linear Store: Store module initialized;
store-dir=/var/lib/qpidd/store

Additionally to loading the store, you need to have the queues created as
durable and send the messages as durable/persistent. Otherwise the
queues/messages will not use the persistent message store.

Flow to disk feature has been removed some time ago. The functionality it
provided (offloading messages from memory to disk) is now provided by the
queue paging feature. Strangely, I can't find it described anywhere in the
Qpid C++ broker documentation. But you can have a look at my answer in this
thread -
http://qpid.2158936.n2.nabble.com/How-do-I-create-a-queue-larger-than-available-RAM-td7643861.html
- it describes how to configure it and it should be still valid in 1.35.0.

Regards
Jakub

On Thu, Oct 20, 2016 at 11:56 PM, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:

> Hi,
>
> How to enable persistent message store in qpid-cpp-1.35 do i have to
> install/load "/usr/lib64/qpid/daemon/linearstore.so"? also how to
> configure
> flow_to_disk policy?
>
>
> Thanks,
> Ram
>

Re: [VOTE] Release Qpid Proton 0.15.0

[Jakub Scholz]

+1

I used the RC with Qpid C++ broker and Dispatch router and run my tests
with different clients against it. All seems OK.

On Wed, Oct 12, 2016 at 7:06 PM, Robbie Gemmell 
wrote:

> On 10 October 2016 at 18:20, Robbie Gemmell 
> wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.15.0 Qpid Proton release as proposed,
> > please test it and vote accordingly.
> >
> > The source archive can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/proton/0.15.0-rc1/
> >
> > The maven artifacts for proton-j are staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1088
> >
> > The JIRAs still need tidied up a bit, but those currently assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12313720=12337973
> >
> > Regards,
> > Robbie
> >
> >
> > P.S. If you want to test things out using maven (e.g with your own build)
> > you can temporarily add this to your poms to access the staging repo:
> >
> >   
> > 
> >   staging
> >   https://repository.apache.org/content/
> repositories/orgapacheqpid-1088
> > 
> >   
> >
> > The dependency for proton-j would then be:
> >
> >   
> > org.apache.qpid
> > proton-j
> > 0.15.0
> >   
>
> +1
>
> I checked the RC out as follows:
>  - Verified the sig and checksum files.
>  - Checked LICENCE+NOTICE files present.
>  - Ran the CMake build+tests+install.
>  - Ran the Maven build+tests.
>  - Build the Qpid C++ 1.35.0 release against the install, ran the Qpid
> JMS HelloWorld example against the broker.
>  - Build Qpid Dispatch 0.7.0 RC1 against the install, ran the Qpid JMS
> HelloWorld example against the router.
>  - Used the proton-j staging repo to run the Qpid JMS client master
> build+tests.
>  - Used the proton-j staging repo to run the ActiveMQ master build and
> AMQP tests.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid JMS client 0.11.1

[Jakub Scholz]

+1. I used the staged artefacts to run my tests against the Qpid C++ broker.

On Fri, Sep 30, 2016 at 10:24 PM, Timothy Bish  wrote:

> +1
>
> * Reviewed the bin and src for license and notice files
> * Checked signatures and checksums
> * Built from source and ran the tests
> * Built ActiveMQ using staged bits and ran its tests
> * Ran the included example against an ActiveMQ 5.14.1 broker
>
>
> On 09/30/2016 11:24 AM, Robbie Gemmell wrote:
>
>> Hi folks,
>>
>> I have put together a spin for a 0.11.1 Qpid JMS client release, please
>> test it and vote accordingly.
>>
>> There are a few small changes included:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12314524=12338292
>>
>> The source and binary archives can be grabbed from:
>> https://dist.apache.org/repos/dist/dev/qpid/jms/0.11.1-rc1/
>>
>> Those files and the other maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1086
>>
>> 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-1086
>>  
>>
>>
>> The dependency for the client itself would then be:
>>
>>
>>  org.apache.qpid
>>  qpid-jms-client
>>  0.11.1
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>
>>
>>
>
> --
> 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
>
>

Re: Dispatch: ‘posix_memalign’, declared with attribute warn_unused_result [-Werror=unused-result]

[Jakub Scholz]

Thanks Ted. My build seems to work fine again now after your fix.

J.

On Tue, Sep 20, 2016 at 1:51 PM, Ted Ross <tr...@redhat.com> wrote:

> Jakub,
>
> This is a bug in the DISPATCH-511 update.  I'll get it fixed.
>
> -Ted
>
> On 09/19/2016 04:00 PM, Jakub Scholz wrote:
>
>> Hi,
>>
>> I seem to have problems with building latest version of Qpid Dispatch
>> (from
>> master) on some systems. In particular on Ubuntu it seems to crash with
>> the
>> error below which I guess is related to the DISPATCH 511 JIRA / commit
>> 566a1a1
>> <https://github.com/apache/qpid-dispatch/commit/566a1a19e2c6
>> 62b40aa4477421bddb51e4e7310c>.
>>
>> Interesting enough, it seems to work fine on CentOS 7.
>>
>> Is this a bug in the dispatch code? Or do I need to use different version
>> of some libraries?
>>
>> Thansk & Regards
>> Jakub
>>
>> vagrant@vagrant-ubuntu-trusty-64:~/qpid-dispatch/build$ make all
>> [  1%] Generating schema_enum.h, schema_enum.c
>> Scanning dependencies of target qpid-dispatch
>> [  3%] Building C object src/CMakeFiles/qpid-dispatch.dir/amqp.c.o
>> [  4%] Building C object src/CMakeFiles/qpid-dispatch.dir/bitmask.c.o
>> [  6%] Building C object src/CMakeFiles/qpid-dispatch.dir/buffer.c.o
>> [  7%] Building C object src/CMakeFiles/qpid-dispatch.dir/error.c.o
>> [  9%] Building C object src/CMakeFiles/qpid-dispatch.dir/compose.c.o
>> [ 10%] Building C object
>> src/CMakeFiles/qpid-dispatch.dir/connection_manager.c.o
>> [ 12%] Building C object src/CMakeFiles/qpid-dispatch.dir/container.c.o
>> [ 14%] Building C object src/CMakeFiles/qpid-dispatch.dir/dispatch.c.o
>> [ 15%] Building C object src/CMakeFiles/qpid-dispatch.dir/entity.c.o
>> [ 17%] Building C object src/CMakeFiles/qpid-dispatch.d
>> ir/entity_cache.c.o
>> [ 18%] Building C object src/CMakeFiles/qpid-dispatch.dir/hash.c.o
>> [ 20%] Building C object src/CMakeFiles/qpid-dispatch.dir/iovec.c.o
>> [ 21%] Building C object src/CMakeFiles/qpid-dispatch.dir/iterator.c.o
>> [ 23%] Building C object src/CMakeFiles/qpid-dispatch.dir/log.c.o
>> [ 25%] Building C object src/CMakeFiles/qpid-dispatch.dir/message.c.o
>> [ 26%] Building C object src/CMakeFiles/qpid-dispatch.dir/parse.c.o
>> [ 28%] Building C object src/CMakeFiles/qpid-dispatch.dir/policy.c.o
>> [ 29%] Building C object src/CMakeFiles/qpid-dispatch.d
>> ir/posix/driver.c.o
>> [ 31%] Building C object
>> src/CMakeFiles/qpid-dispatch.dir/posix/threading.c.o
>> In file included from
>> /home/vagrant/qpid-dispatch/src/posix/threading.c:27:0:
>> /home/vagrant/qpid-dispatch/src/posix/threading.c: In function
>> ‘sys_mutex’:
>> /home/vagrant/qpid-dispatch/include/qpid/dispatch/ctools.h:39:46: error:
>> ignoring return value of ‘posix_memalign’, declared with attribute
>> warn_unused_result [-Werror=unused-result]
>>  #define NEW_CACHE_ALIGNED(t,p) posix_memalign((void*) &(p), 64,
>> (sizeof(t)
>> + (sizeof(t) % 64 ? 64 - (sizeof(t) % 64) : 0)))
>>   ^
>> /home/vagrant/qpid-dispatch/src/posix/threading.c:40:5: note: in
>> expansion
>> of macro ‘NEW_CACHE_ALIGNED’
>>  NEW_CACHE_ALIGNED(sys_mutex_t, mutex);
>>  ^
>> /home/vagrant/qpid-dispatch/src/posix/threading.c: In function
>> ‘sys_cond’:
>> /home/vagrant/qpid-dispatch/include/qpid/dispatch/ctools.h:39:46: error:
>> ignoring return value of ‘posix_memalign’, declared with attribute
>> warn_unused_result [-Werror=unused-result]
>>  #define NEW_CACHE_ALIGNED(t,p) posix_memalign((void*) &(p), 64,
>> (sizeof(t)
>> + (sizeof(t) % 64 ? 64 - (sizeof(t) % 64) : 0)))
>>   ^
>> /home/vagrant/qpid-dispatch/src/posix/threading.c:76:5: note: in
>> expansion
>> of macro ‘NEW_CACHE_ALIGNED’
>>  NEW_CACHE_ALIGNED(sys_cond_t, cond);
>>  ^
>> cc1: all warnings being treated as errors
>> make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/posix/threading.c.o]
>> Error 1
>> make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2
>> make: *** [all] Error 2
>>
>>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Dispatch: ‘posix_memalign’, declared with attribute warn_unused_result [-Werror=unused-result]

[Jakub Scholz]

Hi,

I seem to have problems with building latest version of Qpid Dispatch (from
master) on some systems. In particular on Ubuntu it seems to crash with the
error below which I guess is related to the DISPATCH 511 JIRA / commit
566a1a1
.
Interesting enough, it seems to work fine on CentOS 7.

Is this a bug in the dispatch code? Or do I need to use different version
of some libraries?

Thansk & Regards
Jakub

vagrant@vagrant-ubuntu-trusty-64:~/qpid-dispatch/build$ make all
[  1%] Generating schema_enum.h, schema_enum.c
Scanning dependencies of target qpid-dispatch
[  3%] Building C object src/CMakeFiles/qpid-dispatch.dir/amqp.c.o
[  4%] Building C object src/CMakeFiles/qpid-dispatch.dir/bitmask.c.o
[  6%] Building C object src/CMakeFiles/qpid-dispatch.dir/buffer.c.o
[  7%] Building C object src/CMakeFiles/qpid-dispatch.dir/error.c.o
[  9%] Building C object src/CMakeFiles/qpid-dispatch.dir/compose.c.o
[ 10%] Building C object
src/CMakeFiles/qpid-dispatch.dir/connection_manager.c.o
[ 12%] Building C object src/CMakeFiles/qpid-dispatch.dir/container.c.o
[ 14%] Building C object src/CMakeFiles/qpid-dispatch.dir/dispatch.c.o
[ 15%] Building C object src/CMakeFiles/qpid-dispatch.dir/entity.c.o
[ 17%] Building C object src/CMakeFiles/qpid-dispatch.dir/entity_cache.c.o
[ 18%] Building C object src/CMakeFiles/qpid-dispatch.dir/hash.c.o
[ 20%] Building C object src/CMakeFiles/qpid-dispatch.dir/iovec.c.o
[ 21%] Building C object src/CMakeFiles/qpid-dispatch.dir/iterator.c.o
[ 23%] Building C object src/CMakeFiles/qpid-dispatch.dir/log.c.o
[ 25%] Building C object src/CMakeFiles/qpid-dispatch.dir/message.c.o
[ 26%] Building C object src/CMakeFiles/qpid-dispatch.dir/parse.c.o
[ 28%] Building C object src/CMakeFiles/qpid-dispatch.dir/policy.c.o
[ 29%] Building C object src/CMakeFiles/qpid-dispatch.dir/posix/driver.c.o
[ 31%] Building C object
src/CMakeFiles/qpid-dispatch.dir/posix/threading.c.o
In file included from
/home/vagrant/qpid-dispatch/src/posix/threading.c:27:0:
/home/vagrant/qpid-dispatch/src/posix/threading.c: In function ‘sys_mutex’:
/home/vagrant/qpid-dispatch/include/qpid/dispatch/ctools.h:39:46: error:
ignoring return value of ‘posix_memalign’, declared with attribute
warn_unused_result [-Werror=unused-result]
 #define NEW_CACHE_ALIGNED(t,p) posix_memalign((void*) &(p), 64, (sizeof(t)
+ (sizeof(t) % 64 ? 64 - (sizeof(t) % 64) : 0)))
  ^
/home/vagrant/qpid-dispatch/src/posix/threading.c:40:5: note: in expansion
of macro ‘NEW_CACHE_ALIGNED’
 NEW_CACHE_ALIGNED(sys_mutex_t, mutex);
 ^
/home/vagrant/qpid-dispatch/src/posix/threading.c: In function ‘sys_cond’:
/home/vagrant/qpid-dispatch/include/qpid/dispatch/ctools.h:39:46: error:
ignoring return value of ‘posix_memalign’, declared with attribute
warn_unused_result [-Werror=unused-result]
 #define NEW_CACHE_ALIGNED(t,p) posix_memalign((void*) &(p), 64, (sizeof(t)
+ (sizeof(t) % 64 ? 64 - (sizeof(t) % 64) : 0)))
  ^
/home/vagrant/qpid-dispatch/src/posix/threading.c:76:5: note: in expansion
of macro ‘NEW_CACHE_ALIGNED’
 NEW_CACHE_ALIGNED(sys_cond_t, cond);
 ^
cc1: all warnings being treated as errors
make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/posix/threading.c.o] Error 1
make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2
make: *** [all] Error 2

Re: [VOTE] Release Qpid JMS client 0.11.0

[Jakub Scholz]

+1 ... I took the staged artifacts and run my tests against different
versions of Qpid C++ broker (0.34, 1.35 and master) and Red Hat MRG-M 3.2.
All seems to work OK.

On Mon, Sep 5, 2016 at 5:47 PM, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.11.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.11.0-rc1/
>
> Those files and the other maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1085
>
> 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-1085
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.11.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Python support for AMQP 1.0?

[Jakub Scholz]

Hi Volker,

You can have a look here:
https://github.com/Eurex-Clearing-Messaging-Interfaces/Python-Code-Examples

In the proton_binding subdirectory there are examples with SSL client
authentication for both blocking and non blocking connection. Hope this
helps.

Jakub


On Thu, Sep 1, 2016 at 11:09 AM, Volker Diels-Grabsch  wrote:

> at is, using the Proton-Python binding, I want to connect to an AMQP
> 1.0 server with SSL and SSL client cert authentica
>