Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M10 (RC1)

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by './build.sh rat'
* Built from source and ran the test suite using the './build.sh test' command 
(dotnet 8.0.103, Ubuntu 22.04.2)

Tomas

On 2024/04/08 23:04:24 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M10 Qpid 
> proton-dotnet release,
> please give it a test out and vote accordingly.
> 
> Tests can be run using the build script in the source archive:
> 
> "./build.sh podman-test" or "./build.sh docker-test"
> 
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M10-rc1/
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353498
> 
> Regards
> 
> -- 
> Tim Bish
> 
> 
> -
> 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 protonj2 1.0.0-M20

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.21), OpenJDK Java 17 (17.0.9) and OpenJDK Java 21 (21.0.2) on Ubuntu 
22.04.2

Regards,
Tomas

On 2024/03/25 18:13:45 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M20 Qpid protonJ2 
> 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/protonj2/1.0.0-M20-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1276
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12354130
> 
> 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-1276
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M20
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M20
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> 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

[ANNOUNCE] Apache Qpid Broker-J 9.2.0 released

[Tomas Vavricka]

The Apache Qpid (http://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid Broker-J 9.2.0.

This is the latest release of pure java implementation of messaging
broker supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0,
ISO/IEC 19464, http://www.amqp.org) and legacy AMQP protocols 0-10,
0-91, 0-9 and 0-8.

Please visit Qpid project site for more details:
http://qpid.apache.org/components/broker-j/index.html

The release is available now from our website:
http://qpid.apache.org/download.html

The release brings bug fixes and improvements. The release notes can
be found at:
http://qpid.apache.org/releases/qpid-broker-j-9.2.0/release-notes.html

Thanks to all involved,
Qpid Team

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

[RESULT][VOTE] Release Qpid Broker-J 9.2.0 (RC4)

[Tomas Vavricka]

There were 4 binding +1 votes and no other votes received. The vote has passed.

I will add the files to the dist release repo and release the maven
staging repo shortly, updating the website and announcing after the
release has had time to sync to the CDN and maven central.

Regards,
Tomas

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

Re: [VOTE] Release Qpid Broker-J 9.2.0 (RC4)

[Tomas Vavricka]

+1

* verified signatures and checksum files
* executed mvn apache-rat:check
* executed the build, unit tests and integration tests using default profile on 
JDK 11/17
* executed unit tests and integration tests using profiles java-bdb.1-0 and 
java-dby.1-0 on JDK 11
* started Qpid Broker-J from binary on JDK 11, created queues, exchanges, 
bindings, trust stores, key stores, ports, authentication providers, loggers, 
access control providers and connection limit providers using REST API
* created JSON Virtual Host Node with BDB Virtual host using the web management 
console
* sent and received messages using Qpid JMS Client

Tomas

On 2024/02/08 10:49:38 Tomas Vavricka wrote:
> Hi all,
> 
> I built release artifacts for Qpid Broker-J version 9.2.0 RC4.
> Please, give them a test out and vote accordingly.
> 
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc4/
> 
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1275/
> 
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included in the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12354195
> 
> Regards,
> Tomas
> 
> P.S. For testing of maven broker staging repo artifacts, please add
> into to your project pom the staging repo as below:
> 
> 
>   
> staging
> 
> https://repository.apache.org/content/repositories/orgapacheqpid-1275/
>   
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

[VOTE] Release Qpid Broker-J 9.2.0 (RC4)

[Tomas Vavricka]

Hi all,

I built release artifacts for Qpid Broker-J version 9.2.0 RC4.
Please, give them a test out and vote accordingly.

The source and binary archives can be found at:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc4/

The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1275/

The new version brings a number of improvements and bug fixes.
You can find the full list of JIRAs included in the release here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12354195

Regards,
Tomas

P.S. For testing of maven broker staging repo artifacts, please add
into to your project pom the staging repo as below:


  
staging

https://repository.apache.org/content/repositories/orgapacheqpid-1275/
  


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

[CANCELLED][VOTE] Release Qpid Broker-J 9.2.0 (RC3)

[Tomas Vavricka]

The vote is cancelled due to the issue with VirtualHost creation. I
will cut a new release candidate for voting when issues will be fixed.

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

Re: [VOTE] Release Qpid Broker-J 9.2.0 (RC3)

[Tomas Vavricka]

Hi Alex,

thank you for checking the RC. I will cancel the vote and prepare a new RC when 
the issues are fixed.

Regards,
Tomas

On 2024/02/07 23:08:31 Oleksandr Rudyy wrote:
> +/-1
> 
> My tests included the following
> * started broker successfully from release bundle binaries using java 17 on
> fedora 38
> * executed successfully Hello World example from AMQP 0-9 JMS client bundle
> v6.4.0 :)
> * built broker from sources bundle with running all unit test successfully
> using default profile  with openjdk 17.0.9 2023-10-17 on fedora 38
> * ran successfully integration tests using profiles java-bdb.1-0 and
> java-bdb.0-9
> * verified checksums and signatures
> * open web management console and tried to invoke some management
> operations but found a couple of minor issues
>   * a creation of JSON Virtual Host Node with BDB Virtual host failed with
> the following error on Mozilla Firefox 122.0
>  Uncaught TypeError: dijit.registry.byId(...) is undefined
> _submit
> http://localhost:8080/js/qpid/management/addVirtualHostNodeAndVirtualHost.js:400
> _add
> http://localhost:8080/js/qpid/management/addVirtualHostNodeAndVirtualHost.js:363
> Dojo 6
> 2 addVirtualHostNodeAndVirtualHost.js:400:53
>  * the copyright years on the web management console are displayed as  ©
> 2004-2023... It might need bumping to 2024...
> 
> I am not sure that copyright is a show-stopper, but I think that the VH
> creation issue could be impactful for some users.
> 
> 
> 
> On Wed, 7 Feb 2024 at 11:31, Daniil Kirilyuk 
> wrote:
> 
> > + 1
> >
> > I checked out the following:
> > - Verified the signature and checksum files
> > - Checked for LICENCE and NOTICE files in the archive
> > - Checked licence headers in the source archive (mvn apache-rat:check)
> > - Built successfully from source (mvn clean install) under JDK 11 / JDK 17
> > - Ran successfully integration tests under JDK 17 (mvn verify
> > -DskipTests=false -DskipITs=false) using profiles java-mms.1-0 /
> > java-bdb.1-0 / java-dby.1-0 as well as java-mms.0-10 / java-bdb.0-10 /
> > java-dby.0-10
> > - Started broker and created / deleted a queue via web management console
> > (JDK 17)
> >
> > On Wed, 7 Feb 2024 at 09:33, Tomas Vavricka  wrote:
> >
> > > +1
> > >
> > > * verified signatures and checksum files
> > > * executed mvn apache-rat:check
> > > * executed the build, unit tests and integration tests using default
> > > profile on JDK 11/17
> > > * executed unit tests and integration tests using profiles java-bdb.1-0
> > > and java-dby.1-0 on JDK 11
> > > * started Qpid Broker-J from binary on JDK 11, created
> > > queues/exchanges/ports/... via REST API
> > > * sent and received messages using Qpid JMS Client
> > >
> > > Tomas
> > >
> > > On 2024/02/06 12:52:21 Tomas Vavricka wrote:
> > > > Hi all,
> > > >
> > > > I built release artifacts for Qpid Broker-J version 9.2.0 RC3.
> > > > Please, give them a test out and vote accordingly.
> > > >
> > > > The source and binary archives can be found at:
> > > > https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc3/
> > > >
> > > > The maven artifacts are also staged at:
> > > > https://repository.apache.org/content/repositories/orgapacheqpid-1274/
> > > >
> > > > The new version brings a number of improvements and bug fixes.
> > > > You can find the full list of JIRAs included in the release here:
> > > >
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12354195
> > > >
> > > > Regards,
> > > > Tomas
> > > >
> > > > P.S. For testing of maven broker staging repo artifacts, please add
> > > > into to your project pom the staging repo as below:
> > > >
> > > > 
> > > >   
> > > > staging
> > > > 
> > > https://repository.apache.org/content/repositories/orgapacheqpid-1274/
> > > 
> > > >   
> > > > 
> > > >
> > > > -
> > > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > > > For additional commands, e-mail: users-h...@qpid.apache.org
> > > >
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > > For additional commands, e-mail: users-h...@qpid.apache.org
> > >
> > >
> >
> 

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

Re: [VOTE] Release Qpid Broker-J 9.2.0 (RC3)

[Tomas Vavricka]

+1

* verified signatures and checksum files
* executed mvn apache-rat:check
* executed the build, unit tests and integration tests using default profile on 
JDK 11/17
* executed unit tests and integration tests using profiles java-bdb.1-0 and 
java-dby.1-0 on JDK 11
* started Qpid Broker-J from binary on JDK 11, created 
queues/exchanges/ports/... via REST API
* sent and received messages using Qpid JMS Client

Tomas

On 2024/02/06 12:52:21 Tomas Vavricka wrote:
> Hi all,
> 
> I built release artifacts for Qpid Broker-J version 9.2.0 RC3.
> Please, give them a test out and vote accordingly.
> 
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc3/
> 
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1274/
> 
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included in the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12354195
> 
> Regards,
> Tomas
> 
> P.S. For testing of maven broker staging repo artifacts, please add
> into to your project pom the staging repo as below:
> 
> 
>   
> staging
> 
> https://repository.apache.org/content/repositories/orgapacheqpid-1274/
>   
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

[VOTE] Release Qpid Broker-J 9.2.0 (RC3)

[Tomas Vavricka]

Hi all,

I built release artifacts for Qpid Broker-J version 9.2.0 RC3.
Please, give them a test out and vote accordingly.

The source and binary archives can be found at:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc3/

The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1274/

The new version brings a number of improvements and bug fixes.
You can find the full list of JIRAs included in the release here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12354195

Regards,
Tomas

P.S. For testing of maven broker staging repo artifacts, please add
into to your project pom the staging repo as below:


  
staging

https://repository.apache.org/content/repositories/orgapacheqpid-1274/
  


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

[CANCELLED][VOTE] Release Qpid Broker-J 9.2.0 (RC2)

[Tomas Vavricka]

The vote is cancelled due to the issues with configuration upgrade. I
will cut a new release candidate for voting when issues will be fixed.

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

[VOTE] Release Qpid Broker-J 9.2.0 (RC2)

[Tomas Vavricka]

Hi all,

I built release artifacts for Qpid Broker-J version 9.2.0 RC2.
Please, give them a test out and vote accordingly.

The source and binary archives can be found at:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc2/

The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1273/

The new version brings a number of improvements and bug fixes.
You can find the full list of JIRAs included in the release here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12354195

Regards,
Tomas

P.S. For testing of maven broker staging repo artifacts, please add
into to your project pom the staging repo as below:


  
staging

https://repository.apache.org/content/repositories/orgapacheqpid-1273/
  


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

[CANCELLED][VOTE] Release Qpid Broker-J 9.2.0

[Tomas Vavricka]

The vote is cancelled due to the issues with configuration upgrade. I
will cut a new release candidate for voting when issues will be fixed.

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

Re: [VOTE] Release Qpid Broker-J 9.2.0

[Tomas Vavricka]

Hi Robbie,

thank you for pointing this out. When Daniil implements the changes I will cut 
a new release candidate.

Regards,
Tomas

On 2024/01/31 17:41:03 Robbie Gemmell wrote:
> I took a skim of the changes, and ended up leaving some comments on
> https://github.com/apache/qpid-broker-j/pull/235 rather than getting
> as far as testing the release in the usual ways.
> 
> Some of the changes made there just dont appear to make sense to me
> from first glance. I need to look further into the actual behaviour as
> what it suggests doesnt seem good, and yet the expected behaviour of
> the change also really isnt clear.
> 
> On Wed, 31 Jan 2024 at 12:02, Tomas Vavricka  wrote:
> >
> > Hi all,
> >
> > I built release artifacts for Qpid Broker-J version 9.2.0 RC1.
> > Please, give them a test out and vote accordingly.
> >
> > The source and binary archives can be found at:
> > https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc1/
> >
> > The maven artifacts are also staged at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1272/
> >
> > The new version brings a number of improvements and bug fixes.
> > You can find the full list of JIRAs included in the release here:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12354195
> >
> > Regards,
> > Tomas
> >
> > P.S. For testing of maven broker staging repo artifacts, please add
> > into to your project pom the staging repo as below:
> >
> > 
> >   
> > staging
> > 
> > https://repository.apache.org/content/repositories/orgapacheqpid-1272/
> >   
> > 
> >
> > -
> > 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

[VOTE] Release Qpid Broker-J 9.2.0

[Tomas Vavricka]

Hi all,

I built release artifacts for Qpid Broker-J version 9.2.0 RC1.
Please, give them a test out and vote accordingly.

The source and binary archives can be found at:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc1/

The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1272/

The new version brings a number of improvements and bug fixes.
You can find the full list of JIRAs included in the release here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12354195

Regards,
Tomas

P.S. For testing of maven broker staging repo artifacts, please add
into to your project pom the staging repo as below:


  
staging

https://repository.apache.org/content/repositories/orgapacheqpid-1272/
  


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

Re: [VOTE] enroll Proton and Dispatch in Packit-as-a-Service CI offering from Fedora

[Tomas Vavricka]

+1

On 2024/01/12 16:11:01 Jiri Daněk wrote:
> I'd like to enable Packit-as-a-Service (
> https://github.com/marketplace/packit-as-a-service) for Qpid Proton and
> Qpid Dispatch GitHub repositories, so that every new PR gets tested on
> Fedora infrastructure (latest released Fedora and Fedora Rawhide).
> 
> There are three (gradually more involved) ways to use Packit:
> 
> 1. use it as a CI system that runs on Fedora (configurable version and
> system architecture (x86_64, aarch64). The job steps are incidentally
> written in a RPM spec file, but we don't use the produced RPM
> 2. write the spec in a way that it builds useful RPM, but don't publish the
> rpm and don't synchronize the spec file with the spec file that Fedora uses
> in its Proton build
> 3. keep the RPM specs in sync with fedora, when new Proton is released, use
> a single packit command to propose spec changes and version upgrade from
> the upstream proton spec to Fedora Rawhide
> 
> My intention is to get Proton all the way to the third scenario.
> 
> There are three steps to do this:
> 
> First, if the plan is approved in a vote here, ASF infra will enable the
> GitHub integration, https://issues.apache.org/jira/browse/INFRA-25349
> (authed link)
> 
> Then, a RPM spec file needs to be written and committed to the repository.
> I volunteer to do that. The Packit CI job will be building from this spec
> file. I'd like to place the spec in a packaging/ sub directory, so that
> files for other packaging systems can be added later and it does not
> clutter the /.
> 
> Finally, the spec file should be brought into 1:1 correspondence with the
> spec file that Fedora itself uses. This way, changes to Fedora's spec can
> be proposed and tested in the ASF project first and then shipped into
> Fedora (Rawhide).
> 
> Benefits:
> 
> * Compilation of Fedora will be tested directly in the GitHub repo and
> issues can be fixed right away.
> * Packit infrastructure offers arm64 machines, so we can opt into compiling
> on arm as well
> 
> Supplementary information:
> 
> * Packit website: https://packit.dev/
> * Packit guide (GitHub integration): https://packit.dev/docs/guide
> * Packit-as-a-Service: https://github.com/marketplace/packit-as-a-service
> * Fedora wiki page: https://fedoraproject.org/wiki/Packit
> 
> Thank you,
> -- 
> Mit freundlichen Grüßen / Kind regards
> Jiri Daněk
> 

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

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M19 (RC1)

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.21) and OpenJDK Java 17 (17.0.9) on Ubuntu 22.04.2

Regards,
Tomas

On 2024/01/08 17:08:51 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M19 Qpid protonJ2 
> 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/protonj2/1.0.0-M19-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1271
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353988
> 
> 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-1271
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M19
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M19
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> 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 protonj2 1.0.0-M18

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.20.1) and OpenJDK Java 17 (17.0.8.1) on Ubuntu 22.04.2

Regards,
Tomas

On 2023/11/01 14:22:37 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M18 Qpid protonJ2 
> 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/protonj2/1.0.0-M18-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1270
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353499
> 
> 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-1270
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M18
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M18
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> 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 2.5.0

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.20.1) and OpenJDK Java 17 (17.0.8) on Ubuntu 22.04.2

Regards,
Tomas

On 2023/10/26 16:46:27 Robbie Gemmell wrote:
> Hi folks,
> 
> I have put together a spin for a 2.5.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
> 
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/2.5.0-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1269
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12353391
> 
> 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-1269
> 
>   
> 
> The dependency for the client itself would then be:
> 
>   
> org.apache.qpid
> qpid-jms-client
> 2.5.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 1.11.0

[Tomas Vavricka]

+1

On 2023/10/30 08:41:04 Tomas Vavricka wrote:
> * Verified the signature and checksum files
> * Verified LICENCE and NOTICE files in archives
> * Verified source license headers by 'mvn apache-rat:check'
> * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
> (11.0.20.1) and OpenJDK Java 17 (17.0.8) on Ubuntu 22.04.2
> 
> Regards,
> Tomas
> 
> On 2023/10/26 16:08:56 Robbie Gemmell wrote:
> > Hi folks,
> > 
> > I have put together a spin for a 1.11.0 Qpid JMS client release,
> > please give it a test out and vote accordingly.
> > 
> > The staged source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/jms/1.11.0-rc1/
> > 
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1268
> > 
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12353390
> > 
> > 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-1268
> > 
> >   
> > 
> > The dependency for the client itself would then be:
> > 
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 1.11.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
> 
> 

-
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 1.11.0

[Tomas Vavricka]

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.20.1) and OpenJDK Java 17 (17.0.8) on Ubuntu 22.04.2

Regards,
Tomas

On 2023/10/26 16:08:56 Robbie Gemmell wrote:
> Hi folks,
> 
> I have put together a spin for a 1.11.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
> 
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.11.0-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1268
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12353390
> 
> 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-1268
> 
>   
> 
> The dependency for the client itself would then be:
> 
>   
> org.apache.qpid
> qpid-jms-client
> 1.11.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

[ANNOUNCE] Apache Qpid Broker-J 9.1.0 released

[Tomas Vavricka]

The Apache Qpid (http://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid Broker-J 9.1.0.

This is the latest release of pure java implementation of messaging broker
supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC
19464,
http://www.amqp.org) and legacy AMQP protocols 0-10, 0-91, 0-9 and 0-8.

Please visit Qpid project site for more details:
http://qpid.apache.org/components/broker-j/index.html

The release is available now from our website:
http://qpid.apache.org/download.html

The release brings bug fixes and improvements. The release notes can
be found at:
http://qpid.apache.org/releases/qpid-broker-j-9.1.0/release-notes.html

Thanks to all involved,
Qpid Team

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

[RESULT][VOTE] Release Qpid Broker-J 9.1.0 (RC2)

[Tomas Vavricka]

There were 3 binding +1 votes, 1 non-binding +1 vote, and no other
votes received. The vote has passed.

I will add the files to the dist release repo and release the maven
staging repo shortly, updating the website and announcing after the
release has had time to sync to the CDN and maven central.

Regards,
Tomas

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

Re: [VOTE] Release Qpid Broker-J 9.1.0 (RC2)

[Tomas Vavricka]

+1

* verified signatures and checksum files
* executed mvn apache-rat:check
* executed the build, unit tests and integration tests using default profile on 
JDK 11/17
* executed unit tests and integration tests using profiles java-bdb.1-0, 
java-bdb.0-10, java-bdb.0-9-1, java-bdb.0-9, java-dby.1-0, java-dby.0-10, 
java-dby.0-9-1 and java-dby.0-9 on JDK 11
* started Qpid Broker-J from binary on JDK 11, created 
queues/exchanges/ports/... via REST API
* sent and received messages using Qpid JMS Client

Tomas

On 2023/08/25 10:10:02 Tomas Vavricka wrote:
> Hi all,
> 
> I built release artifacts for Qpid Broker-J version 9.1.0 RC2.
> Please, give them a test out and vote accordingly.
> 
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.1.0-rc2/
> 
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1267/
> 
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included in the release here:
> https://issues.apache.org/jira/projects/QPID/versions/12353514
> 
> Regards,
> Tomas
> 
> P.S. For testing of maven broker staging repo artifacts, please add
> into to your project pom the staging repo as below:
> 
> 
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1267/
> 
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

[VOTE] Release Qpid Broker-J 9.1.0 (RC2)

[Tomas Vavricka]

Hi all,

I built release artifacts for Qpid Broker-J version 9.1.0 RC2.
Please, give them a test out and vote accordingly.

The source and binary archives can be found at:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.1.0-rc2/

The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1267/

The new version brings a number of improvements and bug fixes.
You can find the full list of JIRAs included in the release here:
https://issues.apache.org/jira/projects/QPID/versions/12353514

Regards,
Tomas

P.S. For testing of maven broker staging repo artifacts, please add
into to your project pom the staging repo as below:



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



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

[CANCELLED][VOTE] Release Qpid Broker-J 9.1.0

[Tomas Vavricka]

The vote is cancelled due to the issue with the BDB store upgrade from
version 7 to 8. I will cut a new release candidate for voting when
issue will be fixed.

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

Re: [VOTE] Release Qpid Broker-J 9.1.0

[Tomas Vavricka]

Hi Alex,

thanks for checking the RC, I was able to replicate all test failures except 
SimpleConversionTest. The SimpleConversionTest passed in all profiles I tried.

Environment and failed test results below:

OS - Ubuntu 22.04.2 LTS
Java 11 - build 11.0.19+7-post-Ubuntu-0ubuntu122.04.1
Java 17 - build 17.0.8+7-Ubuntu-122.04

-Pjava-bdb.1-0

* UpgradeFrom7To8Test* - 1 test error
* ExportImportMessagesTest* - 1 test failure
* MultiNodeTest* - 4 test failures
* BDBUpgradeTest* - 3 test errors

-Pjava-bdb.0-10 or -Pjava-bdb.0-9-1

* UpgradeFrom7To8Test* - 1 test error
* ExportImportMessagesTest* - 1 test failure
* MultiNodeTest* - 3 test failures, 1 test error
* CompressedMessageContentTest - 4 test failures

Daniil created Pull requests below to fix the failing tests. 

https://github.com/apache/qpid-broker-j/pull/218 - fix for UpgradeFrom7To8Test
https://github.com/apache/qpid-broker-j/pull/220 - fix for 
CompressedMessageContentTest and ExportImportMessagesTest
https://github.com/apache/qpid-broker-j/pull/221 - fix for MultiNodeTest and 
BDBUpgradeTest

Since the UpgradeFrom7To8Test fix is done in the bdbstore module which is part 
of release I think it makes sense to cancel the vote and fix it along with 
other failing tests (all other fixes seem to be done in tests only).

Regards,
Tomas

On 2023/08/17 03:31:19 Oleksandr Rudyy wrote:
> Hi Tomas,
> 
> I tried to execute system tests using the 9.1 source bundle and JDK17
> on fedora 37.
> 
> The system tests invoked using default profile are all passing as expected
> 
> mvn clean install -DskipITs=false
> 
> However, with bdb profiles for AMQP 1.0 and 0-9 a number of tests are
> failing or hanging for me.
> Here are the failing test suites from various modules
> * CompressedMessageContentTest*
> * ExportImportMessagesTest*
> * UpgradeFrom7To8Test*
> * MultiNodeTest*
> * BDBUpgradeTest*
> 
> Here are hanging tests
> * SimpleConversionTest*
> 
> In order to ignore the failures I had  to exclude the tests using the below
> 
> mvn clean install -DskipITs=false  -Pjava-bdb.1-0
> -Dtest=\!CompressedMessageContentTest*,\!ExportImportMessagesTest*,\!UpgradeFrom7To8Test*,\!SimpleConversionTest*,\!MultiNodeTest*,\!BDBUpgradeTest*
>  -Dsurefire.failIfNoSpecifiedTests=false
> 
> To be fair I have not looked into the root causes of failures. It
> could be just test failures. The most worrying test failures are
> SimpleConversionTest covering the functionality to convert messages
> between different protocols.
> 
> Kind Regards,
> Alex
> 
> On Mon, 14 Aug 2023 at 11:04, Tomas Vavricka  wrote:
> >
> > Hi all,
> >
> > I built release artifacts for Qpid Broker-J version 9.1.0 RC1.
> > Please, give them a test out and vote accordingly.
> >
> > The source and binary archives can be found at:
> > https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.1.0-rc1/
> >
> > The maven artifacts are also staged at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1266/
> >
> > The new version brings a number of improvements and bug fixes.
> > You can find the full list of JIRAs included in the release here:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12353514
> >
> > Regards,
> > Tomas
> >
> > P.S. For testing of maven broker staging repo artifacts, please add
> > into to your project pom the staging repo as below:
> >
> > 
> > 
> >   staging
> >   
> > https://repository.apache.org/content/repositories/orgapacheqpid-1266/
> > 
> > 
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

Re: [VOTE] Release Qpid Broker-J 9.1.0

[Tomas Vavricka]

+1

* verified signatures and checksum files
* executed mvn apache-rat:check
* executed the build and tests on JDK 11/17
* started Qpid Broker-J from binary on JDK 11, created 
queues/exchanges/ports/... via REST API
* sent and received messages using Qpid JMS Client

Tomas

On 2023/08/14 10:03:47 Tomas Vavricka wrote:
> Hi all,
> 
> I built release artifacts for Qpid Broker-J version 9.1.0 RC1.
> Please, give them a test out and vote accordingly.
> 
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.1.0-rc1/
> 
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1266/
> 
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included in the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12353514
> 
> Regards,
> Tomas
> 
> P.S. For testing of maven broker staging repo artifacts, please add
> into to your project pom the staging repo as below:
> 
> 
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1266/
> 
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

[VOTE] Release Qpid Broker-J 9.1.0

[Tomas Vavricka]

Hi all,

I built release artifacts for Qpid Broker-J version 9.1.0 RC1.
Please, give them a test out and vote accordingly.

The source and binary archives can be found at:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.1.0-rc1/

The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1266/

The new version brings a number of improvements and bug fixes.
You can find the full list of JIRAs included in the release here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12353514

Regards,
Tomas

P.S. For testing of maven broker staging repo artifacts, please add
into to your project pom the staging repo as below:



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



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

[CANCELLED][VOTE] Release Qpid Broker-J 9.0.1

[Tomas Vavricka]

The vote is cancelled due to the issues with logging and licensing. I
will cut a new release candidate for voting when issues will be fixed.

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

Re: [VOTE] Release Qpid Broker-J 9.0.1

[Tomas Vavricka]

Hi Robbie,

thank you very much for testing and comments.

We will fix the mentioned issues and try to prepare RC2 next week.

Regards,
Tomas

On 2023/08/10 10:17:48 Robbie Gemmell wrote:
> -1
> 
> There are some blocking issues needing resolved, and the version
> itself seems off, both of which I'll elaborate on below. Beyond these
> I verified the assemblies as usual in terms of running the build,
> verifying checksums, licences etc and all seemed well other than the
> issues noted.
> 
> First, the version itself. Considering the JIRAs listed and related
> changes in them from just a quick skim, the 9.0.1 version doesn't
> actually seem appropriate given some of the very significant
> non-bugfix changes that have been made in the ~9 months since 9.0.0,
> various of which have at least some scope for breaking existing things
> people might be doing with 9.0.0. Seems like at minimum a 9.1.0
> release at this point if not more. E.g:
> - Updating from Jetty 9 to Jetty 11, itself significant but even more
> so in that it is also a switch from using javax to jakarta API
> packages.
> - SLF4J switched from 1.x to 2.x, which though API compatible, has an
> incompatible logging impl registration system and so can actually
> 'break' things applications do.
> - Significant 'clean up' that while hopefully
> non-impacting/behavioural, is significant churn and certainly doesnt
> seem suited to what appears named like a bug-fix release.
> - Swapping the tests from JUnit 4 to JUnit 5, though clearly that's
> mainly internal, would still seem unusual like the above.
> 
> Beyond the version seeming off, there are some actual problems with
> the code/build/packages also needing addressed.
> 
> The broker assembly is defaulting to DEBUG (or higher) level output to
> the console unlike previously. It is still only doing INFO to the log
> file. Perhaps related to the SLF4J change, though it would be quite
> odd given a recent Logback is being used, so maybe it's more likely
> the Logback change itself which is the issue. Or maybe just a wayward
> testing config change was committed. Who knows.
> 
> There are some licence related changes around the updates that are also 
> needed.
> 
> Skimming the diff I noticed an unsuitable licenceMerge config addition
> for the licence plugin:
> https://github.com/apache/qpid-broker-j/blob/2f99658e57b0cb3b2cad9c354aaf73f304dee870/pom.xml#L1675
> 
> The 'GPL2 w/ CPE' ID on its own is definitely not a merge candidate
> with the dual-licensed CDDL entries. We are allowed to ship CDDL bits
> which is why those are there, but are not allowed to ship GPL-only
> bits. That config should be removed.
> 
> Since this was added as part of
> https://github.com/apache/qpid-broker-j/commit/2f99658e57b0cb3b2cad9c354aaf73f304dee870
> to update Jetty it also seemed unnecessary anyway, as Jetty is ASLv2
> or EPL 2.0 licenced overall. If there was something tripping up on a
> dual-licensed thing then it may be a candidate for exclusion from the
> check instead (noticing the Logback one in the config above that). But
> definitely not merging 'GPL2 w/ CPE' into the CDDL entries.
> 
> Actually, digging further I notice the same commit added a couple of
> jakarta spec deps (based on the DEPENDENCIES_REFERENCE file [1]
> changes shown) which did reference 'GPL2 w/ CPE' so it may have been
> something around those...though they were also EPL 2.0 licensed, and
> so that would be what we select as we can actually ship that. I see
> those spec deps have since been removed as unnecessary, however the
> incorrect licenceMerge config remains. Also, no entry was added for
> them in the binary assembly LICENCE [2] file which there should have
> been, but clearly thats no longer an issue now as they were later
> removed again.
> 
> Looking at the wider changes from 9.0.0 to now though for the
> DEPENDENCIES_REFERENCE [1] file for the assembly, and indeed the
> actual binary assembly contents themselves, another change to the
> reference that should have flagged a potential change to the LICENCE
> [2] file was the addition of multiple Bouncy Castle deps
> (bcpkix-jdk18on, bcprov-jdk18on, bcutil-jdk18on) [3]. An entry for
> those should have been, but wasnt, added to the binary assembly
> LICENCE file since they are MIT licensed (the noted Bouncy Castle
> Licence https://www.bouncycastle.org/licence.html is just the MIT
> licence, as it mentions and a read confirms).
> 
> [1] 
> https://github.com/apache/qpid-broker-j/blob/main/apache-qpid-broker-j/src/main/assembly/dependency-verification/DEPENDENCIES_REFERENCE
> [2] 
> https://github.com/apache/qpid-broker-j/blob/main/apache-qpid-broker-j/src/main/assembly/LICENSE
> [3] 
> https://github.com/apache/qpid-broker-j/blo

[VOTE] Release Qpid Broker-J 9.0.1

[Tomas Vavricka]

Hi all,

I built release artifacts for Qpid Broker-J version 9.0.1 RC1.
Please, give them a test out and vote accordingly.

The source and binary archives can be found at:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.0.1-rc1/

The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1265/

The new version brings a number of improvements and bug fixes.
You can find the full list of JIRAs included in the release here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12352584

Regards,
Tomas

P.S. For testing of maven broker staging repo artefacts, please add
into to your project pom the staging repo as below:



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



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

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M16

[Tomas Vavricka]

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.18) and OpenJDK Java 17 (17.0.6) on Ubuntu 22.04.2

Regards,
Tomas

On 2023/06/26 16:54:28 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M16 Qpid ProtonJ2 
> 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/protonj2/1.0.0-M16-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1261
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353206
> 
> 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-1261
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M16
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M16
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> 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 1.9.0

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.18) and OpenJDK Java 17 (17.0.6) on Ubuntu 22.04.2

Regards,
Tomas

On 2023/05/17 16:44:40 Robbie Gemmell wrote:
> Hi folks,
> 
> I have put together a spin for a 1.9.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
> 
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.9.0-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1259
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352747
> 
> 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-1259
> 
>   
> 
> The dependency for the client itself would then be:
> 
>   
> org.apache.qpid
> qpid-jms-client
> 1.9.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 2.3.0

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.18) and OpenJDK Java 17 (17.0.6) on Ubuntu 22.04.2

Regards,
Tomas

On 2023/05/17 17:41:15 Robbie Gemmell wrote:
> I have put together a spin for a 2.3.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
> 
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/2.3.0-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1260
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352748
> 
> 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-1260
> 
>   
> 
> The dependency for the client itself would then be:
> 
>   
> org.apache.qpid
> qpid-jms-client
> 2.3.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 protonj2 1.0.0-M15

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
(11.0.18) and OpenJDK Java 17 (17.0.6) on Ubuntu 22.04.2

Regards,
Tomas

On 2023/05/02 17:27:36 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M15 Qpid ProtonJ2 
> 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/protonj2/1.0.0-M15-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1258
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353134
> 
> 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-1258
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M15
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M15
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> 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 ProtonJ2 1.0.0-M13 (RC1)

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source and ran tests (mvn clean install) on Java 11 and Java 17

On 2023/03/27 19:03:53 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M13 Qpid ProtonJ2 
> 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/protonj2/1.0.0-M13-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1256
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352763
> 
> 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-1256
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M13
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M13
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> 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 Proton-J 0.34.1

[Tomas Vavricka]

+1

* Verified the signature and checksum files
* Verified LICENCE and NOTICE files in archives
* Verified source license headers by 'mvn apache-rat:check'
* Built from source (mvn clean install) on Java 11 and Java 17

Tomas

On 2023/03/02 18:00:04 Robbie Gemmell wrote:
> Hi folks,
> 
> I have put together a spin for a Qpid Proton-J 0.34.1 release, please
> test it and vote accordingly.
> 
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.34.1-rc1/
> 
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1255
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352971
> 
> Regards,
> Robbie
> 
> P.S. If you want to test things out using maven 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-1255
> 
>   
> 
> The dependency for proton-j would then be:
> 
>   
> org.apache.qpid
> proton-j
> 0.34.1
>   
> 
> -
> 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: [RESULT][VOTE] Release Qpid Broker-J 9.0.0 (RC2)

[Tomas Vavricka]

Thanks for publishing. Website has been updated and the release announced.

Regards,
Tomas

On 2022/11/23 10:08:44 Robbie Gemmell wrote:
> I have added the files to the dist release repo and promoted the maven
> staging repo, they should sync to the CDN (for visibility see
> https://dlcdn.apache.org/qpid/broker-j/) and maven central (see e.g
> https://repo1.maven.org/maven2/org/apache/qpid/qpid-broker/) shortly,
> at which point the website can be updated and the release announced
> (and I'll then remove 8.0.6 from the dist release repo).
> 
> On Tue, 22 Nov 2022 at 09:20, Tomas Vavricka  wrote:
> >
> > There were 3 binding +1 votes, 1 non-binding +1 vote, 1 indicative +1 vote
> > and no other votes received. The vote has passed.
> >
> > I am not a PMC member, I would like to ask if a PMC member could publish
> > the release?
> >
> > Voting thread:
> > https://lists.apache.org/thread/sdn5mmf3glgjtdywbo9hlk7wo41o2pxy
> >
> > Regards,
> > Tomas
> 
> -
> 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

[ANNOUNCE] Apache Qpid Broker-J 9.0.0 released

[Tomas Vavricka]

The Apache Qpid (http://qpid.apache.org) community is pleased to
announce the immediate availability of Apache Qpid Broker-J 9.0.0.

This is the latest release of pure java implementation of messaging broker
supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC
19464,
http://www.amqp.org) and legacy AMQP protocols 0-10, 0-91, 0-9 and 0-8.

Please visit Qpid project site for more details:
http://qpid.apache.org/components/broker-j/index.html

The release is available now from our website:
http://qpid.apache.org/download.html

The release brings bug fixes and improvements. The release notes can
be found at:
http://qpid.apache.org/releases/qpid-broker-j-9.0.0/release-notes.html

Thanks to all involved,
Qpid Team

[RESULT][VOTE] Release Qpid Broker-J 9.0.0 (RC2)

[Tomas Vavricka]

There were 3 binding +1 votes, 1 non-binding +1 vote, 1 indicative +1 vote
and no other votes received. The vote has passed.

I am not a PMC member, I would like to ask if a PMC member could publish
the release?

Voting thread:
https://lists.apache.org/thread/sdn5mmf3glgjtdywbo9hlk7wo41o2pxy

Regards,
Tomas

Re: [VOTE] Release Qpid Broker-J 9.0.0 (RC2)

[Tomas Vavricka]

+1

* verified signatures and checksum files
* extracted source bundle using 'tar -xvf' or 'mc' on Ubuntu 22.04 and using 
7-zip (Windows 10)
* executed mvn apache-rat:check
* executed the build and tests with -DskipITs parameter on JDK 11/17
* started Qpid Broker-J, created queues/exchanges/ports/... via REST API
* sent and received messages using Qpid JMS Client

Tomas

On 2022/11/14 11:51:14 Tomas Vavricka wrote:
> Hi all,
> 
> I built release artefacts for Qpid Broker-J version 9.0.0 RC2.
> Please, give them a test out and vote accordingly.
> 
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.0.0-rc2/
> 
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1251/
> 
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included in the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12348607
> 
> Regards,
> Tomas
> 
> P.S. For testing of maven broker staging repo artefacts, please add
> into to your project pom the staging repo as below:
> 
> 
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1251/
> 
> 
> 

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

[VOTE] Release Qpid Broker-J 9.0.0 (RC2)

[Tomas Vavricka]

Hi all,

I built release artefacts for Qpid Broker-J version 9.0.0 RC2.
Please, give them a test out and vote accordingly.

The source and binary archives can be found at:
https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.0.0-rc2/

The maven artifacts are also staged at:
https://repository.apache.org/content/repositories/orgapacheqpid-1251/

The new version brings a number of improvements and bug fixes.
You can find the full list of JIRAs included in the release here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12348607

Regards,
Tomas

P.S. For testing of maven broker staging repo artefacts, please add
into to your project pom the staging repo as below:



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

Re: [VOTE] Release Qpid Broker-J 9.0.0

[Tomas Vavricka]

For a start, I created new Jenkins job for Java 17 with -DskipITs=false 
parameter https://ci-builds.apache.org/job/Qpid/job/Qpid-Broker-J-Test-JDK17/ 
and added -DskipITs=false parameter to existing Java 11 Jenkins job 
https://ci-builds.apache.org/job/Qpid/job/Qpid-Broker-J-Test-JDK11/.

I tried to add a Jenkins post build action 'Set GitHub commit status', but the 
post build action seems to require some changes to the github repository 
settings that I do not have permissions to set.

On 2022/11/11 16:09:42 Robbie Gemmell wrote:
> Np. Though it does suggest some update/rework of the CI jobs is in
> order, since the test issues should have been caught earlier. That in
> addition to perhaps preparing for removal of the Travis based jobs
> when Infra cease paying for Travis at the end of December.
> 
> On Fri, 11 Nov 2022 at 15:54, Tomas Vavricka  wrote:
> >
> > Hi Robbie,
> >
> > thank you very much for testing and comments.
> >
> > The points mentioned should be fixed in main branch.
> >
> > I will try to prepare RC2 next week (if no more issues).
> >
> > Regards,
> > Tomas
> >
> > On 2022/11/11 13:25:27 Robbie Gemmell wrote:
> > > One further issue noticed now the earlier test issue was resolved on
> > > main and the build got further this time:
> > >
> > > Another test failing on Java 17, probably related to
> > > https://issues.apache.org/jira/browse/QPID-8586 as it seems the same
> > > type of failure and area.
> > >
> > > mvn clean verify -DskipITs=false
> > >
> > > [INFO] Running org.apache.qpid.systest.disttest.endtoend.EndToEndTest
> > > [ERROR] Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time
> > > elapsed: 7.784 s <<< FAILURE! - in
> > > org.apache.qpid.systest.disttest.endtoend.EndToEndTest
> > > [ERROR] 
> > > testHillClimbing(org.apache.qpid.systest.disttest.endtoend.EndToEndTest)
> > >  Time elapsed: 0.073 s  <<< ERROR!
> > > java.lang.NullPointerException: Cannot invoke
> > > "javax.script.ScriptEngine.eval(java.io.Reader)" because "engine" is
> > > null
> > > at 
> > > org.apache.qpid.systest.disttest.endtoend.EndToEndTest.runController(EndToEndTest.java:288)
> > > at 
> > > org.apache.qpid.systest.disttest.endtoend.EndToEndTest.testHillClimbing(EndToEndTest.java:226)
> > >
> > >
> > >
> > > On Wed, 9 Nov 2022 at 13:03, Robbie Gemmell  
> > > wrote:
> > > >
> > > > I know the vote was already cancelled, but I had started testing and
> > > > so continued. Given that, my vote would have been -1 due some niggles
> > > > needing fixed.
> > > >
> > > > Quick list, with expansions later:
> > > > - Some licence file updates needed for the binary distribution.
> > > > - Possible extraneous tests jar file in the binary distribution.
> > > > - The binary distribution doesnt start on Java 17 due to a removed GC
> > > > option, same option causes a warning on Java 11.
> > > > - The E2E Conversion tests fail for me.
> > > > - I would delete the 9.0.x branch and use main.
> > > >
> > > >
> > > > ## Licence file issues and potentially stray jar in distribution:
> > > > - ASM / ASM-Tree was added to the binary distro and should be
> > > > mentioned in LICENCE given it isnt ASLv2; prodding this is part of
> > > > what dependencies reference file is for, LICENCE update should be made
> > > > at same time as adding the deps.
> > > > - A couple of logback -db jars added, names should be noted in LICENCE
> > > > with the others (assuming using the same licence).
> > > > - There is a possibly extraneous logback tests jar added to the
> > > > distribution, the dep should either be removed wherever it is coming
> > > > in (if not actually needed), or also covered in LICENCE.
> > > >
> > > >
> > > > ## The broker distribution cant start on Java 17 out the box due to
> > > > the default options set from JAVA_GC:
> > > > This seems unreasonable at this stage, especially for a new major this
> > > > long after Java 17 came out, and would be particularly odd given the
> > > > overall changes look to include JDK17 compatibility fixes.
> > > >
> > > > Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC
> > > > -XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError
> > > > Info: QPID_JAVA_MEM not set. Defaultin

Re: [VOTE] Release Qpid Broker-J 9.0.0

[Tomas Vavricka]

Hi Robbie,

thank you very much for testing and comments.

The points mentioned should be fixed in main branch.

I will try to prepare RC2 next week (if no more issues).

Regards,
Tomas

On 2022/11/11 13:25:27 Robbie Gemmell wrote:
> One further issue noticed now the earlier test issue was resolved on
> main and the build got further this time:
> 
> Another test failing on Java 17, probably related to
> https://issues.apache.org/jira/browse/QPID-8586 as it seems the same
> type of failure and area.
> 
> mvn clean verify -DskipITs=false
> 
> [INFO] Running org.apache.qpid.systest.disttest.endtoend.EndToEndTest
> [ERROR] Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 7.784 s <<< FAILURE! - in
> org.apache.qpid.systest.disttest.endtoend.EndToEndTest
> [ERROR] 
> testHillClimbing(org.apache.qpid.systest.disttest.endtoend.EndToEndTest)
>  Time elapsed: 0.073 s  <<< ERROR!
> java.lang.NullPointerException: Cannot invoke
> "javax.script.ScriptEngine.eval(java.io.Reader)" because "engine" is
> null
> at 
> org.apache.qpid.systest.disttest.endtoend.EndToEndTest.runController(EndToEndTest.java:288)
> at 
> org.apache.qpid.systest.disttest.endtoend.EndToEndTest.testHillClimbing(EndToEndTest.java:226)
> 
> 
> 
> On Wed, 9 Nov 2022 at 13:03, Robbie Gemmell  wrote:
> >
> > I know the vote was already cancelled, but I had started testing and
> > so continued. Given that, my vote would have been -1 due some niggles
> > needing fixed.
> >
> > Quick list, with expansions later:
> > - Some licence file updates needed for the binary distribution.
> > - Possible extraneous tests jar file in the binary distribution.
> > - The binary distribution doesnt start on Java 17 due to a removed GC
> > option, same option causes a warning on Java 11.
> > - The E2E Conversion tests fail for me.
> > - I would delete the 9.0.x branch and use main.
> >
> >
> > ## Licence file issues and potentially stray jar in distribution:
> > - ASM / ASM-Tree was added to the binary distro and should be
> > mentioned in LICENCE given it isnt ASLv2; prodding this is part of
> > what dependencies reference file is for, LICENCE update should be made
> > at same time as adding the deps.
> > - A couple of logback -db jars added, names should be noted in LICENCE
> > with the others (assuming using the same licence).
> > - There is a possibly extraneous logback tests jar added to the
> > distribution, the dep should either be removed wherever it is coming
> > in (if not actually needed), or also covered in LICENCE.
> >
> >
> > ## The broker distribution cant start on Java 17 out the box due to
> > the default options set from JAVA_GC:
> > This seems unreasonable at this stage, especially for a new major this
> > long after Java 17 came out, and would be particularly odd given the
> > overall changes look to include JDK17 compatibility fixes.
> >
> > Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC
> > -XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError
> > Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx512m
> > -XX:MaxDirectMemorySize=1536m
> > Unrecognized VM option 'UseConcMarkSweepGC'
> > Error: Could not create the Java Virtual Machine.
> > Error: A fatal exception has occurred. Program will exit.
> >
> > The same option also causes a warning when starting on Java 11 since
> > it was deprecated in Java 9.
> >
> >
> > ## E2E Conversion tests fail:
> >
> > Perhaps something to do with the updates of the tests maven-based
> > dependencies, and compatibility with other deps and/or the maven
> > version running the build. Failed for me on Java 17 and 11, using
> > Maven 3.8.6 and 3.8.5.
> >
> > Quick path to the failure without installing the dependent modules is:
> > mvn clean verify -DskipTests -DskipITs=false -am -pl
> > "org.apache.qpid:qpid-systests-end-to-end-conversion-tests"
> >
> > Failures are all like:
> >
> > [ERROR] 
> > correlationIdAsBytes(org.apache.qpid.systests.end_to_end_conversion.SimpleConversionTest)
> >  Time elapsed: 0.22 s  <<< ERROR!
> > java.util.concurrent.ExecutionException:
> > com.google.common.util.concurrent.ExecutionError:
> > java.lang.NoSuchMethodError: 'java.util.List
> > org.eclipse.aether.spi.connector.layout.RepositoryLayout.getChecksumAlgorithmFactories()'
> > at 
> > org.apache.qpid.systests.end_to_end_conversion.SimpleConversionTest.performTest(SimpleConversionTest.java:548)
> > at 
> > org.apache.qpid.systests.end_to_end_conversion.SimpleConversionTest.performSimpleTest(SimpleConversionTest.java:538)
> > at 
> > org.apache.qpid.systests.end_to_end_conversion.SimpleConversionTest.correlationIdAsBytes(SimpleConversionTest.java:184)
> > Caused by: com.google.common.util.concurrent.ExecutionError:
> > java.lang.NoSuchMethodError: 'java.util.List
> > org.eclipse.aether.spi.connector.layout.RepositoryLayout.getChecksumAlgorithmFactories()'
> > Caused by: java.lang.NoSuchMethodError: 'java.util.List
> > 

[CANCELLED][VOTE] Release Qpid Broker-J 9.0.0

[Tomas Vavricka]

The vote is cancelled due to the issues with truncating file paths in
source bundle when extracted by 7-zip or Midnight Commander (tar -xvf works
fine). I will cut a new release candidate for voting when issue will be
fixed.

Re: [VOTE] Release Qpid Broker-J 8.0.0

[Vavricka]

+1

* built from source
* executed system and integration tests
* installed broker with BDB store
* * added broker objects (queues/exchanges/ports/...) via REST API
* * password and external authentication
* * send and receive
* * message recovery after broker restart
* * ACL rights

Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [Qpid Broker-J] NullPointerException when using temporary queues

[Vavricka]

Hi Alex,

I created JIRA  QPID-8323   

Regards,
Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

[Qpid Broker-J] NullPointerException when using temporary queues

[Vavricka]

Hi,

during performance test there are created temporary exclusive autodelete
queues, then messages are sent to created temporary queues and then
temporary queues are deleted. All operation are done in parallel in multiple
threads.

Sometimes broker throws NullPointerException and then dies (broker survived
one NPE). Unfortunately I did not found deterministic steps to reproduce the
issue, but broker logs with exceptions could be helpful.

Qpid Broker-J: 7.1.2
Client library: qpid-proton-c-0.16.0-10.el6.x86_64 and
qpid-cpp-client-1.36.0-15.el6.x86_64
Operating System: 6.10

*First NPE crash:*

2019-06-13 13:33:47,000 INFO  [VirtualHostNode-default-Config]
(q.m.b.created) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
[vh(/default)/ex(direct/response)] BND-1001 : Create :
{bindingKey=response.USER.80e56e07-154e-4d44-abec-60800c18484b,
destination=qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/6e1e3346-a354-4b7d-9395-6067054e6d8b_/nondurable,
arguments={}}
2019-06-13 13:33:47,000 INFO  [VirtualHostNode-default-Config]
(q.m.a.allowed) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
ACL-1001 : Allowed : Consume Queue
NAME=qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/6e1e3346-a354-4b7d-9395-6067054e6d8b_/nondurable,DURABLE=false,EXCLUSIVE=true,TEMPORARY=true,AUTO_DELETE=true,VIRTUALHOST_NAME=default,CREATED_BY=USER
2019-06-13 13:33:47,001 INFO  [VirtualHostNode-default-Config]
(q.m.s.create) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
[sub:6,303(vh(/default)/qu(qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/6e1e3346-a354-4b7d-9395-6067054e6d8b_/nondurable)]
SUB-1001 : Create
2019-06-13 13:33:47,012 INFO  [VirtualHostNode-default-Config]
(q.m.a.allowed) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
ACL-1001 : Allowed : Create Queue
NAME=qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/888b6a37-54fa-4e13-8228-82f32e6f128c_/nondurable,DURABLE=false,EXCLUSIVE=true,TEMPORARY=true,AUTO_DELETE=true,VIRTUALHOST_NAME=default
2019-06-13 13:33:47,013 INFO  [VirtualHostNode-default-Config]
(q.m.q.created) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
[vh(/default)/qu(qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/888b6a37-54fa-4e13-8228-82f32e6f128c_/nondurable)]
QUE-1001 : Create : ID: 1303f679-9c4e-46ad-9aa4-7e68948a44e5 AutoDelete
Transient
2019-06-13 13:33:47,014 INFO  [VirtualHostNode-default-Config]
(q.m.b.created) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
[vh(/default)/ex(direct/response)] BND-1001 : Create :
{bindingKey=response.USER.4abd7047-2147-4dda-80a7-6cdb4fc3bd0e,
destination=qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/888b6a37-54fa-4e13-8228-82f32e6f128c_/nondurable,
arguments={}}
2019-06-13 13:33:47,014 INFO  [VirtualHostNode-default-Config]
(q.m.a.allowed) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
ACL-1001 : Allowed : Consume Queue
NAME=qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/888b6a37-54fa-4e13-8228-82f32e6f128c_/nondurable,DURABLE=false,EXCLUSIVE=true,TEMPORARY=true,AUTO_DELETE=true,VIRTUALHOST_NAME=default,CREATED_BY=USER
2019-06-13 13:33:47,015 INFO  [VirtualHostNode-default-Config]
(q.m.s.create) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
[sub:6,304(vh(/default)/qu(qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/888b6a37-54fa-4e13-8228-82f32e6f128c_/nondurable)]
SUB-1001 : Create
2019-06-13 13:33:47,017 INFO  [VirtualHostNode-default-Config]
(q.m.a.allowed) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
ACL-1001 : Allowed : Create Queue
NAME=qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/fce80719-4448-478f-add1-450f6b3c1770_/nondurable,DURABLE=false,EXCLUSIVE=true,TEMPORARY=true,AUTO_DELETE=true,VIRTUALHOST_NAME=default
2019-06-13 13:33:47,018 INFO  [VirtualHostNode-default-Config]
(q.m.q.created) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
[vh(/default)/qu(qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/fce80719-4448-478f-add1-450f6b3c1770_/nondurable)]
QUE-1001 : Create : ID: b118efc7-db6f-40f2-bf77-5a1c6c387caf AutoDelete
Transient
2019-06-13 13:33:47,019 INFO  [VirtualHostNode-default-Config]
(q.m.b.created) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
[vh(/default)/ex(direct/response)] BND-1001 : Create :
{bindingKey=response.USER.c38d77ca-18de-4747-a2f3-f5a43c584c5d,
destination=qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/fce80719-4448-478f-add1-450f6b3c1770_/nondurable,
arguments={}}
2019-06-13 13:33:47,019 INFO  [VirtualHostNode-default-Config]
(q.m.a.allowed) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]
ACL-1001 : Allowed : Consume Queue
NAME=qpidsub_/938f3368-bae4-4b5c-a549-e326ad76858e_/fce80719-4448-478f-add1-450f6b3c1770_/nondurable,DURABLE=false,EXCLUSIVE=true,TEMPORARY=true,AUTO_DELETE=true,VIRTUALHOST_NAME=default,CREATED_BY=USER
2019-06-13 13:33:47,020 INFO  [VirtualHostNode-default-Config]
(q.m.s.create) - [con:1,107(USER@/172.16.11.49:49824/default)/ch:0]

Re: [Java Broker] Connection to broker using public key of certification authority in broker truststore

[Vavricka]

Hi,

thank you for quick replies.

When I checked system tests I remembered there is property "Peers only" set
to true in truststore in our broker setup.

I set "Peers only" to false, restarted broker and I was able to connect with
certificate signed by custom CA.

Best Regards,
Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

[Java Broker] Connection to broker using public key of certification authority in broker truststore

[Vavricka]

Hi,

I tried to authenticate via certificate which is signed by my own
certificate authority and only certificate authority public key is present
in broker. 

Steps I have done:
* create certificate authority
* add public CA key to broker truststore (certutil DB in C++ broker)
* sign client private key by CA
* use signed private certificate in client to connect to broker

When I perform steps above I am able to connect to C++ broker if only public
CA key is present in broker certificate DB. When I used same steps on Java
Broker I get exception 'javax.net.ssl.SSLException: Received fatal alert:
certificate_unknown'.

Am I doing something wrong?

Does Java Broker supports this feature?

qpid-cpp version 1.36.0
Java Broker version 7.0.4

Best Regards,
Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

[Broker-J] Limit connections per user

[Vavricka]

Hi,

is it possible to limit maximum number of AMQP connections per user basis?

I can set maximum number of connections for AMQP port, but then one user can
create maximum number of connections and this user will block other users
connections.

Best regards,
Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [Broker-J] Detect idle connections

[Vavricka]

JIRA created - https://issues.apache.org/jira/browse/QPID-8240

Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [VOTE] Release Apache Qpid Broker-J 7.0.4

[Vavricka]

+1 

* checkout tag 7.0.4 from git repository 
* build using mvn clean package (including tests) 
* started broker on Debian 9
* checked if only user which created temporary queue, can consume message
when rule 'ACL ALLOW-LOG OWNER CONSUME QUEUE' is applied
* created queue and exchange with name containing dot using Web Management
Console

Tomas 


Oleksandr Rudyy wrote
> Hi all,
> 
> I built a release candidate for a Qpid Broker-J 7.0.4.
> 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/broker-j/7.0.4-rc1
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1141
> 
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12343040
> 
> Regards,
> Alex
> 
> P.S. For testing of maven broker staging repo artefacts, please add into
> to
> your poms the staging repo as below:
> 
>   
> 
> 
> 
>   
> 
> staging
> 
>   
> 
> https://repository.apache.org/content/repositories/orgapacheqpid-1141
> 
> 
> 
>   
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [Java Broker] Temporary queues ACLs for multiple users

[Vavricka]

Hi Keith,

excellent idea, this will completely solve our use case.

Regards,
Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [Java Broker] Temporary queues ACLs for multiple users

[Vavricka]

Hi Keith,

thanks for explanation.

It will be great if you can post skeletal code of ACL module.

Tomas


Keith Wall wrote
> Hi Tomas
> 
> Unfortunately, Broker-J's access_control plugin is not too good.  It
> is something we would like to rework when schedules allow.  The
> current module actually uses an object modal that pre-dates the
> current one - which leads to user confusion and an ugly adaption layer
> in the code.  The ACL also assumes AMQP 0-x conventions - publishing
> only to exchanges and consuming from queues when expressing rules
> which creates a further wrinkle when using AMQP 1.0.
> 
> The current module lets you specify rules that match objects using
> zero or more property qualifiers (e.g. name="foo" or type="fanout"),
> so it is possible to write rules about named objects in your system
> and all objects matching certain criteria.   For temporary queues,
> this doesn't work well as you have discovered.  It is possible to say
> that user foo can (or cannot) consume from any temporary queue using
> the temporary=true qualifier, but it is not possible to be specific,
> but you cannot express a rule that gives users to temporary queues
> that they have created.
> 
> The ACL mechanism is pluggable - so it would be possible to write a
> module that would give the behaviour you need.  You would need to look
> at the AccessControlProvider and AccessControl interfaces.  The Broker
> supports one or more access control providers.  It consults each
> AccessControlProvider in order until one make a decision that is not
> DEFER.  So you could hopefully write a simple ACL module that you give
> you the additional behaviour you need and fallback on access_control
> plugin for everything else.  If you want to explore this route, I
> could share some skeletal code to help get you started.
> 
> Turning to your last point, when using AMQP 1.0 and wishing to
> permission publishing directly to queues, as access_control plugin
> knows only AMQP 0-x conventions you have to permission the default
> exchange.
> 
> ACL ALLOW-LOG foo PUBLISH EXCHANGE name="" routingKey="queueName"
> 
> Hope this helps.
> 
> Keith
> 
> On 5 April 2018 at 14:46, Vavricka 

> vavricka.tomas@

>  wrote:
>> Hi,
>>
>> I am trying to get working temporary queues on Java Broker. Each user
>> should
>> have access only to queue which he created.
>>
>> ACL rights:
>>
>> ACL ALLOW-LOG user1 ACCESS VIRTUALHOST
>> ACL ALLOW-LOG user1 CREATE QUEUE temporary="true" owner="user1"
>> ACL ALLOW-LOG user1 CONSUME QUEUE temporary="true" owner="user1"
>>
>> ACL ALLOW-LOG user2 ACCESS VIRTUALHOST
>> ACL ALLOW-LOG user2 CREATE QUEUE temporary="true" owner="user2"
>> ACL ALLOW-LOG user2 CONSUME QUEUE temporary="true" owner="user2"
>>
>> I successfully create temporary queue by JMS method "TemporaryQueue
>> temporaryQueue = session.createTemporaryQueue()", queue is correctly
>> created
>> on broker, but owner is not set in webgui (however createdBy and
>> lastUpdatedBy in JSON is correctly set to corresponding user).
>>
>> When I try to create consumer by "MessageConsumer consumer =
>> session.createConsumer(temporaryQueue)", I get "Permission CREATE is
>> denied
>> for : Consumer ...". When owner is not set in CONSUME ACL I can create
>> consumer without error, but both users can consume same queue. Is there
>> any
>> different way to distinguish temporary queues, so one user cannot read
>> other
>> user messages?
>>
>> Another issue is I cannot sent messages directly to temporary queue. When
>> I
>> try to send message I get error "Permission PERFORM_ACTION(publish) is
>> denied for : Queue 'TempQueueba2f889e-f95c-49d4-8c15-023e62666320'". We
>> could utilize sending messages directly to queue, because we cannot
>> dynamically create exchange binding by REST API. Or is there any way to
>> set
>> bindings by JMS?
>>
>> Java Broker 7.0.3
>> Qpid JMS client 0.31.0
>>
>> Tomas
>>
>>
>>
>> --
>> Sent from:
>> http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>>
>> -
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache

>>
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

[Java Broker] Temporary queues ACLs for multiple users

[Vavricka]

Hi, 

I am trying to get working temporary queues on Java Broker. Each user should
have access only to queue which he created.

ACL rights:

ACL ALLOW-LOG user1 ACCESS VIRTUALHOST
ACL ALLOW-LOG user1 CREATE QUEUE temporary="true" owner="user1"
ACL ALLOW-LOG user1 CONSUME QUEUE temporary="true" owner="user1"

ACL ALLOW-LOG user2 ACCESS VIRTUALHOST
ACL ALLOW-LOG user2 CREATE QUEUE temporary="true" owner="user2"
ACL ALLOW-LOG user2 CONSUME QUEUE temporary="true" owner="user2"

I successfully create temporary queue by JMS method "TemporaryQueue
temporaryQueue = session.createTemporaryQueue()", queue is correctly created
on broker, but owner is not set in webgui (however createdBy and
lastUpdatedBy in JSON is correctly set to corresponding user).

When I try to create consumer by "MessageConsumer consumer =
session.createConsumer(temporaryQueue)", I get "Permission CREATE is denied
for : Consumer ...". When owner is not set in CONSUME ACL I can create
consumer without error, but both users can consume same queue. Is there any
different way to distinguish temporary queues, so one user cannot read other
user messages? 

Another issue is I cannot sent messages directly to temporary queue. When I
try to send message I get error "Permission PERFORM_ACTION(publish) is
denied for : Queue 'TempQueueba2f889e-f95c-49d4-8c15-023e62666320'". We
could utilize sending messages directly to queue, because we cannot
dynamically create exchange binding by REST API. Or is there any way to set
bindings by JMS?

Java Broker 7.0.3
Qpid JMS client 0.31.0

Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [Java Broker] Select certificate from broker keystore

[Vavricka]

Hi,

thanks for quick reply. We are eager for Java Broker 7.0.3.

Regards,
Tomas


Keith Wall wrote
> Hi Tomas,
> 
> It should not be too hard to separate out a defect fix from the work
> of QPID-7567.   I will look to include this in a 7.0.3 which should
> not be too far away.
> 
> Kind regards, Keith.
> 
> On 15 March 2018 at 17:06, Rob Godfrey 

> rob.j.godfrey@

>  wrote:
>> Hi Tomas,
>>
>> there is/was a bug in the broker whereby it would always pick the first
>> certificate rather than the one with the correct alias.  I fixed the bug
>> as
>> part of QPID-7567[1] last year, however I think that is only on master
>> (and
>> scheduled for 7.1) and hasn't been backported to 7.0.x.
>>
>> -- Rob
>>
>> [1] https://issues.apache.org/jira/browse/QPID-7567
>>
>> On 15 March 2018 at 15:03, Vavricka 

> vavricka.tomas@

>  wrote:
>>
>>> Hi,
>>>
>>> *I generate multiple self-signed certificates by:*
>>>
>>> keytool -genkeypair -alias pc18379_1 -dname CN=pc18379 -validity 1096
>>> -keysize 2048 -keyalg RSA -sigalg SHA512withRSA -keypass '123456'
>>> -storepass
>>> 123456 -deststoretype PKCS12 -keystore pc18379_1.jks
>>> keytool -genkeypair -alias pc18379_2 -dname CN=pc18379 -validity 1096
>>> -keysize 2048 -keyalg RSA -sigalg SHA512withRSA -keypass '123456'
>>> -storepass
>>> 123456 -deststoretype PKCS12 -keystore pc18379_2.jks
>>> keytool -genkeypair -alias pc18379_3 -dname CN=pc18379 -validity 1096
>>> -keysize 2048 -keyalg RSA -sigalg SHA512withRSA -keypass '123456'
>>> -storepass
>>> 123456 -deststoretype PKCS12 -keystore pc18379_3.jks
>>>
>>> Each generated keypair has own keystore.
>>>
>>> *I export private keys to keystore which broker will use by:*
>>>
>>> keytool -importkeystore -srckeystore pc18379_1.jks -srcstoretype PKCS12
>>> -storepass '123456' -srcstorepass '123456' -alias pc18379_1
>>> -deststoretype
>>> PKCS12 -destkeystore keystore
>>> keytool -importkeystore -srckeystore pc18379_2.jks -srcstoretype PKCS12
>>> -storepass '123456' -srcstorepass '123456' -alias pc18379_2
>>> -deststoretype
>>> PKCS12 -destkeystore keystore
>>> keytool -importkeystore -srckeystore pc18379_3.jks -srcstoretype PKCS12
>>> -storepass '123456' -srcstorepass '123456' -alias pc18379_3
>>> -deststoretype
>>> PKCS12 -destkeystore keystore
>>>
>>> *I export public certificates by:*
>>>
>>> keytool -exportcert -keystore pc18379_1.jks -storepass '123456' -alias
>>> pc18379_1 -rfc -file pc18379_1.crt
>>> keytool -exportcert -keystore pc18379_2.jks -storepass '123456' -alias
>>> pc18379_2 -rfc -file pc18379_2.crt
>>> keytool -exportcert -keystore pc18379_3.jks -storepass '123456' -alias
>>> pc18379_3 -rfc -file pc18379_3.crt
>>>
>>> *I create truststores for clients by:*
>>>
>>> keytool -import -alias pc18379_1 -file pc18379_1.crt -storepass '123456'
>>> -noprompt -deststoretype PKCS12 -keystore pc18379_1.truststore
>>> keytool -import -alias pc18379_2 -file pc18379_2.crt -storepass '123456'
>>> -noprompt -deststoretype PKCS12 -keystore pc18379_2.truststore
>>> keytool -import -alias pc18379_3 -file pc18379_3.crt -storepass '123456'
>>> -noprompt -deststoretype PKCS12 -keystore pc18379_3.truststore
>>>
>>> *List of certificates in "keystore" (keystore broker will use)*
>>>
>>> Enter keystore password:
>>> Keystore type: JKS
>>> Keystore provider: SUN
>>>
>>> Your keystore contains 3 entries
>>>
>>> Alias name: pc18379_1
>>> Creation date: Mar 15, 2018
>>> Entry type: PrivateKeyEntry
>>> Certificate chain length: 1
>>> Certificate[1]:
>>> Owner: CN=pc18379
>>> Issuer: CN=pc18379
>>> Serial number: 54f1c168
>>> Valid from: Thu Mar 15 14:05:07 CET 2018 until: Mon Mar 15 14:05:07 CET
>>> 2021
>>> Certificate fingerprints:
>>>  MD5:  60:6C:94:B6:5D:18:C3:AC:89:56:3F:A9:A2:70:83:37
>>>  SHA1:
>>> 0D:D4:14:24:E6:92:35:B7:5B:A3:71:A7:BF:45:B3:6C:37:65:7F:4E
>>>  SHA256:
>>> 79:F0:77:65:27:93:5C:D0:55:73:42:B6:2D:4E:75:94:9A:64:6A:35:
>>> 7C:12:4F:B0:CD:82:D7:89:96:8F:88:59
>>> Signature algorithm name: SHA512withRSA
>>> Subject Public Key Algorithm: 2048-bit RSA key
>>> Version: 3
>>>
>>> Extensions:
>>>
>>> #1: ObjectId: 2.5.29.14 C

[Java Broker] Select certificate from broker keystore

[Vavricka]

Hi,

*I generate multiple self-signed certificates by:*

keytool -genkeypair -alias pc18379_1 -dname CN=pc18379 -validity 1096
-keysize 2048 -keyalg RSA -sigalg SHA512withRSA -keypass '123456' -storepass
123456 -deststoretype PKCS12 -keystore pc18379_1.jks
keytool -genkeypair -alias pc18379_2 -dname CN=pc18379 -validity 1096
-keysize 2048 -keyalg RSA -sigalg SHA512withRSA -keypass '123456' -storepass
123456 -deststoretype PKCS12 -keystore pc18379_2.jks
keytool -genkeypair -alias pc18379_3 -dname CN=pc18379 -validity 1096
-keysize 2048 -keyalg RSA -sigalg SHA512withRSA -keypass '123456' -storepass
123456 -deststoretype PKCS12 -keystore pc18379_3.jks

Each generated keypair has own keystore.

*I export private keys to keystore which broker will use by:*

keytool -importkeystore -srckeystore pc18379_1.jks -srcstoretype PKCS12
-storepass '123456' -srcstorepass '123456' -alias pc18379_1 -deststoretype
PKCS12 -destkeystore keystore
keytool -importkeystore -srckeystore pc18379_2.jks -srcstoretype PKCS12
-storepass '123456' -srcstorepass '123456' -alias pc18379_2 -deststoretype
PKCS12 -destkeystore keystore
keytool -importkeystore -srckeystore pc18379_3.jks -srcstoretype PKCS12
-storepass '123456' -srcstorepass '123456' -alias pc18379_3 -deststoretype
PKCS12 -destkeystore keystore

*I export public certificates by:*

keytool -exportcert -keystore pc18379_1.jks -storepass '123456' -alias
pc18379_1 -rfc -file pc18379_1.crt
keytool -exportcert -keystore pc18379_2.jks -storepass '123456' -alias
pc18379_2 -rfc -file pc18379_2.crt
keytool -exportcert -keystore pc18379_3.jks -storepass '123456' -alias
pc18379_3 -rfc -file pc18379_3.crt

*I create truststores for clients by:*

keytool -import -alias pc18379_1 -file pc18379_1.crt -storepass '123456'
-noprompt -deststoretype PKCS12 -keystore pc18379_1.truststore
keytool -import -alias pc18379_2 -file pc18379_2.crt -storepass '123456'
-noprompt -deststoretype PKCS12 -keystore pc18379_2.truststore
keytool -import -alias pc18379_3 -file pc18379_3.crt -storepass '123456'
-noprompt -deststoretype PKCS12 -keystore pc18379_3.truststore

*List of certificates in "keystore" (keystore broker will use)*

Enter keystore password:  
Keystore type: JKS
Keystore provider: SUN

Your keystore contains 3 entries

Alias name: pc18379_1
Creation date: Mar 15, 2018
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=pc18379
Issuer: CN=pc18379
Serial number: 54f1c168
Valid from: Thu Mar 15 14:05:07 CET 2018 until: Mon Mar 15 14:05:07 CET 2021
Certificate fingerprints:
 MD5:  60:6C:94:B6:5D:18:C3:AC:89:56:3F:A9:A2:70:83:37
 SHA1: 0D:D4:14:24:E6:92:35:B7:5B:A3:71:A7:BF:45:B3:6C:37:65:7F:4E
 SHA256:
79:F0:77:65:27:93:5C:D0:55:73:42:B6:2D:4E:75:94:9A:64:6A:35:7C:12:4F:B0:CD:82:D7:89:96:8F:88:59
Signature algorithm name: SHA512withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Extensions: 

#1: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
: 87 A5 26 94 CC 30 E8 63   66 61 87 1A 83 29 E7 63  ..&..0.cfa...).c
0010: EE 16 2D B6..-.
]
]



***
***


Alias name: pc18379_2
Creation date: Mar 15, 2018
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=pc18379
Issuer: CN=pc18379
Serial number: 23e58c32
Valid from: Thu Mar 15 14:06:38 CET 2018 until: Mon Mar 15 14:06:38 CET 2021
Certificate fingerprints:
 MD5:  15:71:70:31:43:11:D9:15:3B:5B:E7:F0:DD:AB:96:DB
 SHA1: D6:37:E3:4B:75:C7:9E:4B:D2:92:5C:50:92:DB:71:17:BE:58:FC:2F
 SHA256:
52:88:88:AA:AE:C3:68:88:02:4D:CA:4E:32:76:DF:98:09:B9:03:9A:AB:3E:C1:CF:69:6C:B2:B2:97:D8:87:ED
Signature algorithm name: SHA512withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Extensions: 

#1: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
: 97 0A 71 24 FA C9 EB 52   72 D8 30 AC 46 FA 87 02  ..q$...Rr.0.F...
0010: 28 63 A8 D8(c..
]
]



***
***


Alias name: pc18379_3
Creation date: Mar 15, 2018
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=pc18379
Issuer: CN=pc18379
Serial number: 4c6d4854
Valid from: Thu Mar 15 14:06:44 CET 2018 until: Mon Mar 15 14:06:44 CET 2021
Certificate fingerprints:
 MD5:  CC:FD:D2:DA:38:A1:0F:3E:B1:6D:A3:62:65:D0:E3:82
 SHA1: EE:37:84:C3:8E:B1:42:06:32:07:A4:CF:F0:EA:39:E7:3D:9F:3B:4F
 SHA256:
18:D4:41:2D:40:F1:19:35:68:6A:90:A3:2D:8A:64:4D:AC:1E:30:DF:48:C9:13:F1:92:EF:A2:02:8B:B9:D3:B7
Signature algorithm name: SHA512withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Extensions: 

#1: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
: CE 2A EE 5D B0 4A DE AA   47 97 A1 B2 70 14 9A 0A  

Re: Java Broker performance

[Vavricka]

It is ok for us to release 7.0.0 and implement this issue in 7.0.1.

Vast majority of our applications need this functionality.

Tomas


Keith Wall wrote
> The test is sending persistent messages so the broker is obliged to
> write them to disk.  After the arrival of each message transfer, the
> Broker-J awaits the sync'd to disk (after the write) before sending
> the Disposition performative back to the client.  The Qpid JMS Client
> is awaiting the Disposition, so it is only then that the
> MessageProducer#send returns and the application can send the next
> message.   I infer that CPP Broker must be optimistically sending the
> Disposition back to the client before the data is sync'd, so that is
> why you see better performance (but with a lesser guarantee).   If you
> were to switch the Qpid JMS Client to jms.forceAsyncSend[1], I would
> expect you would see greater performance.   Let me ask a higher level
> question - what messaging guarantee does this application require?
> 
> [1] https://qpid.apache.org/releases/qpid-jms-0.27.0/docs/index.html
> 
> On 10 November 2017 at 15:50, Rob Godfrey 

> rob.j.godfrey@

>  wrote:
>> On 10 November 2017 at 16:39, Vavricka 

> vavricka.tomas@

>  wrote:
>>
>>> Hi,
>>>
>>> hardware:
>>> * Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
>>> * 16 GB RAM
>>> * HDD ST500DM002-1BD142
>>>
>>> timings:
>>> Currently Java Broker 6.1.1 seems to behave as version 7.0.0 RC. 10 - 30
>>> messages per second. Interesting is when I increase message size to
>>> 10kB.
>>> Messages per second are same but throughput is increased ten times.
>>> When I use nonpersistent messages everything goes smooth. Thousand of
>>> 1kB
>>> messages are sent within 1 second.
>>>
>>
>> So, this is more what I would expect (in the sense that 6.1 will behave
>> like 7.0 - the performance is unacceptable, but I think I understand it).
>>
>> I *think* the issue is that we have not yet implemented the optimisations
>> in the 1.0 layer for non-transactional durable messages to be processed
>> asynchronously.  Because of this the rate of message processing is
>> dependent upon how many times fsync() can be called a second.  500/s is
>> probably about right for a SAN, ~20 is what I saw from conventional hard
>> drives; for SSDs with a battery backed write cache I've gotten > 1000/s.
>> Because it is dependent upon the number of fsyncs rather than the
>> throughput of the disk, increasing the message size will not affect the
>> rate and thus you will see a linear improvement in throughput.
>>
>> Fixing this shouldn't actually be a huge change, and after it you should
>> see something more like the C++ broker behaviour.  Since this isn't (I
>> think) a regression between 7.0 and 6.1 I'd suggest that we progress with
>> the 7.0 release and then quickly follow that with a 7.0.1 that introduces
>> the necessary optimisation (we can essentially copy over the code from
>> the
>> 0-x protocol layers).
>>
>> -- Rob
>>
>>
>>>
>>> There are no extra JVM options, just the ones which are present in
>>> bin/qpid-server file.
>>>
>>> Heap and direct memory on broker is also default - -Xmx512m
>>> -XX:MaxDirectMemorySize=1536m. I tried to increase to four times larger
>>> ones
>>> -Xmx2048m -XX:MaxDirectMemorySize=6000m, but there was no change in
>>> messages
>>> per second.
>>>
>>> Unfortunately vmstat gives same values pro CPU, I am sending at least
>>> top
>>> output.
>>>
>>> 6.1.1:
>>> %Cpu(s):  6.9 us,  0.3 sy,  0.0 ni, 68.5 id, 24.1 wa,  0.0 hi,  0.2 si,
>>> 0.0
>>> st
>>>
>>> 7.0.0:
>>> %Cpu(s):  2.4 us,  0.4 sy,  0.0 ni, 71.2 id, 25.9 wa,  0.0 hi,  0.0 si,
>>> 0.0
>>> st
>>>
>>> When we tried on server where message store was stored on SAN disk,
>>> sending
>>> of messages increased to 500 msg/sec. With C++ broker on same machine we
>>> are
>>> able to send 5000 msg/sec.
>>>
>>> ps. I cannot create queue in 7.0.0 version by webgui when queue contains
>>> '.'
>>> character, in 6.1.1 version queue with dot in name can be created by
>>> webgui
>>>
>>>
>>> Keith Wall wrote
>>> > Hi Tomas,
>>> >
>>> > Nor can I reproduce any discernible difference in performance between
>>> > 6.1.1 and the 7.0.0 RC with your Java code.  I have not tried the C+

Re: Java Broker performance

[Vavricka]

Hi,

hardware:
* Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
* 16 GB RAM
* HDD ST500DM002-1BD142

timings:
Currently Java Broker 6.1.1 seems to behave as version 7.0.0 RC. 10 - 30
messages per second. Interesting is when I increase message size to 10kB.
Messages per second are same but throughput is increased ten times.
When I use nonpersistent messages everything goes smooth. Thousand of 1kB
messages are sent within 1 second.

There are no extra JVM options, just the ones which are present in
bin/qpid-server file.

Heap and direct memory on broker is also default - -Xmx512m
-XX:MaxDirectMemorySize=1536m. I tried to increase to four times larger ones
-Xmx2048m -XX:MaxDirectMemorySize=6000m, but there was no change in messages
per second.

Unfortunately vmstat gives same values pro CPU, I am sending at least top
output.

6.1.1:
%Cpu(s):  6.9 us,  0.3 sy,  0.0 ni, 68.5 id, 24.1 wa,  0.0 hi,  0.2 si,  0.0
st

7.0.0:
%Cpu(s):  2.4 us,  0.4 sy,  0.0 ni, 71.2 id, 25.9 wa,  0.0 hi,  0.0 si,  0.0
st

When we tried on server where message store was stored on SAN disk, sending
of messages increased to 500 msg/sec. With C++ broker on same machine we are
able to send 5000 msg/sec.

ps. I cannot create queue in 7.0.0 version by webgui when queue contains '.'
character, in 6.1.1 version queue with dot in name can be created by webgui


Keith Wall wrote
> Hi Tomas,
> 
> Nor can I reproduce any discernible difference in performance between
> 6.1.1 and the 7.0.0 RC with your Java code.  I have not tried the C++
> yet.
> 
> Can you share with us:
> 
> * details of the hardware (including the storage) you are using for the
> test.
> * the timings you seeing for your tests for both the 6.1.1 case and 7.0.0
> RC
> * any extra JVM options you are passing either client or broker side.
> * size of java heap (client side) and heap and direct memory (broker)
> 
> Can I suggest that you collect vmstat type information for both runs
> and compare?   My expectation is that CPU usage, disk I/O, and network
> utilisation should be approximately equal between the two runs.
> 
> cheers, Keith





--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: Java Broker performance

[Vavricka]

Yes, we running it on same hardware and versions.

Couldn't be there issue with our configuration? Can you spot there some
misconfiguration in config files below?

Will be helpful if you send us your broker configuration?

config.json

{
  "id" : "cfa9a57a-6f98-4f17-b81d-22fb5a032473",
  "name" : "cps",
  "modelVersion" : "7.0",
  "accesscontrolproviders" : [ {
"id" : "65b550b1-0a22-4815-9b6f-5287f6a9b455",
"name" : "brokerAcl",
"type" : "AclFile",
"path" : "/home/vavrtom/qpid/0406/broker/work/broker.acl",
"lastUpdatedBy" : null,
"lastUpdatedTime" : null,
"createdBy" : null,
"createdTime" : null
  } ],
  "authenticationproviders" : [ {
"id" : "df3680b4-8bd7-4bb8-92b7-705d33bf1496",
"name" : "SHA_256",
"type" : "SCRAM-SHA-256",
"secureOnlyMechanisms" : [ ],
"users" : [ {
  "id" : "e98445dd-4f79-46b1-bc7f-a153f546e63e",
  "name" : "C7",
  "type" : "managed",
  "durable" : true,
  "password" :
"KAkXZolpJXtHteNgxqeNaosC3eecIN0MRZVdFcAwGm4=,,U52qJCBi8jUfjPTHMxayTwUhQ3UT+N6B7h78S+kRNUw=,fQdDP2WsuAGZ/P4PxJuSAHrpmgE/2GBMjD9/TrYw0QY=,4096",
  "lastUpdatedBy" : "admin",
  "lastUpdatedTime" : 1510235279421,
  "createdBy" : "admin",
  "createdTime" : 1510235279421
}, {
  "id" : "62ab34ac-11d8-4ed0-adc3-bd1c34a2f7af",
  "name" : "admin",
  "type" : "managed",
  "password" :
"7uKre2FrpVvO+/gABKrTHyQS5tAY92UqOWNcWPCubyw=,,j3TzWP+Bg2iZUXxMdZbVi1ftrHIvzev5PqO9ftDC4hU=,9cvIWGYPfeUD0hFLvINPKz+Ddvv/9/yz8PuMC+JR3Ro=,4096"
}, {
  "id" : "e6451384-9ef5-4823-81c6-7b1aff7251ca",
  "name" : "monit",
  "type" : "managed",
  "password" :
"b3MiUviPyxYSfB9bxRZG4FJ/uxDWjWnNvBe1B/w8JYc=,,gxUMuoFhW9oVNV/tEiLm3IdgObL2uQagi63G+3bnFgs=,cQmi/8NKL2b8ESfoF/wcffPRILoMOx5cRy+rEG2TAxw=,4096"
} ]
  }, {
"id" : "85d7cb16-4c60-45ca-94e8-47c611a7b1e4",
"name" : "external",
"type" : "External"
  } ],
  "brokerloggers" : [ {
"id" : "e637b21b-c3a8-457f-a0ff-c4327c88135b",
"name" : "logfile",
"type" : "File",
"fileName" :
"${qpid.work_dir}${file.separator}..${file.separator}..${file.separator}log${file.separator}broker.log",
"brokerloginclusionrules" : [ {
  "id" : "f8e8c9eb-6ca9-4845-8ac8-1ba614a47ce8",
  "name" : "Operational",
  "type" : "NameAndLevel",
  "level" : "INFO",
  "loggerName" : "qpid.message.*"
}, {
  "id" : "13c4e2c4-3b3a-43be-890b-cc506dae63f8",
  "name" : "Qpid",
  "type" : "NameAndLevel",
  "level" : "INFO",
  "loggerName" : "org.apache.qpid.*"
}, {
  "id" : "00ff6321-2d42-4dce-aad0-12c55c928e0d",
  "name" : "Root",
  "type" : "NameAndLevel",
  "level" : "INFO",
  "loggerName" : "ROOT"
} ]
  }, {
"id" : "b25480a7-5ed1-4035-af9d-565c9c223708",
"name" : "memory",
"type" : "Memory",
"brokerloginclusionrules" : [ {
  "id" : "ffc9a1da-e812-476c-8ccf-c8ead2f15e1e",
  "name" : "Operational",
  "type" : "NameAndLevel",
  "level" : "INFO",
  "loggerName" : "qpid.message.*"
}, {
  "id" : "8c2a2fe6-9531-469b-8f26-c5d449e97f26",
  "name" : "Qpid",
  "type" : "NameAndLevel",
  "level" : "INFO",
  "loggerName" : "org.apache.qpid.*"
}, {
  "id" : "dcb193af-fba8-49e7-9ed4-9a4a08627e8c",
  "name" : "Root",
  "type" : "NameAndLevel",
  "level" : "INFO",
  "loggerName" : "ROOT"
} ]
  } ],
  "keystores" : [ {
"id" : "f262fc1c-081b-4215-8afb-bb0ce6131857",
"name" : "keyStore",
"type" : "FileKeyStore",
"certificateAlias" : "vavrtom-amqp",
"password" : "admin",
"storeUrl" : "/home/vavrtom/qpid/0406/broker/work/keystore.jks"
  } ],
  "plugins" : [ {
"id" : "1276ff6c-61ea-4b4d-b1ad-4edc5c02f581",
"name" : "httpManagement",
"type" : "MANAGEMENT-HTTP",
"httpBasicAuthenticationEnabled" : "true"
  } ],
  "ports" : [ {
"id" : "6fdbb8b1-76ba-4048-9ca8-4e7dfb884a38",
"name" : "amqp",
"type" : "AMQP",
"port" : 20406,
"protocols" : [ "AMQP_1_0" ],
"authenticationProvider" : "SHA_256",
"threadPoolSize" : 10,
"numberOfSelectors" : 1,
"maxOpenConnections" : 1000,
"virtualhostaliases" : [ {
  "id" : "59d083e1-57f2-45c0-b8d4-c75f23ea33ef",
  "name" : "defaultAlias",
  "type" : "defaultAlias"
}, {
  "id" : "1c61ebd0-fbc6-4891-998b-59b972492fc7",
  "name" : "hostnameAlias",
  "type" : "hostnameAlias"
}, {
  "id" : "d75851d6-ea9c-4aec-a8db-7e28d5815b5e",
  "name" : "nameAlias",
  "type" : "nameAlias"
} ]
  }, {
"id" : "f52c4129-d388-4f3a-b23f-892070a131dd",
"name" : "amqps",
"type" : "AMQP",
"port" : 10406,
"protocols" : [ "AMQP_1_0" ],
"authenticationProvider" : "external",
"needClientAuth" : true,
"wantClientAuth" : true,
"keyStore" : "keyStore",
"transports" : [ "SSL" ],
"trustStores" : [ "trustStore" ],
"threadPoolSize" : 10,
"numberOfSelectors" : 1,
"maxOpenConnections" : 

Re: Java Broker performance

[Vavricka]

C++ client code below

#include 
#include 

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

class Broadcaster : public proton::messaging_handler
{

private:

std::string _account;
std::string _password;
std::string _host;
unsigned int _port;
unsigned int _count;
unsigned int _size;
unsigned int _sent;
unsigned int _confirmed;
std::string _exchange;
std::string _routingKey;
proton::sender _sender;

public:

explicit Broadcaster(const std::string ,
 const std::string ,
 const std::string ,
 unsigned int port,
 const std::string ,
 const std::string ,
 unsigned int count,
 unsigned int size)
: _account(account)
, _password(password)
, _host(host)
, _port(port)
, _count(count)
, _size(size)
, _sent(0)
, _confirmed(0)
, _exchange(exchange)
, _routingKey(routingKey)
{
}

void on_container_start(proton::container )
{
proton::connection_options connectionOptions;
connectionOptions.sasl_allow_insecure_mechs(true);
connectionOptions.sasl_allowed_mechs("PLAIN");
c.client_connection_options(connectionOptions);

std::string url = "amqp://" + _account + ":" + _password + "@" +
_host + ":" + std::to_string(_port) + "/" + _exchange;

_sender = c.open_sender(url);
}

void on_sendable(proton::sender )
{
while (s.credit() && _sent < _count)
{
proton::message msg;
msg.id(_sent + 1);
msg.subject(_routingKey);
msg.body(std::string(_size, '*'));
msg.durable(true);
s.send(msg);
_sent++;
std::cout << "-I sent " << _sent << " of " << _count <<
std::endl;
}
}

void on_tracker_accept(proton::tracker )
{
_confirmed++;
if (_confirmed == _count)
{
std::cout << "-I- All messages (" << _confirmed << ") confirmed"
<< std::endl;
t.connection().close();
}
}

void on_transport_close(proton::transport )
{
_sent = _confirmed;
}

void run()
{
try
{
proton::default_container(*this).run();
}
catch (const std::exception )
{
std::cerr << "-E- Caught exception: " << error.what() <<
std::endl;
throw error;
}
}
};

int main(void)
{
Broadcaster("C7",
"C7",
"pc1wj611",
20001,
"broadcast",
"broadcast.C7_CashTransaction",
1000,
1024).run();
return 0;
}




--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: Java Broker performance

[Vavricka]

Hi, 

when consumer is not attached sending of messages is slow too. We were
running performance tests for Java Broker 6.1.1 before 6 months and there
were no issues (throughput for 1K messages was around 10MB/s).


rgodfrey wrote
> Hi Tomas, 
> 
> are you saying that there is a significant degradation in performance 
> between 7.0.0 and prior versions for this scenario, or do you see the same 
> performance in 6.1.x? 
> 
> In terms of consuming - is the performance slow if you are consuming from
> a 
> queue with 1000 messages already in it, or is the slowness just caused by 
> the slow producer? 
> 
> Thanks, 
> Rob

Code below is for JMS client 0.27.0 (without catching exceptions) which
behaves similarly as client based on proton 0.18.1.

Properties properties = new Properties();
properties.setProperty(Context.INITIAL_CONTEXT_FACTORY,
"org.apache.qpid.jms.jndi.JmsInitialContextFactory");
properties.setProperty("connectionfactory.connection",
"amqp://localhost:20406?jms.username=C7=C7");
properties.setProperty("topic.broadcastAddress", "broadcast");
InitialContext context = new InitialContext(properties);

Connection connection = ((ConnectionFactory)
context.lookup("connection")).createConnection();
Session session = connection.createSession(false,
Session.CLIENT_ACKNOWLEDGE);
MessageProducer broadcastProducer = session.createProducer((Destination)
context.lookup("broadcastAddress"));
connection.start();
char[] chars = new char[1024];
Arrays.fill(chars, 'f');
TextMessage message = session.createTextMessage(new String(chars));
message.setJMSDeliveryMode(DeliveryMode.PERSISTENT);
message.setJMSType("broadcast.C7_CashTransaction");
System.out.println(Instant.now());
int messageCount = 1000;
for (int i = 1 ; i <= messageCount ; i++)
{
broadcastProducer.send(message, DeliveryMode.PERSISTENT,
Message.DEFAULT_PRIORITY, Message.DEFAULT_TIME_TO_LIVE);
if (i % 100 == 0)
{
System.out.println(Instant.now() + " sent " + i + " messages");
}
}
System.out.println(Instant.now());

Output of client is below

[main] INFO com.deutscheboerse.amqp_1_0.examples.BroadcastSender - Creating
connection
[AmqpProvider :(1):[amqp://localhost:20406]] INFO
org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was:
SASL-SCRAM-SHA-256
[AmqpProvider :(1):[amqp://localhost:20406]] INFO
org.apache.qpid.jms.JmsConnection - Connection
ID:0333e24e-c00a-4dd7-91af-57fd1366512c:1 connected to remote Broker:
amqp://localhost:20406
2017-11-10T08:46:31.135Z
2017-11-10T08:46:41.770Z sent 100 messages
2017-11-10T08:46:52.449Z sent 200 messages
2017-11-10T08:47:03.958Z sent 300 messages
2017-11-10T08:47:15.174Z sent 400 messages
2017-11-10T08:47:25.514Z sent 500 messages
2017-11-10T08:47:36.045Z sent 600 messages
2017-11-10T08:47:46.432Z sent 700 messages
2017-11-10T08:47:57.797Z sent 800 messages
2017-11-10T08:48:09.434Z sent 900 messages
2017-11-10T08:48:20.419Z sent 1000 messages
2017-11-10T08:48:20.419Z


Keith Wall wrote
> Hi Tomas,
> 
> That does sound surprising.  These performance tests[1] are run, with
> BDB and using the latest Qpid JMS Client,  against both the Broker-J
> 7.0.0 and 6.1.4 code lines each day, which is consistently showing
> v7.0.0 is faster for the five use-cases exercised by the tests (see
> perftests/etc/testdefs/defaultTests.js).  I am interested to hear
> about your use-case.   Do you have code you can share?
> 
> cheers, Keith.





--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Java Broker performance

[Vavricka]

Hi, 

we are testing release candidate of Java Broker 7.0.0.

I checkout tag 7.0.0, build broker with tests without any problem.

We have sender and receiver based on proton 0.18.1.
Both sender and receiver are started at same time.
Sender is sending 1000 persistent messages to exchange and receiver expects
1000 messages in queue. Messages have size 1 kB.
We tried DERBY and BDB as persistent storage.

Sending and consuming of durable messages is slow (10 messages per second).
When sending non-persistent messages then broker behaves as expected.

Is there some settings that can optimize persistent storage?

Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [Java Broker] Usage of any certificate from keystore

[Vavricka]

rgodfrey wrote
> On 27 October 2017 at 10:43, Vavricka 

> vavricka.tomas@

>  wrote:
> 
> In the period 28.10.2017 10:00 - 30.10.2017 10:00; both certificates are
> valid... the broker can't really know which is "preferred" by the client,
> I
> would think that we should always go with the one with the most distant
> expiry simply to avoid issues where we are getting very close to the
> expiry
> time of the older certificate (i.e. if we are within a minute, then you
> run
> the risk of clock drift between the client and server causing the served
> certificate to appear invalid.  Is this your expectation too?
> 
> -- Rob

I misunderstood how SSL handshake works. Because server offers certificate
first, server can't know what certificate client have. 

Case 2. is now irrelevant and I expect same Java broker behavior as today.

Thanks for explanation.

Vavricka



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [Java Broker] Usage of any certificate from keystore

[Vavricka]

I can imagine these situations where it can be helpful.

1. 

* There is active/passive cluster (provides a fully redundant instance of
each node, which is only brought online when its associated primary node
fails) environment where Java broker is running on node1
* Shared drive is used for keystore and truststore
* In keystore there are certificates for each node
   * node1 - CN=hostname1, alias hostname1
   * node2 - CN=hostname2, alias hostname2
   ...
* Unless "transport.verifyHost=false" is specified in connection string,
clients can connect only with correct certificates for each node
* When cluster node is relocated to node2, Java broker starts on node2 and
loads keystore from shared drive
* If client cannot connect with certificate for node1, he can try node2 and
if Java broker is running on node2, he can successfully connect to broker

2. 

* Certificate with "CN=hostname" and alias "hostname" is valid from
30.10.2014 10:00 to 30.10.2017 10:00
* At 26.10.2017 certificate with "CN=hostname" and alias "hostname_2" with
validity from 28.10.2017 10:00 to 28.10.2020 is added to server keystore and
sent to client
* Client can use both certificates in transitional period 28.10.2017 10:00 -
30.10.2017 10:00. Because there is transitional period client can prepare
new certificate in his software
* In maintenance batch at 30.10.2017 24:00 is expired certificate removed
and only new certificate is present in keystore





--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [Qpid JMS client] Characters ',' and '=' in password

[Vavricka]

Yes type of authentication provider is SCRAM-SHA-256.

And I can confirm that when PLAIN sasl mechanism is used, password with ','
and '=' characters can be used.

Thanks for quick replies.

Vavricka



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

[Qpid JMS client] Characters ',' and '=' in password

[Vavricka]

Hi, 

 it looks like there are two characters which cannot be used in password.
These characters are comma and equals.

  Qpid JMS Client - 0.25.0 
  Qpid Java Broker - 7.0.0

 Connection string
amqp://host:port?jms.username=user=encodedPassword

 I am encoding password by URLEncoder.encode(password,
StandardCharsets.UTF_8.name()).

 Are these characters unsupported?

  Vavricka



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: [Qpid JMS Client] Password with '+' character

[Vavricka]

Hi,

  when I used URLEncoder.encode(pass, "UTF-8") as used in mentioned test,
client successfully connected.

  Thanks for reply.

  Tomas



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

[Qpid JMS Client] Password with '+' character

[Vavricka]

Hi,

  I am facing an issue when connecting to Qpid C++ broker with Qpid JMS
client (AMQP 1.0) when jms.password property in connection string contains
'+' character.

  Qpid JMS Client - 0.24.0
  Qpid C++ broker - 0.34

 Connection strings I tried:

  amqp://host:port?jms.username=admin=passwith+char

  amqp://host:port?jms.username=admin='passwith+char'

  amqp://host:port?jms.username=admin="passwith+char"

  amqp://host:port?jms.username=admin=passwith%2Bchar

  amqp://host:port?jms.username=admin='passwith%2Bchar'

  Client always failed to connect. Is it possible to have '+' character in
jms.password property?

  Vavricka



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

[Qpid JMS client] Asynchronous send JMS 2.0

[Vavricka]

Hi, 

  qpid jms client version - 0.23.0
  qpid c++ broker version - 0.34

  I am unable to send messages asynchronously using the JMS 2.0 API.

  Connection string is same for JMS 1.1 and JMS 2.0 -
"amqp://host:20405?jms.username=admin=admin=true=true=true"

  When I use JMS 1.1 API, it works ok.

*Code for JMS 1.1 below.*

try
{
Topic queue = (Topic) initialContext.lookup("node");
Connection connection = ((ConnectionFactory)
initialContext.lookup("connection")).createConnection();
Session session = connection.createSession(false,
Session.CLIENT_ACKNOWLEDGE);
MessageProducer producer = session.createProducer(queue);
connection.start();
for (int i = 0; i < 500; i++)
{
producer.send(session.createTextMessage("test"));
}
}
catch
...

 However when I use JMS 2.0 API, sending is extremely slow (1 message per
second). 

*Code for JMS 2.0 API below.*

try (JMSContext context =
connectionFactory.createContext(JMSContext.CLIENT_ACKNOWLEDGE))
{
JMSProducer producer = context.createProducer();
producer.setAsync(new SendCompletitionListener());
for (int i = 0; i < senderOptionParser.getMessageCountValue(); i++)
{
producer.send(queue, context.createTextMessage("test"));
}
}
catch
...

*Part of trace output of JMS 1.1 during one message sent:*

{Output before producer.send(session.createTextMessage("test"));}
...
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.AmqpFixedProducer - Producer sending
message: JmsOutboundMessageDispatch {dispatchId =
ID:dfbce852-0cdc-4669-99df-e9d59569b0f6:1:1:1-1, MessageID =
ID:dfbce852-0cdc-4669-99df-e9d59569b0f6:1:1:1-1 }
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.FRAMES - SENT: Transfer{handle=0,
deliveryId=0, deliveryTag=0, messageFormat=0, settled=null, more=false,
rcvSettleMode=null, state=null, resume=false, aborted=false,
batchable=false}
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.transports.netty.NettyTcpTransport - Attempted write of:
2283 bytes
...
{Output after producer.send(session.createTextMessage("test"));}

*Part of trace output of JMS 2.0 during one message sent:*

{Output before producer.send(queue, context.createTextMessage("test"));}
...
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.FRAMES - SENT:
Attach{name='qpid-jms:sender:ID:8261d327-2100-47a1-8860-69bc1d0fd6ae:1:-1:1:broadcast',
handle=0, role=SENDER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='ID:8261d327-2100-47a1-8860-69bc1d0fd6ae:1:-1:1',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=null},
target=Target{address='broadcast', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=[topic]},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
maxMessageSize=null, offeredCapabilities=null,
desiredCapabilities=[DELAYED_DELIVERY], properties=null}
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.transports.netty.NettyTcpTransport - Attempted write of:
324 bytes
[epollEventLoopGroup-2-1] TRACE
org.apache.qpid.jms.transports.netty.NettyTcpTransport - New data read: 212
bytes incoming: PooledUnsafeDirectByteBuf(ridx: 0, widx: 212, cap: 65536)
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.FRAMES - RECV:
Attach{name='qpid-jms:sender:ID:8261d327-2100-47a1-8860-69bc1d0fd6ae:1:-1:1:broadcast',
handle=0, role=RECEIVER, sndSettleMode=MIXED, rcvSettleMode=FIRST,
source=Source{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, distributionMode=null,
filter=null, defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='broadcast', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=[topic]},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.FRAMES - RECV: Flow{nextIncomingId=2,
incomingWindow=2147483647, nextOutgoingId=0, outgoingWindow=2147483647,
handle=0, deliveryCount=0, linkCredit=500, available=null, drain=false,
echo=false, properties=null}
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.AmqpProvider - New Proton Event: LINK_INIT
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.AmqpProvider - New Proton Event:
LINK_LOCAL_OPEN
[AmqpProvider:(1):[amqp://host:20405]] TRACE
org.apache.qpid.jms.provider.amqp.AmqpProvider - New Proton Event:
LINK_REMOTE_OPEN
[AmqpProvider:(1):[amqp://host:20405]] TRACE

Re: [Java Broker] Invalid routing key

[Vavricka]

Hi, 

 JIRA issue created  https://issues.apache.org/jira/browse/QPID-7857
<https://issues.apache.org/jira/browse/QPID-7857>  .

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Java-Broker-Invalid-routing-key-tp7664724p7664731.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

[Java Broker] Invalid routing key

[Vavricka]

Hi, 

 I have a issue with sending message with routing key to Java broker. Java
Broker always denies access.

 Java Broker version is latest trunk. Client version is 0.11.1.

related ACL:

ACL ALLOW-LOG FIXGW ACCESS VIRTUALHOST
ACL ALLOW-LOG FIXGW PUBLISH EXCHANGE name="request.FIXGW"
routingKey="TradeReport*"

Client code:

TextMessage message = session.createTextMessage("...");
message.setJMSCorrelationID(UUID.randomUUID().toString());
message.setJMSType("TradeReport");

Java Broker log:

...
2017-07-11 15:55:31,003 DEBUG [IO-/172.23.38.39:40030]
(o.a.q.s.s.a.c.RuleSet) - Checking against rule: Rule[identity='ALL',
action=AclAction[action=Action[operation=All, object=All, properties={}],
firewallRule=null], permission=DENY_LOG]
2017-07-11 15:55:31,003 DEBUG [IO-/172.23.38.39:40030]
(o.a.q.s.s.a.c.RuleSet) - Action matches.  Result: DENY_LOG
2017-07-11 15:55:31,003 INFO  [IO-/172.23.38.39:40030] (q.m.a.denied) -
[con:2(FIXGW@/172.23.38.39:40030/default)/ch:1] ACL-1002 : Denied : Publish
Exchange {ROUTING_KEY=request.FIXGW, NAME=request.FIXGW,
VIRTUALHOST_NAME=default}
2017-07-11 15:55:31,003 DEBUG [IO-/172.23.38.39:40030]
(o.a.q.s.m.AbstractConfiguredObject) - authorise returned DENIED
2017-07-11 15:55:31,003 DEBUG [IO-/172.23.38.39:40030] (o.a.q.s.p.frame) -
SEND[/172.23.38.39:40030|1] :
Detach{handle=0,closed=true,error=Error{condition=not-allowed,description=Permission
ACTION(publish) is denied for : Exchange 'request.FIXGW' on VirtualHost
'default'}}
2017-07-11 15:55:31,003 DEBUG [IO-/172.23.38.39:40030]
(o.a.q.s.s.d.DerbyMessageStore) - REMOVE called on message: 3
2017-07-11 15:55:31,003 DEBUG [IO-/172.23.38.39:40030]
(o.a.q.s.p.v.f.FrameHandler) - RECV 0 bytes
...

In log there is routing key same as name. But in client was routing key
specified as TradeReport.

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Java-Broker-Invalid-routing-key-tp7664724.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: [Qpid Java Broker] Get SessionPrincipal

[Vavricka]

Thanks,

  it works like a charm.

 Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Get-SessionPrincipal-tp7663741p7663794.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

[Qpid Java Broker] Get SessionPrincipal

[Vavricka]

Hi, 

  I would like to get current session in Java Broker source code. In class
ProducerFlowControlOverflowPolicyHandler in checkOverfull() method there is
current session get by 

Set sessionPrincipals =
subject.getPrincipals(SessionPrincipal.class);

When I use this for AMQP 1.0 connection, everything goes fine and I get
session. But when I use AMQP 0-10 client for connection to broker,
SessionPrincipal is empty.

I checked that in constructor of AbstractAMQPSession session added to
Subject. But when I get Subject in OverflowPolicyHandler, there is no
SessionPrincipal.

Simplified code how I get current session below:

Subject subject =
Subject.getSubject(AccessController.getContext());
Set sessionPrincipals =
subject.getPrincipals(SessionPrincipal.class);
SessionPrincipal sessionPrincipal =
sessionPrincipals.iterator().next();
AMQPSession session =
sessionPrincipal.getSession();

Am I doing anything wrong?

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Get-SessionPrincipal-tp7663741.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: [Java Broker] Access control rights, routingKey and wildcard

[Vavricka]

I apologize for the part regarding "*" wildcard. I connected to different
broker where ACL rules were different and therefore Java Broker correctly
forbid access.

Wildcard "*" is working, but behavior is different than in topic exchange
(https://qpid.apache.org/releases/qpid-java-6.1.2/java-broker/book/Java-Broker-Concepts-Exchanges.html).
It seems to me when I set routingKey="test.*" in ACL, rule matches every
message with routing key starting with "test." and it does not care about
number of words split by dot (like in topic queue).

Using "*" as wildcard is ok for me. I was just confused that ACL wildcard
works differently from topic exchange.

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Java-Broker-Access-control-rights-routingKey-and-wildcard-tp7662212p7662213.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

[Java Broker] Access control rights, routingKey and wildcard

[Vavricka]

Hi, 

  I am struggling to get working access control rights with specified
routingKey when routingKey contains wildcard "#" or "*".

  When i have ACL rule with "#" wildcard

ALLOW-LOG test PUBLISH EXCHANGE name="broadcast" routingKey="#"

  and I send message with routing key "test", I receive error 

Permission ACTION(publish) is denied for : Exchange 'broadcast' on
VirtualHost 'default'

  but when I set message routing key to "#", message is successfully sent.

  When I use "*" wildcard in routingKey 

ACL ALLOW-LOG amqpsrv PUBLISH EXCHANGE name="broadcast" routingKey="ABCD.*"

  and I send message with routing key "ABCD.test", I receive same error as
before

Permission ACTION(publish) is denied for : Exchange 'broadcast' on
VirtualHost 'default'

  this error is also same when I set message routing key to "ABCD.*".

Is there a way to restrict access by routing key with wildcard? Am I doing
everything correctly? I used
https://qpid.apache.org/releases/qpid-java-6.1.2/java-broker/book/Java-Broker-Security-ACLs.html
as source of information.

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Java-Broker-Access-control-rights-routingKey-and-wildcard-tp7662212.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: [Qpid Java Broker] Remove alternate exchange

[Vavricka]

It worked like a charm.

Thanks.

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Remove-alternate-exchange-tp7660147p7660212.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

[Qpid Java Broker] Remove alternate exchange

[Vavricka]

Hi, 

  I have two exchanges with alternate exchange set to the other exchange.

 Below are the two exchanges in following format 

  broadcast,broadcast_resend
  broadcast_resend,broadcast

  I am trying to remove exchange by REST API.

 When I tried to remove exchange 'broadcast' Java Broker complained that
exchange is used in another exchange as alternate exchange.

  Then I tried to remove alternate exchange from exchange 'broadcast'.
  I tried to remove alternate exchange by configured object update as
described at
https://qpid.apache.org/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Channel-REST-API.html
(section 6.3.5).

  I tried to set parameters to { "alternateExchange" : "" } which failed
with error "Cannot convert '' into a
org.apache.qpid.server.model.Exchange for attribute alternateExchange
(Could not find object of category Exchange with name '')".

  Then I tried to set whole exchange object. I received JSON string of
exchange object, map it to Jackson JsonNode, remove "alternateExchange" key
and then made configured object update of exchange with rest of exchange
parameters. This call successfully passes, but no change is done, alternate
exchange still persists.

  Is this the correct way how to remove exchange with alternate exchange?

  Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Remove-alternate-exchange-tp7660147.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

[Java Broker] SASL connection to REST API

[Vavricka]

Hi, 

 I successfully managed to connect to the Java Broker's REST API by Basic
Authentication using curl and Jersey framework.

cURL command:

curl -v -u admin:admin
http://localhost:8080/api/latest/queue/default/default/test.queue

Java code:

HttpAuthenticationFeature feature = HttpAuthenticationFeature.basic("admin",
"admin");
Client client = ClientBuilder.newClient();
client.register(feature);
client.register(JsonProcessingFeature.class);
WebTarget target =
client.target(UriBuilder.fromUri("http://localhost/api/latest/queue/default/default/test.queue;).port(8080).build());
Response response =
target.request(APPLICATION_JSON).post(Entity.json("{}"));


But when I try to connect using SASL I always get 401 (Unauthorized) status.
cURL command and Java code used for SASL connection below.

cURL command:

curl -v --digest -u admin:admin
http://localhost:8080/api/latest/queue/default/default/test.queue

Java code:

HttpAuthenticationFeature feature =
HttpAuthenticationFeature.digest("admin", "admin");
Client client = ClientBuilder.newClient();
client.register(feature);
client.register(JsonProcessingFeature.class);
WebTarget target =
client.target(UriBuilder.fromUri("http://localhost/api/latest/queue/default/default/test.queue;).port(8080).build());
Response response =
target.request(APPLICATION_JSON).post(Entity.json("{}"));

I also tried to use HttpAuthenticationFeature feature =
HttpAuthenticationFeature.universal("admin", "admin"); with no success (401
status).

Am I doing something wrong?

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Java-Broker-SASL-connection-to-REST-API-tp7659042.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: [Qpid Java Broker] Generate SHA-256 password

[Vavricka]

Many thanks.

I successfully managed to generate SCRAM-SHA256 password by using code from
AbstractScramAuthenticationManager.java.

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Generate-SHA-256-password-tp7658669p7658778.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

[Qpid Java Broker] Generate SHA-256 password

[Vavricka]

Hi, 

 I would like to ask If there is possibility to generate SHA-256 hash for
password by external program and then paste it to config.json file?

 Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Generate-SHA-256-password-tp7658669.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

Java Broker QMF2 Management

[Vavricka]

Hi, 

  I am using Java Broker 6.0.2. 

  In documentation here
https://qpid.apache.org/releases/qpid-java-6.0.4/java-broker/book/Java-Broker-Management-Channel-QMF.html
is described that QMF2 can be enabled by plugin.

  When I try to google it how to add QMF2 plugin I found only some info
regarding older versions (0.22) here
https://svn.apache.org/repos/asf/qpid/branches/QPID-5048-maven3-build/tools/src/java/README-Java-Broker.txt
. I tried to add jar to lib directory
(qpid-broker-plugins-management-qmf2-0.32.jar and
qpid-broker-plugins-management-qmf2-0.32.jar), enable plugin in
configuration, but exception below was thrown during startup.

13:52:05.863 [main] ERROR o.a.q.s.u.ServerScopedRuntimeException - A state
transition method must return a ListenableFuture. Method doStop on
org.apache.qpid.server.qmf2.QmfManagementPluginImpl does not meet this
criteria.
13:52:05.868 [main] ERROR org.apache.qpid.server.Broker - Exception during
startup
org.apache.qpid.server.util.ServerScopedRuntimeException: A state transition
method must return a ListenableFuture. Method doStop on
org.apache.qpid.server.qmf2.QmfManagementPluginImpl does not meet this
criteria.
at
org.apache.qpid.server.model.ConfiguredObjectTypeRegistry.addStateTransitions(ConfiguredObjectTypeRegistry.java:982)
~[qpid-broker-core-6.0.2.jar:6.0.2]

  Is still possible to add QMF2 management plugin ?

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Java-Broker-QMF2-Management-tp7651474.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: Java Broker exclusive binding

[Vavricka]

rgodfrey wrote
> I think what you are looking for here is a new type of exchange (or a
> variation on the topic exchange) where the message is routed to at
> most one binding - which would require bindings to have some sort or
> ordering / priority placed upon them.  There is nothing like that
> currently.

I meant exactly that, sorry for mine vague explanation.

Thanks a lot for clarifying.

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Java-Broker-exclusive-binding-tp7651458p7651464.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

Java Broker exclusive binding

[Vavricka]

Hi, 

 I am using java broker version 6.0.2. I have one queue named 'test.queue'
and on this queue set two bindings. First binding is more specific 'test.#'
and second binding is '#'. 

 When I send message with routing key 'test.a', message is forwarded by both
bindings. Is it possible to set bindings (or queue) to use only the most
specific option (binding 'test.#') when it can be applied?

 I know that similar behavior (like binding '#') can be achieved by setting
alternate exchange, but it will be helpful if some configuration options
could allow using only one binding for routed message.

 In REST API definitions I found attribute named 'type' which looks
promising, but unfortunately I couldn't find any documentation about it.

 Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Java-Broker-exclusive-binding-tp7651458.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: Filtering issues

[Vavricka]

Gordon Sim wrote
> For the timestamp query, why are you dividing by 1000? The JMSTimestamp is
> in milliseconds. Is  'tomorrow' a Date object?

Thanks for pointing this out, I used same code for testing qpid c++ broker.
Qpid c++ broker expects timestamp in seconds.

When I removed division by 1000, code is working correctly now.


Gordon Sim wrote
> However AMQP 0-10 defines the message-id to be a uuid, JMS 
> defines it to be a string. Is it possible there is some issue in the 
> exact format being compared?

You are also correct in this one. I used to retrieve messageID by 'String
messageID = msg.getJMSMessageID();' and returned string was in format
'ID:UUID', but selector in consumer expects string without 'ID:' prefix.
When I removed the prefix code start to work as expected.


Gordon Sim wrote
> Ok, so I _believe_ the java broker does not support the AMQP style 
> naming of properties for AMQP 1.0. You can use the JMS names however.

Is planned support for AMQP naming style properties for AMQP 1.0?

Thanks a lot for your help.

Regards,
Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Filtering-issues-tp7642996p7643131.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: Filtering issues

[Vavricka]

I am using Qpid Java Broker 6.0.2.



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Filtering-issues-tp7642996p7642998.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

Filtering issues

[Vavricka]

Hi, 

  i am having some issues with filtering messages.

AMQP 0-10 (client 6.0.2 or 6.1.0):

* message ID filtering JMS style

 Consumer created by 'session.createConsumer(this.utils.getQueue(RTG_QUEUE),
"JMSMessageID = '" + messageID + "'");', the message is in the queue and
message have correct message ID, but when selector is specified when
creating consumer, no message is received.

* timestamp filtering JMS style

 Consumer created by 'session.createConsumer(this.utils.getQueue(RTG_QUEUE),
"JMSTimestamp > " + tomorrow.getTime()/1000);'. Message was created with
today's timestamp so message should not be received, but message was
received.

AMQP 1.0 (client 0.9.0)

* correlation ID filtering AMQP style

 Consumer created by 'session.createConsumer(this.utils.getQueue(RTG_QUEUE),
"\"amqp.correlation_id\" = '" + correlationID + "'");'. Message in queue
have correct Correlation ID, but when selector is specified when creating
consumer, no message is received.

* message ID filtering AMQP style

 Consumer created by 'session.createConsumer(this.utils.getQueue(RTG_QUEUE),
"\"amqp.message_id\" = '" + messageID + "'");'. Message in queue have
correct message ID, but when selector is specified when creating consumer,
no message is received.

* priority filtering AMQP style

 Consumer created by 'session.createConsumer(this.utils.getQueue(RTG_QUEUE),
"\"amqp.priority\" > 5");'. Message in queue have priority set to 9, but
when selector is specified when creating consumer, no message is received.

* subject filtering AMQP style

 Consumer created by 'session.createConsumer(this.utils.getQueue(RTG_QUEUE),
"\"amqp.subject\" = 'my.subject.key'");'. Message in queue have correct
subject, but when selector is specified when creating consumer, no message
is received.

* timestamp filtering AMQP style

 Consumer created by 'session.createConsumer(this.utils.getQueue(RTG_QUEUE),
"\"amqp.creation_time\" >= " + yesterday.getTime());'. Message was created
with today's timestamp so message should be received, but no message was
received, when selector is specified.

Is this known issues? Am I doing everything right?

Best regards,
Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Filtering-issues-tp7642996.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: ACL Java Broker 6.0.2 AMQP 1.0

[Vavricka]

Hi,

 thanks for quick reply.

 Including this in version 6.1 is OK for me.

 Best Regards,
 Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/ACL-Java-Broker-6-0-2-AMQP-1-0-tp7642793p7642947.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: ACL Java Broker 6.0.2 AMQP 1.0

[Vavricka]

If there any problems viewing ACL rule or log,it maybe connected to nabble
formatting. 

You can view original message at
http://qpid.2158936.n2.nabble.com/ACL-Java-Broker-6-0-2-AMQP-1-0-td7642793.html



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/ACL-Java-Broker-6-0-2-AMQP-1-0-tp7642793p7642794.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

ACL Java Broker 6.0.2 AMQP 1.0

[Vavricka]

Hi, 

  I am testing Qpid Java Broker 6.0.2. I am struggling with setting ACL
rights for AMQP 1.0 (qpid-jms-client 0.9.0) client. 

  For AMQP 0-10 (qpid-client 6.0.2) ACL rights are working as expected.

  When I use same ACL rights for AMQP 1.0 as in AMQP 0-10, looks like client
is not restricted at all. I can publish to exchanges, consume queues, etc.

  When I set only one ACL rule



  I cannot consume from queue but I can still publish to exchange with AMQP
1.0 client.

  Below is log of PUBLISH to exchange from AMQP 1.0 client with
amqp.traceFrames=true option:



Is there need some special configuration for AMQP 1.0 to get ACL working as
in AMQP 0-10?

Vavricka



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/ACL-Java-Broker-6-0-2-AMQP-1-0-tp7642793.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