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

[Oleksandr Rudyy]

+1

I tested release artifacts as follows
* verified signatures and checksums
* built successfully Qpid broker from source distribution bundle with
running all unit tests using java 17 on Fedora 38
* executed successfully integration tests for test profile java-bdb.1-0 and
java-bdb.0-9
* started broker from binaries bundle and created virtual host, queues,
binding, etc using web management console


On Thu, 8 Feb 2024 at 10:49, 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
>
>

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

[Oleksandr Rudyy]

+/-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
> >
> >
>

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

[Oleksandr Rudyy]

+1

I tested as follows:
* using OpenJDK17 built successfully broker from source bundle with running
successfully unit and integration tests (for profiles default,
java-bdb.0-9, java-bdb.1-0)
* verified checksums and signatures
* started broker and used JMS client HelloWorld example to send/receive
test message



On Fri, 25 Aug 2023 at 11:10, 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
>
>

Re: [VOTE] Release Qpid Broker-J 9.1.0

[Oleksandr Rudyy]

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

[Oleksandr Rudyy]

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

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

[Oleksandr Rudyy]

+1

my tests included the following
* verified signatures and checksums
* built and ran successfully all unit tests from source bundle using
JDK11 with default profile
* built and ran successfully all unit/integration tests from source
bundle using JDK17 with profiles java-bdb.0-9, java-bdb.1-0
* started broker from a binary distribution and performed basic
operations in web management console



On Mon, 14 Nov 2022 at 11:51, 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

Re: [VOTE] Release Apache Qpid JMS 2.1.0

[Oleksandr Rudyy]

+1

I tested release artifacts as below
* verified signatures and checksums
* built successfully from source bundle with running all tests
* ran HelloWorld example against Qpid Broker-J built from branch 8.0.x

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

[Oleksandr Rudyy]

+1

I tested release artifacts as below:
* verified signatures and checksums
* bult successfully client from source bundle with running all the tests
* ran HelloWorld against Qpid Broker-J built from branch 8.0.x

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

[Oleksandr Rudyy]

+1
* verified signatures and checksums
* built from source bundle with running all unit tests
* ran the Hello World example against Qpid Broker-J built from master branch

On Fri, 22 Apr 2022 at 18:19, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 2.0.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/2.0.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1239
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12351646
>
> The notable change from the 1.x releases (which will continue) is that
> it implements the new "jakarta.jms" packaged spec from
> jakarta.jms:jakarta.jms-api:3.0.0 rather than the older "javax.jms"
> packaged spec from previous releases. Otherwise its basically the
> same.
>
> 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-1239
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 2.0.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.6.0

[Oleksandr Rudyy]

+1
* verified signatures and checksums
* built from source bundle with running all tests on OpenJDK 11
* ran Qpid Broker-J integration tests with staged artifacts for v1.6.0

On Mon, 28 Mar 2022 at 17:07, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.6.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.6.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1237
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12351131
>
> 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-1237
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.6.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: QPID Broker-J Java 11

[Oleksandr Rudyy]

+1

Please feel free to migrate Qpid Broker-J to java 11. I cannot think
about any issue with an update to java 11.

Kind Regards,
Alex

On Sat, 26 Mar 2022 at 07:53, Daniil Kirilyuk  wrote:
>
> Hi Colleagues,
>
>
>
> We'd like to update the java version from 8 to 11 for QPID Broker-J.
> Although Java 8 is still being supported, Java 11 is already actively used
> in development as well as in production environments.
>
> There are several issues pointed out to ensure support for java 9 and 11 -
> QPID-8241, QPID-7885, QPID-8267.
>
> Are there any implications to consider? Are there any tasks to be done or
> issues to be solved before updating the java version?
>
>
>
> Kind regards,
>
> Daniil Kirilyuk

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

magus

[Oleksandr Rudyy]

This is a very fun and powerful build, the Dragonknight.
Race Aasimar Angelkin All points from levels into strength
Str: 19 Dex:13 Con: 10 Int: 13 Wis: 11 Cha: 16
Level   Class   Feat
1  Eldritch Scion(1)Dodge
2  Scaled Fist(1) Crane Style
3  Eldritch Scion(2)Weapon Focus (Greataxe)
4  Eldritch Scion(3)
5  Eldritch Scion(4)Dazzling Display
6  Dragon Disciple(1)
7  Dragon Disciple(2) Crane Wing, Power Attack
8  Dragon Disciple(3)
9  Dragon Disciple(4) Cornugon Smash
10Eldritch Knight (1)  Shatter Defenses
11Eldritch Knight (2)  Crane Ripose
12Eldritch Knight (3)
13Eldritch Knight (4)  Improved Critical (Greataxe)
14Eldritch Knight (5)  Weapon Specialization (Greataxe)
15Eldritch Knight (6)  Combat Expertise
16Eldritch Knight (7)
17Eldritch Knight (8)  Greater Weapon Focus (Greataxe)
18Eldritch Knight (9)  Critical Focus
19Eldritch Knight (10)Intimidating Prowess
20Eldritch Scion(5) Dreadful Carnage


STR:20(18+2) DEX:14 CON:9 INT:8 WIS:7 CHA:16



Skills: Mobility, Persuasion, Athletics


1) Magus 1 - Combat Reflexes, Seize the Moment
2) Magus 2 -
3) Magus 3 - Exotic Wpn(Fauchard), Extended Magic
4) Magus 4 - STR+1
5) Magus 5 - Wpn Focus(Fauchard), Blind Fight
6) Magus 6 - Enduring Blade
7) Magus 7 - Dazzling Display
8) Magus 8 - STR+1
9) Magus 9 - Shatter Defenses, Ghost Blade
10) Magus 10 -
11) Magus 11 - Imp Crit(Fauchard), Outflank
12) Magus 12 - STR+1, Dimension Strike
13) Magus 13 - Power Attack
14) Magus 14 -
15) Magus 15 - Dreadful Carnage, Bane Blade
16) Magus 16 - STR+1
17) Magus 17 - Greater Wpn Focus(Fauchard), Wpn Spec(Fauchard)
---
18)
19)
20)

Spells:

1) Shield, Enlarge Person, True Strike, Expeditious Retreat, Vanish,
  Grease
2) Mirror Image, Effortless Armor, Blur, Glitterdust, Invisibility,
 Web
3) Displacement, Haste, Slow, Stinking Cloud, Vampiric Touch,
 Lightning Bolt
4) Greater Invisibility, Dragon's Breath, Shout, Dimension Door,
 Controlled Fireball
5) Cloudkill, Baleful Polymorph, Acidic Spray, Cone of Cold
6) True Seeing, Sirocco, Dragonkind I


Starting StatsLevel+BABClassFeatSourceMagus
ArcanaMythic AbilitiesMythic FeatsSpellsSpecial
Mythic AbilitiesMythic Feats

2
Str: 71+0Eldritch Scion(1)Weapon FinesseLevel
1 Feat
3
Dex: 192+1Eldritch Scion(2)
4
Con: 103+2Eldritch Scion(3)Weapon Focus (Rapier)
 Level 3 FeatArcane Accuracy
5
Int: 94+3Eldritch Scion(4)
6
Wis: 105+3Eldritch Scion(5)Fencing Grace
Spell PenetrationLevel 5 Feat
Bonus Magus FeatElemental Barrage
  `
7
Cha: 206+4Eldritch Scion(6)Enduring Blade
8
Race: Aasimar7+5Eldritch Scion(7)Greater Spell
PenetrationLevel 7 Feat
Ascendant Element: Electricity
9
Background: Martial Disciple8+6Eldritch Knight(1)
OutflankBonus Combat Feat
10
9+7Eldritch Knight(2)DodgeLevel 9 Feat
Dimension StrikeAbundant Casting
11
10+8Eldritch Knight(3)
12
11+9Eldritch Knight(4)Crane StyleLevel 11 Feat
13
12+10Eldritch Knight(5)Crane WingBonus Combat
FeatSpell Penetration
14
13+11Eldritch Knight(6)Crane RiposteLevel 13
Feat
15
14+12Eldritch Knight(7)
16
15+13Eldritch Knight(8)Spell Focus (Evocation)
Leve 15 Feat
Improved Abundant Casting
17
16+14Eldritch Knight(9)Greater Weapon Focus
(Rapier)Bonus Combat Feat
18
17+15Eldritch Knight(10)Greater Spell Focus
(Evocation)Level 17 Feat
19
18+16Eldritch Scion(8)Weapon Focus
20
19+16Eldritch Scion(9)Critical FocusLevel 19
FeatThundering BlowsSpell Focus
21
20+17Eldritch Scion(10)


Elf - starting stats: STR 18 - DEX 13 - CON 10 - INT 12 - CHA 14
Lvl 1 dodge
Lvl 2 crane style (monk)
Lvl 3 weapon focus elven curve blade
Lvl 4
Lvl 5 combat reflexes
Lvl 6
Lvl 7 crane wing, power attack
Lvl 8
Lvl 9 Cornugon smash
Lvl 10 shattered defenses
Lvl 11 intimidating prowess
Lvl 12
Lvl 13 improved critical
Lvl 14 critical focus
Lvl 15 Outflank
Lvl 16
Lvl 17 Crane riposte
Lvl 18 GWFocus elven curve blade
Lvl 19 Seize the moment
Lvl 20 Weapon Specialization elven curve bladeBloodline
Ascendance: ElementalSecond Bloodline: Bronze Drago




Eldritch Disciple Build
Pitborn Tiefling Lawful Alignment
Str 19, Dex 13, Con 11, Int 13, Wis 7, Cha 16
Level 1 Eldritch Scion Magus, Draconic 

Re: Issue with the same name for topic and queue

[Oleksandr Rudyy]

Hi Andrey,

Only persistent messages survive the change of the master. The
transient messages are lost on mastership transfer.
Could you please verify that persistent messages are published into
durable queues?

As for error 500 "Please correct the problem and retry your
operation." reported for the binding delete operation, could you
please provide exception stack traces reported into broker logs?


Kind Regards,
Alex




On Tue, 11 Jan 2022 at 19:29, Andrey Shi  wrote:
>
> Hi all,
>
> I have a three-node cluster qpid broker-j 8.0.6
>
> I create a topic and durable queue with the same name (for example, random 
> generated Ae8M6kKM) and make a binding. At this stage, I can send and receive 
> messages.
>
> I move the master node to another server. After that, all messages that I 
> sent to the topic Ae8M6kKM dropped.
> If I try to delete the binding, web interface returns an error with code 500 
> "Please correct the problem and retry your operation.", but the binding is 
> deleted successfully. After the binding recreation, all messages are sent and 
> received correctly.
>
> If I move the master node, the issue reproduces again. I have reproduced this 
> behaviour on different clusters.
>
> Does anyone know how to fix this?
>
> Thanks
>
>
> Andrey
> -
> 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-M4

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built client from source bundle with running all the tests
* ran successfully HelloWorld example against Qpid Broker-J built from main


On Mon, 20 Dec 2021 at 20:03, Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M4 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-M4-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1236
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12350719
>
> 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-1236
>  
>
>
> The dependency for the protocol engine or the client itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M4
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M4
>
>
> --
> 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 0.61.0

[Oleksandr Rudyy]

+1

* verified checksums and signatures
* built successfully client from source bundle with running all unit tests
* ran successfully all Qpid broker system tests using v0.61.0 staged artefacts

On Mon, 20 Dec 2021 at 18:54, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 0.61.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.61.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1235
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12351130
>
> 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-1235
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.61.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.5.0

[Oleksandr Rudyy]

+1

* verified checksums and signatures
* built successfully client from source bundle with running all unit tests
* ran successfully all Qpid broker system tests using v1.5.0 staged artefacts

On Mon, 20 Dec 2021 at 18:07, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.5.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.5.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1234
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12351054
>
> 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-1234
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.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 0.60.0

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran tests successfully from source bundle
* ran successfully Qpid Broker-J integration tests using v0.60.0 maven
staged artefacts


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

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran tests successfully from source bundle
* ran successfully Qpid Broker-J integration tests using v1.4.0 staged
maven artefacts

On Mon, 13 Dec 2021 at 18:23, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.4.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.4.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1230
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12350710
>
> 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-1230
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.4.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-M3

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built successfully from source code with running all tests
* ran successfully "HelloWorld" example against Qpid Broker-J built from main

On Tue, 19 Oct 2021 at 23:21, Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M3 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-M3-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1229
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12350232
>
> 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-1229
>  
>
>
> The dependency for the protocol engine or the client itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M3
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M3
>
>
> --
> 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.3.0

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built successfully from sources with running all unit tests
* ran successfully Qpid Broker integration tests on main branch using
staged client artefacts

On Mon, 18 Oct 2021 at 17:59, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.3.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.3.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1228
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12350657
>
> 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-1228
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.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 Proton-J 0.33.10

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built successfully from source bundle with running all the tests
* ran successfully Qpid Broker-J integration tests using staged maven
artifacts for Qpid Proton-J 0.33.10 and Qpid JMS client 0.59.0

On Thu, 14 Oct 2021 at 18:39, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.33.10 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.10-rc1/
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1227
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12349270
>
> 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-1227
> 
>   
>
> The dependency for proton-j would then be:
>
>   
> org.apache.qpid
> proton-j
> 0.33.10
>   
>
> -
> 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.2.0

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran successfully tests from source bundles
* ran successfully Qpid Broker-J integration tests using v1.2.0 staged
artifacts and JDK11

On Fri, 24 Sept 2021 at 15:52, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.2.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.2.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1226
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12350375
>
> 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-1226
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.2.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 Proton-J 0.33.9

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built successfully from source bundle
* ran successfully Qpid Broker-J integration tests (on main branch)
using qpid-jms clients 0.54.0/0.59.0/1.1.0 and staged proton-j 0.33.9
artifacts

On Tue, 24 Aug 2021 at 17:43, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.33.9 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.9-rc1/
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1224
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12350517
>
> 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-1224
> 
>   
>
> The dependency for proton-j would then be:
>
>   
> org.apache.qpid
> proton-j
> 0.33.9
>   
>
> -
> 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: Possibility of a Broker-J 8.0.6 release?

[Oleksandr Rudyy]

Hi Tom,
I will try to build version 8.0.6 this week.
You can track the release JIRA QPID-8561.

Kind Regards,
Alex

On Tue, 17 Aug 2021 at 18:55, Tom Jordahl  wrote:
>
> Hi Qpid folks,
>
> Would it be possible to release Broker-J 8.0.6 ?
>
> I need the resolution of https://issues.apache.org/jira/browse/QPID-8552 - 
> Management interface should reject OPTIONS - which was flagged by our 
> security scanners, in a release.
>
> Thanks.
> --
> Tom

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

Re: [Broker-J] Http management interface should ignore OPTIONS method

[Oleksandr Rudyy]

Hi Tom,
The Qpid Broker-J supports configuring CORS settings to allow access
to REST API from different origins. This can be done via HTTP
management attributes
(corsAllowOrigins,corsAllowMethods,corsAllowHeaders,corsAllowCredentials).
Though, by default, the origin(s), allowed headers and methods are not
set. Thus, it is actually safe to disable the OPTIONS method when no
original related attribute is set.
We will look into adding corresponding changes into version 8.0.6.

Kind Regards,
Alex

On Thu, 15 Jul 2021 at 15:47, Tom Jordahl  wrote:
>
> Hello Devs,
>
> In our environment we run security scanning tools.  They flag any HTTP port 
> that supports the OPTIONS method as a problem:
>   “Web servers that respond to the OPTIONS HTTP method expose what other 
> methods are supported by the web server, allowing attackers to narrow and 
> intensify their efforts.”
>
> I don’t see Qpid having any need to support this method, so I have filed a 
> bug with a patch that blocks the OPTIONS method: 
> https://issues.apache.org/jira/browse/QPID-8552. I would love to have this 
> patch in the next 8.x release of Broker-J.
>
> Thoughts?
> --
> Tom

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

Re: Welcome to Tomas Vavricka as an Apache Qpid committer

[Oleksandr Rudyy]

Welcome, Tomas!

On Thu, 15 Jul 2021 at 10:36, Robbie Gemmell  wrote:
>
> The Qpid PMC voted to grant commit rights to Tomas Vavricka in
> recognition of his contributions to the project, which he accepted and
> has now been onboarded.
>
> Welcome, Tomas!
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

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

Re: [VOTE] Commit rights for Tomas Vavricka

[Oleksandr Rudyy]

The vote is now closed with 8 votes in favour and none against. The
vote has passed.

Kind Regards,
Alex

On Mon, 5 Jul 2021 at 19:22, Martin Krása  wrote:
>
> +1
>
> On 01/07/2021, Gordon Sim  wrote:
> > +1
> >
> > On Thu, Jul 1, 2021 at 12:23 AM Alex Rudyy  wrote:
> >>
> >> Hi folks,
> >>
> >> I'd like to call a vote to offer commit rights to Tomas Vavricka
> >>
> >> Tomas has been contributing to Qpid Broker-J for a couple of years
> >> starting from 2017. In particular, he submitted an initial
> >> implementation of the queue ring policy (QPID-7618) and reject policy
> >> (QPID-7815) for Qpid Broker-J back in 2017. He is an author of
> >> certificate revocation feature in Qpid Broker-J (QPID-8367). Tomas
> >> contributed a number of bug fixes and improvements for Qpid Broker-J
> >> (QPID-83543, QPID-8354,QPID-8456,QPID-8460,QPID-8458,QPID-8459). He
> >> tested and voted on a number of Qpid Broker-J releases. He also has
> >> been raising various issues with Qpid Broker-J and Qpid JMS Client for
> >> AMQP 1.0 in the user mailing list and creating JIRAs for the issues.
> >>
> >> I feel it is time we offer Tomas commit-rights of his own.
> >>
> >> I will close this vote at 00:00 UTC on Friday 9th June, at which timeI
> >> will tally the votes.
> >>
> >> Regards,
> >> Alex Rudyy
> >>
> >
> >
> > -
> > 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.1.0

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran tests from source bundle
* ran Qpid broker integration tests with staged 1.1.0 artifacts using JDK 11

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

[RESULT][VOTE] Release Qpid Broker-J 8.0.5

[Oleksandr Rudyy]

There were 4 binding +1 votes and 1 non-binding +1 community vote. The
vote has passed.

The voting thread can be found here:
https://lists.apache.org/thread.html/ra341858db3067adba17c8e7a4a3f11d0be6fe75087149123dc8f3b84%40%3Cusers.qpid.apache.org%3E

I will add the archives to the dist release repo and release the maven
staging repo shortly. The website will be updated once the artefacts
have had time to sync to the mirrors and maven central.

Kind Regards,
Alex

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

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran successfully tests from source bundle
* started Qpid broker-j and used web management console to create
queue, groups, etc
* verified new operational logs
* ran successfully HelloWorld examples from Qpid JMS Client and Proton-J 2

On Tue, 15 Jun 2021 at 13:00, Alex Rudyy  wrote:
>
> Hi folks,
>
> I built release artefacts for Qpid Broker-J version 8.0.5 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/8.0.5-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1222/
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=1234
>
> Kind Regards,
> Alex
>
> 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-1222/
> 
> 
>
> -
> 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-M2

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran tests from source bundle
* ran HelloWorld using staged artefacts against Qpid Broker-J built
from main branch

On Tue, 25 May 2021 at 20:28, Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M2 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-M2-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1221
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/projects/PROTON/versions/12350154
>
> 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-1221
>  
>
>
> The dependency for the protocol engine or the client itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M2
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M2
>
>
> --
> 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 0.59.0

[Oleksandr Rudyy]

+1

* built and ran tests from source distribution bundle
* verified checksums
* ran Qpid Broker-J integration tests using staged client artefacts

On Mon, 24 May 2021 at 11:44, Robbie Gemmell  wrote:
>
> Bumpety
>
> On Wed, 19 May 2021 at 17:44, Robbie Gemmell  wrote:
> >
> > Hi folks,
> >
> > I have put together a spin for a 0.59.0 Qpid JMS client release,
> > please give it a test out and vote accordingly.
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/jms/0.59.0-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1220
> >
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12350077
> >
> > 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-1220
> > 
> >   
> >
> > The dependency for the client itself would then be:
> >
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 0.59.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: Configuring an in-memory QPID Broker-J 8.0.4 with behaviourOnUnknownDeclareArgument: ignore

[Oleksandr Rudyy]

Hi Siman,

I missed the fact that connection context is checked for the variable.
The context variables are inherited from the parent objects in the
object hierarchy. Thus, you can declare the corresponding variable on
the connection parent (Port) or parent of a parent (Broker).

{
  "name": "Embedded Broker",
  "modelVersion": "8.0",
  "context": {"queue.behaviourOnUnknownDeclareArgument":"IGNORE"},
 ...

Kind Regards,
Alex

On Fri, 21 May 2021 at 17:08, Simon Baptista  wrote:
>
> So I'm digging around the source, I think the issue might be related to the
> nodeType of the nodeAutoCreationPolicies
>
> = AMQChannel.java. lines 3040-3042 =
>
> Queue.BehaviourOnUnknownDeclareArgument unknownArgumentBehaviour =
>
> getConnection().getContextValue(Queue.BehaviourOnUnknownDeclareArgument.class,
>
> Queue.UNKNOWN_QUEUE_DECLARE_ARGUMENT_BEHAVIOUR_NAME);
>
> =
>
> would suggest to me that the context value is on the connection rather than
> on the queue itself.
>
> However attempting to configure a nodeType "connection" throws an error too:
>
> "The node type of a NodeAutoCreationPolicy must be a valid child type of a
> VirtualHost, 'connection' is not."
>
> even though both Queue and Connection are interfaces which extend
> ConfiguredObject.
>
>
> And as you can tell, I'm thoroughly lost.
>
> I'm only mentioning this in the hope that this triggers an idea for someone.
>
> Here's what my virtualhostnodes config looks like right now:
>
> 
>
>   "virtualhostnodes": [
> {
>   "name": "default",
>   "type": "Memory",
>   "defaultVirtualHostNode": "true",
>   "virtualHostInitialConfiguration" : "{\"type\": \"Memory\",
> \"nodeAutoCreationPolicies\":
> [{\"pattern\":\".*\",\"createdOnPublish\":\"true\",\"createdOnConsume\":\"true\",\"nodeType\":\"queue\",\"attributes\":{}},
> {\"pattern\":\".*\",\"createdOnPublish\":\"true\",\"createdOnConsume\":\"true\",\"nodeType\":\"connection\",\"attributes\":{\"context\":
> {\"queue.behaviourOnUnknownDeclareArgument\":\"IGNORE\"}}}] }"
> }
>   ]
> ===
>
>
>
>
> --
> 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
>

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

Re: Direct memory in Qpid 7.0.7

[Oleksandr Rudyy]

Hi Rajashekar,
Please check Qpid Broker-J documentation how memory is used
http://qpid.apache.org/releases/qpid-broker-j-8.0.4/book/Java-Broker-Runtime-Memory.html#Java-Broker-Runtime-Memory

Kind Regards,
Alex

On Tue, 18 May 2021 at 19:42, rhudumula
 wrote:
>
> Hi Team,
>
> I would like to understand a few things around direct-memory in Qpid 7.0.7
> 1) What is direct memory used for? only message-payloads and headers? I read
> connection data is also held here (ref:
> http://qpid.2158936.n2.nabble.com/Java-broker-OOM-due-to-DirectMemory-tc7662358.html#a7662372)
>
> 2) Our typical message-size is 500bytes. Heap and direct memory allocations
> are 36GB and 13GB respectively. Do you see any problem here? We have around
> 120 connections with 20 sessions per connection on a Qpid broker.
>
> 3) Is there a doc that helps us understand design of the direct-memory
> usage? Our heap usage is hitting 100% while the direct-memory usage is under
> 2%. This is mostly around the creation of new connections/sessions from a
> new set of servers.
>
> Thanks,
> Rajashekar
>
>
>
> --
> 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
>

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

Re: [DISCUSS] bumping Qpid JMS to 1.0.0 and requiring Java 11+

[Oleksandr Rudyy]

+1 to both: JDK11 and bumping Qpid JMS up to version 1.0.0

On Thu, 15 Apr 2021 at 13:16, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I would like to propose bumping Qpid JMS up to version 1.0.0+ for
> future releases, and simultaneously require Java 11+ for those new
> releases, leaving further Java 8 support efforts with the existing 0.x
> stream. Barring discussion otherwise I would look to release such a
> combination in May.
>
> Java 11 has been the current Java LTS release since September 2018,
> and Java 17 will arrive in September to supplant even it. It is over 4
> years since we required Java 8+ usage, which was itself a bit over 2
> years after first requiring Java 7+ usage (in the old JMS client, the
> current one started out on Java 7+). I have seen other projects
> discussing transition to Java 11+ for over a year now, with some since
> having made the change and some being in progress or imminently so. I
> think now is an appropriate time to begin requiring Java 11+.
>
> On the version number I think the codebase has been stable for several
> years and the API is fixed, so it's probably long overdue that we just
> did it. Other versions numbers are still available if we need them
> later.
>
> Doing both at the same time would make it simpler/clearer to
> distinguish old and new, simplifying doing future maintenance releases
> for the old 0.x line to support JDK8 users for a further period of
> time, for example if a security issue arises or just to backport some
> important fixes.
>
> Thoughts?
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

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

Re: Configuring an in-memory QPID Broker-J 8.0.4 with behaviourOnUnknownDeclareArgument: ignore

[Oleksandr Rudyy]

Hi Simon,
You set context variable "queue.behaviourOnUnknownDeclareArgument" as
an attribute in your virtual host initial configuration.
You need to set it as an entry in "context" attribute, for example,
{
...
"context": {
   "queue.behaviourOnUnknownDeclareArgument": "IGNORE"
 }
...
}

Thus, your virtual host initial configuration should be like the one below

{
  "type": "Memory",
  "nodeAutoCreationPolicies": [
{
  "pattern": ".*",
  "createdOnPublish": "true",
  "createdOnConsume": "true",
  "nodeType": "queue",
  "attributes": {
"context": {
  "queue.behaviourOnUnknownDeclareArgument": "IGNORE"
}
  }
}
  ]
}
or in strigified form


"{\"type\":\"Memory\",\"nodeAutoCreationPolicies\":[{\"pattern\":\".*\",\"createdOnPublish\":\"true\",\"createdOnConsume\":\"true\",\"nodeType\":\"queue\",\"attributes\":
{\"context\": {\"queue.behaviourOnUnknownDeclareArgument\":\"IGNORE\"
}}}]}"

It seems that instructions [1], you followed, are based on Qpid
instructions [2] but I could be wrong.

Kind Regards,
Alex

[1] 
https://novotnyr.github.io/scrolls/qpid-as-mocking-amqp-broker-for-integration-tests/
[2] https://cwiki.apache.org/confluence/display/qpid/How+to+embed+Qpid+Broker-J

On Tue, 30 Mar 2021 at 15:27, Simon Baptista  wrote:
>
> Hi,
>
> I'm trying to use QPID in-memory for the purpose of an integration test 
> against a RabbitMQ consumer.
>
> My application uses a RabbitMQ specific queue declaration argument 
> (x-expires). I've seen through googling that 
> "queue.behaviourOnUnknownDeclareArgument: Ignore" Will do what I want to do.
>
> This is what my config looks like at the moment (I'm making guesses about the 
> nodeAutoCreationPolicies being the default template for how elements are 
> created...):
> ===
> {
>   "name": "Embedded Broker",
>   "modelVersion": "7.0",
>   "authenticationproviders": [
> {
>   "name": "hardcoded",
>   "type": "Plain",
>   "secureOnlyMechanisms": [],
>   "users": [
> {
>   "name": "guest",
>   "password": "guest",
>   "type": "managed"
> }
>   ]
> }
>   ],
>   "ports": [
> {
>   "name": "AMQP",
>   "port": "${qpid.amqp_port}",
>   "bindingAddress": "127.0.0.1",
>   "protocols": [
> "AMQP_0_9_1"
>   ],
>   "authenticationProvider": "hardcoded",
>   "virtualhostaliases": [
> {
>   "name": "defaultAlias",
>   "type": "defaultAlias"
> }
>   ]
> }
>   ],
>   "virtualhostnodes": [
> {
>   "name": "default",
>   "type": "Memory",
>   "defaultVirtualHostNode": "true",
>   "virtualHostInitialConfiguration": "{\"type\": \"Memory\", 
> \"nodeAutoCreationPolicies\": 
> [{\"pattern\":\".*\",\"createdOnPublish\":\"true\",\"createdOnConsume\":\"true\",\"nodeType\":\"queue\",
>  \"attributes\": {\"queue.behaviourOnUnknownDeclareArgument\":\"IGNORE\"}}]}"
> }
>   ]
> }
> =
>
> And it's doesn't appear to be doing anything as my application is throwing:
> ===
> java.io.IOException: null
> at com.rabbitmq.client.impl.AMQChannel.wrap(AMQChannel.java:129)
> at com.rabbitmq.client.impl.AMQChannel.wrap(AMQChannel.java:125)
> at com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:147)
> at com.rabbitmq.client.impl.ChannelN.queueDeclare(ChannelN.java:968)
> at 
> com.rabbitmq.client.impl.recovery.AutorecoveringChannel.queueDeclare(AutorecoveringChannel.java:342)
> ...
> Caused by: com.rabbitmq.client.ShutdownSignalException: connection error; 
> protocol method: #method(reply-code=542, reply-text=Error 
> creating queue 'myqueue_dtmanager_task': Unsupported queue declare 
> argument(s) : x-expires, class-id=50, method-id=10) at 
> com.rabbitmq.utility.ValueOrException.getValue(ValueOrException.java:66)
> ===
>
>
> This is how I am initialising my broker:
> ===
>
> public class BrokerManager {
>
> private static final String DEFAULT_INITIAL_CONFIGURATION_LOCATION = 
> "qpid-it.json";
>
> private SystemLauncher systemLauncher;
>
> public BrokerManager() {
> this.systemLauncher = new SystemLauncher();
> }
>
> public void start() throws Exception {
> this.systemLauncher.startup(createSystemConfig());
> }
>
> public void shutdown() {
> this.systemLauncher.shutdown();
> }
>
> private Map createSystemConfig() throws 
> IllegalConfigurationException {
> Map attributes = new HashMap<>();
> URL initialConfigUrl = 
> BrokerManager.class.getClassLoader().getResource(DEFAULT_INITIAL_CONFIGURATION_LOCATION);
> if (initialConfigUrl == null) {
> throw new IllegalConfigurationException("Configuration location '" + 
> DEFAULT_INITIAL_CONFIGURATION_LOCATION + "' not found");
> }
> attributes.put(SystemConfig.TYPE, "Memory");
> attributes.put(SystemConfig.INITIAL_CONFIGURATION_LOCATION, 

Re: [DISCUSS/NOTICE] Renaming default git repo branches to "main"

[Oleksandr Rudyy]

Hi Robbie,
Thanks for branch removal.
My apologies, I have not checked the state of the repo before the commit.

Kind Regards,
Alex

On Wed, 31 Mar 2021 at 10:31, Robbie Gemmell  wrote:
>
> Infra removed the protection from master for me and I have now removed
> the branch again.
>
> (The same protection remains for all the other repositories for now,
> it will be removed if actually needed).
>
> On Wed, 31 Mar 2021 at 10:21, Robbie Gemmell  wrote:
> >
> > I see that qpid-broker-j was being worked on over the precise period
> > the renames were being done, and so has unfortunately already had the
> > master branch re-created by a push.
> >
> > I've brought the main up to date with the change, but I cant delete
> > the old master branch as its protected from being rewound. I will
> > enquire with infra.
> >
> > On Wed, 31 Mar 2021 at 09:29, Robbie Gemmell  
> > wrote:
> > >
> > > The remaining repositories have now had their default branches renamed
> > > from master to main, following the earlier test change.
> > >
> > > If you have an existing clone of a repo, you either need to re-clone
> > > it, or manually update your local repo to ensure it reflects the
> > > branch name change.
> > >
> > > For the latter these are GitHub's suggested steps:
> > > git branch -m master main
> > > git fetch origin
> > > git branch -u origin/main main
> > >
> > > (Where 'origin' is the git remote name given to the repo, update this
> > > as appropriate for your naming choice if different)
> > >
> > > Note that you will also have to do the rename in your own existing
> > > GitHub forks if you want them to align. GitHub notifies you of the
> > > change in its UI when you load your fork repo page, and directs you to
> > > the relevant space in settings (essentially go to
> > > https://github.com///settings/branches and then
> > > click the pencil to rename, type in main).
> > >
> > > As a final point, for those who update an existing local repo using
> > > the steps above, you may spot you still have a 'remote ref' pointing
> > > to origin/master (e.g if you run git branch -avv you would see an
> > > entry like: remotes/origin/HEAD -> origin/master). This is a local
> > > value that only gets set while cloning, based on the default branch of
> > > the remote repo at the time. Its mostly not important but you can
> > > update it yourself anyway. I elected to do this, by first explicitly
> > > setting the ref to origin/main and then pruning any refs for 'origin'
> > > (or again, whatever you named your repo remote) that dont actually
> > > exist on the remote repo:
> > > git remote set-head origin main
> > > git remote prune --dry-run origin
> > >
> > > (Note the latter is a --dry-run, repeat the command again without that
> > > flag if you are happy with what it said it will do, i.e it will
> > > indicate it would prune origin/master, but will also prune any other
> > > 'origin' refs you have for branches that no longer exist in the remote
> > > repo)
> > >
> > > On Tue, 16 Mar 2021 at 17:07, Robbie Gemmell  
> > > wrote:
> > > >
> > > > I was going to begin this tomorrow as noted below, however since I
> > > > sent this proposal I have now been both on the receiving end of a
> > > > GitHub-driven rename and done some of them for myself...that is, doing
> > > > the rename with their tooling as described at
> > > > https://github.com/github/renaming.
> > > >
> > > > It is a nicer process than I outlined below, with some benefits we
> > > > wouldnt get doing it the other way. As we can actually push to the ASF
> > > > GitHub 'mirrors' if jumping through appropriate hoops first, I decided
> > > > to enquire with Infra whether it might actually be possible to use the
> > > > GitHub driven approach. It isnt something they have done before, but
> > > > said they'll take a look at it, and could perhaps use us to try it
> > > > out. I have now raised
> > > > https://issues.apache.org/jira/browse/INFRA-21589 for this either way,
> > > > and I'll keep you updated with what is happening.
> > > >
> > > > On Thu, 11 Mar 2021 at 12:21, Robbie Gemmell  
> > > > wrote:
> > > > >
> > > > > Hi folks,
> > > > >
> > > > > I would like to propose renaming our git repository default branches
> > > > > from "master" to "main" in keeping with general efforts to remove
> > > > > offensive language, and also aligning with it being the default naming
> > > > > approach on new repositories in various places for some time now.
> > > > >
> > > > > Having looked into doing this my understanding is that we simply
> > > > > create the new branches ourselves, start using them, and then ask
> > > > > infra to reconfigure the repository default branch both here and at
> > > > > GitHub. After that is done, we can then remove the old branches at our
> > > > > own discretion.
> > > > >
> > > > > Various updates could be needed as part of the process. Some CI jobs
> > > > > and scripts etc could need to be updated, maybe some READMES etc,
> > > > > there could be 

Re: Addressing CVE-2020-5258 in Qpid Broker-J

[Oleksandr Rudyy]

Hi Tom,
My apologies. It is a typo. There will be no 8.1.x releases. I meant
versions 8.0.x.

Kind Regards,
Alex

On Thu, 18 Mar 2021 at 15:11, Tom Jordahl  wrote:
>
> HI Alex,
>
> You say below that the dojotoolkit will be updated in 8.0.5, but then you 
> mention upgrading to the “latest 8.1.x version”.
> Was that a typo or do you expect an 8.1.0 release to be coming soon?
>
> I was planning on upgrading from 7.1.x to 8.x and wanted to make sure I 
> picked up this fix.
>
> BTW – any caveats to upgrading from 7 to 8 that anyone is aware of?  I 
> reviewed the release notes and it doesn’t seem like any breaking changes were 
> made.
> Thanks.
> --
> Tom
>
> From: Oleksandr Rudyy 
> Reply-To: "users@qpid.apache.org" 
> Date: Sunday, March 14, 2021 at 4:22 PM
> To: "users@qpid.apache.org" 
> Subject: Re: Addressing CVE-2020-5258 in Qpid Broker-J
>
> Hi Rajashekar,
>
> Thanks for bringing this to our attention.
> I committed a change upgrading dojotoolkit to version 1.16.3 on master
> and 8.0.x branches. It will be available in version 8.0.5.
> I am not planning to release a new 7.1.x version. We released 7.1.0
> around two years ago in January 2019. A life cycle of major/minor
> versions is 2 years which includes building of maintenance releases
> with fixes for security and critical issues. The users of 7.1.x
> versions should upgrade their brokers to the latest 8.1.x version.
>
> Kind Regards,
> Alex
>
> [1] https://issues.apache.org/jira/browse/QPID-8511
>
> On Tue, 9 Mar 2021 at 18:54, rhudumula 
> mailto:rhudum...@salesforce.com.invalid>> 
> wrote:
>
> Hi Qpid team,
>
> CVE-2020-5258 is reported against dojo-toolkit and the fix is available in
> these versions - 1.14.6 and 1.16.2. The latest Qpid Broker-J versions still
> seem to be using older dojo-toolkit versions.
> Any update on when the this will be addressed? Or is it safe to just pick
> the latest dojo-toolkit version?
>
> Thanks,
> Rajashekar
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> -
> To unsubscribe, e-mail: 
> users-unsubscr...@qpid.apache.org<mailto:users-unsubscr...@qpid.apache.org>
> For additional commands, e-mail: 
> users-h...@qpid.apache.org<mailto:users-h...@qpid.apache.org>
>
>
> -
> To unsubscribe, e-mail: 
> users-unsubscr...@qpid.apache.org<mailto:users-unsubscr...@qpid.apache.org>
> For additional commands, e-mail: 
> users-h...@qpid.apache.org<mailto: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: Disable SASL in Broker-J

[Oleksandr Rudyy]

Hi Rajashekar,
If you are using certificate based authentication, then an EXTERNAL
authentication provider should work for you.
If not, I am afraid that configuring ANONYMOUS authentication provider
is your only option.
There is no switch to disable SASL authentication on the broker side.

Kind Regards,
Alex

On Thu, 18 Mar 2021 at 13:43, Rajashekar Hudumula
 wrote:
>
> Thanks Alex for the quick response.
>
> Is it possible to disable the SASL framework altogether. I do not want any
> authentication for Qpid as we have mTLS protecting the communication
> between client and server hosts.
>
> Thanks,
> Rajashekar
>
>
> On Wed, Mar 17, 2021 at 5:33 PM Oleksandr Rudyy  wrote:
>
> > Hi Rajashekar,
> > I am not sure I understood your request.
> > Are you asking to delegate authentication to an external system like
> > LDAP, Kerberos or OAUTH2 based, rather than managing user credentials
> > on the broker side?
> >
> > BTW, you can configure broker authentication using the following
> > mechanisms:
> > * external with certificate based authentication
> > * LDAP authentication
> > * Kerberos authentication
> > * OAUTH2 based authentication (there are a number of OAUTH2 based
> > authentication providers. If none of those used in your company, you
> > need to build your own auth provider)
> >
> >
> > Kind Regards,
> > Alex
> >
> > On Wed, 17 Mar 2021 at 06:01, rhudumula
> >  wrote:
> > >
> > > Hi Qpid Team,
> > >
> > > Do we have an option to turn off SASL in Broker-J?
> > > We do not want to use any authentication and ANONYMOUS auth is not an
> > option
> > > for us as FIPS blocks it.
> > >
> > > Thanks,
> > > Rajashekar
> > >
> > >
> > >
> > > --
> > > 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
> > >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
> >

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

Re: [VOTE] Release Apache Qpid JMS 0.57.0

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built client and ran tests from source bundle
* ran successfully Qpid Broker-J integration tests using staged 0.57.0
artefacts.

On Mon, 15 Mar 2021 at 17:30, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 0.57.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.57.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1216
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12349504
>
> 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-1216
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.57.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: Disable SASL in Broker-J

[Oleksandr Rudyy]

Hi Rajashekar,
I am not sure I understood your request.
Are you asking to delegate authentication to an external system like
LDAP, Kerberos or OAUTH2 based, rather than managing user credentials
on the broker side?

BTW, you can configure broker authentication using the following mechanisms:
* external with certificate based authentication
* LDAP authentication
* Kerberos authentication
* OAUTH2 based authentication (there are a number of OAUTH2 based
authentication providers. If none of those used in your company, you
need to build your own auth provider)


Kind Regards,
Alex

On Wed, 17 Mar 2021 at 06:01, rhudumula
 wrote:
>
> Hi Qpid Team,
>
> Do we have an option to turn off SASL in Broker-J?
> We do not want to use any authentication and ANONYMOUS auth is not an option
> for us as FIPS blocks it.
>
> Thanks,
> Rajashekar
>
>
>
> --
> 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
>

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

Re: Addressing CVE-2020-5258 in Qpid Broker-J

[Oleksandr Rudyy]

Hi Rajashekar,

Thanks for bringing this to our attention.
I committed a change upgrading dojotoolkit to version 1.16.3 on master
and 8.0.x branches. It will be available in version 8.0.5.
I am not planning to release a new 7.1.x version. We released 7.1.0
around two years ago in January 2019. A life cycle of major/minor
versions is 2 years which includes building of maintenance releases
with fixes for security and critical issues. The users of 7.1.x
versions should upgrade their brokers to the latest 8.1.x version.

Kind Regards,
Alex

[1] https://issues.apache.org/jira/browse/QPID-8511

On Tue, 9 Mar 2021 at 18:54, rhudumula  wrote:
>
> Hi Qpid team,
>
> CVE-2020-5258 is reported against dojo-toolkit and the fix is available in
> these versions - 1.14.6 and 1.16.2. The latest Qpid Broker-J versions still
> seem to be using older dojo-toolkit versions.
> Any update on when the this will be addressed? Or is it safe to just pick
> the latest dojo-toolkit version?
>
> Thanks,
> Rajashekar
>
>
>
> --
> 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
>

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

Re: [DISCUSS/NOTICE] Renaming default git repo branches to "main"

[Oleksandr Rudyy]

+1

On Thu, 11 Mar 2021 at 12:22, Robbie Gemmell  wrote:
>
> Hi folks,
>
> I would like to propose renaming our git repository default branches
> from "master" to "main" in keeping with general efforts to remove
> offensive language, and also aligning with it being the default naming
> approach on new repositories in various places for some time now.
>
> Having looked into doing this my understanding is that we simply
> create the new branches ourselves, start using them, and then ask
> infra to reconfigure the repository default branch both here and at
> GitHub. After that is done, we can then remove the old branches at our
> own discretion.
>
> Various updates could be needed as part of the process. Some CI jobs
> and scripts etc could need to be updated, maybe some READMES etc,
> there could be links that need updated, etc. I would take care of
> creating the branches, requesting INFRA update the repo defaults, and
> ensuring the CI builds and website are in order during/after the
> change. Committers would need to update their checkouts accordingly.
> Folks with their own CI jobs etc elsewhere may also need to make any
> updates as appropriate.
>
> Barring discussion otherwise, I would look to begin the process next
> week on Wednesday 17th.
>
> I would create branches in all our repositories and send a notice mail
> that it had been done, such that committers then make the swap over
> for pushing new work. I would then ask infra to make the repository
> changes, and proceed with updates to CI jobs etc. Perhaps adjusting
> the READMEs on master to make things more obvious for anyone looking
> at the repositories while it is still the default and/or both branches
> exist. After all is done, we can consider when/whether to remove the
> old branches.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

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

Re: Java Client failing to authenticate w/ secure broker depending on Java version

[Oleksandr Rudyy]

Hi,
I would like to suggest enabling on client ssl debug logging
(-Djavax.net.debug=ssl,handshake). Hopefully, it might shed some
lights on the issue with SSL handshake.

Kind regards,
Alex


On Tue, 23 Feb 2021 at 18:52, cluelessdev  wrote:
>
> Hi everyone,
>
> I'm experiencing a bizarre issue where a client will not properly connect to
> the Qpidd broker depending on which version of Java is being used. All of
> these versions work: 1.8u222 - 1.8u265. Starting with 1.8u272 the problem
> arises, however it is inconsistent/intermittent. I've also tested 1.u282 and
> Java 11. It does seem like there were significant updates made to the
> java.security module in 1.8u272 as the logging significantly changes in this
> version and above. I am trying to use SSL/TLS 1.2 w/ the SASL mechanism of
> EXTERNAL.
>
> The qpidd broker is being run with the following security-related options:
> --ssl-cert-password= --ssl-cert-db --ssl-port=5672
> --ssl-cert-name= --ssl-require-client-authentication
> --require-encryption --ssl-sasl-no-dict
>
> When running the qpidd broker w/ trace logging enabled, I see this with the
> versions of Java referenced above when things are working properly:
> [Network] trace Accepting connection with optional SSL wrapper.
> [Network] Accepted SSL connection.
> ...
> [Security] debug External ssf=256 and auth=
> [Security] debug = min_ssf: 0, max_ssf: 0, external_ssf: 256
> [Security] debug external auth detected and set to 
> [Security] info SASL: Mechanism list: EXTERNAL
> ...
>
> In the versions that do not work (sometimes), the broker log looks like
> this:
> [Network] trace Accepting connection with optional SSL wrapper.
> [Network] Accepted Plaintext connection.
> ...
> [System] debug Exception constructed: SASL layer required!
> [System] error SASL layer required!
>
> I noticed pouring over the Java version release notes that there was a
> backport of TLSv1.3 put into 1.8u272 and beyond, but I've done everything I
> can find to ensure my client is still using TLSv1.2 (and it is my
> understanding that TLSv1.2 is the default) such as running my client
> application with -Djdk.tls.client.protocols=TLSv1.2.
>
> I'm throwing darts at this point. Any help would be greatly appreciated.
>
>
>
> --
> 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
>

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

[Oleksandr Rudyy]

There were 3 binding +1 votes and 1 non-binding +1 community vote. The vote
has passed.

The voting thread can be found here:
https://lists.apache.org/thread.html/r48b6fbec6380705ed880d9851cb9cffb1aa4a2c5018f8402adb7%40%3Cusers.qpid.apache.org%3E

I will add the archives to the dist release repo and release the maven
staging repo shortly. The website will be updated once the artefacts
have had time to sync to the mirrors and maven central.

Kind Regards,
Alex

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

[Oleksandr Rudyy]

+1

* Verified signatures and checksums
* Built successfully from source bundle
* Ran successfully unit and integration tests using default profile and JDK8
* Started broker
* Created queue via web management console
* Published and received test messages using JMS client 0.56.0
* Verified that broker log timestamp is reported in new format

On Mon, 15 Feb 2021 at 00:02, Oleksandr Rudyy  wrote:
>
> Hi folks,
>
> I built release artefacts for Qpid Broker-J version 7.1.12 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/7.1.12-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1214
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12349619
>
> Kind Regards,
> Alex
>
> 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-1214
> 
> 
>
> -
> 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 8.0.4

[Oleksandr Rudyy]

+1

* Verified signatures and checksums
* Built successfully from source bundle
* Ran successfully unit and integration tests using default profile and JDK8
* Started broker
* Created queue via web management console
* Published and received test messages using JMS client 0.56.0
* Verified that broker log timestamp is reported in new format

On Mon, 15 Feb 2021 at 00:36, Oleksandr Rudyy  wrote:
>
> Hi all,
>
> I built release artefacts for Qpid Broker-J version 8.0.4 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/8.0.4-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1215
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12349598
>
> Kind Regards,
> Alex
>
> 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-1215
> 
> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
> Oleksandr Rudyy 
>
> 00:02 (31 minutes ago)
>
>
> to users

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

[VOTE] Release Qpid Broker-J 8.0.4

[Oleksandr Rudyy]

Hi all,

I built release artefacts for Qpid Broker-J version 8.0.4 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/8.0.4-rc1/

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

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

Kind Regards,
Alex

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



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

Oleksandr Rudyy 

00:02 (31 minutes ago)


to users

[VOTE] Release Qpid Broker-J 7.1.12

[Oleksandr Rudyy]

Hi folks,

I built release artefacts for Qpid Broker-J version 7.1.12 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/7.1.12-rc1/

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

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

Kind Regards,
Alex

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



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

Re: [RABBITMQ/QPID-JMS/VHOST] failed to connect to a virtual host

[Oleksandr Rudyy]

Hi Herbert,
I would like to clarify that the latest version of legacy JMS client
for AMQP 0-x is 6.4.0.

You can find more details on this old JMS client at:

http://qpid.apache.org/components/jms/amqp-0-x.html
http://qpid.apache.org/releases/qpid-jms-amqp-0-x-6.4.0/

Kind Regards,
Alex

On Fri, 12 Feb 2021 at 18:51, KOELMAN Herbert
 wrote:
>
> Ok, thank you for your help.
>
> -Message d'origine-
> De : Rob Godfrey 
> Envoyé : vendredi 12 février 2021 19:15
> À : users@qpid.apache.org
> Cc : VARSHNEY Prerna 
> Objet : Re: [RABBITMQ/QPID-JMS/VHOST] failed to connect to a virtual host
>
> So, the Qpid JMS client only speaks AMQP 1.0.
>
> In the past we released a different JMS client which spoke AMQP 0-9-1, and 
> AMQP 0-10.  I believe that last release of that is detailed here:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fqpid.apache.org%2Freleases%2Fqpid-java-6.1.7%2Findex.htmldata=04%7C01%7Cherbert.koelman%40soprasteria.com%7Cd3edf820fbf341dfaf0408d8cf821dca%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C637487505053974823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=obKDtfcQ9RmUh6jH2X0Dy9mR%2FAByONu%2Bd6ghOrQhtu0%3Dreserved=0
>
> Just to forewarn - I believe there are a few issues where RabbitMQ either 
> chose to deviate from the AMQP specification, or the Qpid client 
> implementation expects behaviour that is not defined in AMQP 0-9-1 itself.
> I know there have been people using this client against RabbitMQ in the past 
> with some success though.
>
> -- Rob
>
> Hope this helps,
> Rob
>
> On Fri, 12 Feb 2021 at 18:03, KOELMAN Herbert < 
> herbert.koel...@soprasteria.com> wrote:
>
> > Got your point.
> >
> > If I understand this well, if I force QPID to use AMQP 0-9-1 than it
> > might work. Am I assuming well :-)
> >
> > Is there a way to have QPID explicitly use AMQP 0-9-1 ? Or do I need
> > to downgrade QPID's version ?
> >
> > (By the way, your help is much appreciated ;-) ) -Message
> > d'origine- De : Rob Godfrey  Envoyé :
> > vendredi 12 février 2021 15:29 À : users@qpid.apache.org Cc : VARSHNEY
> > Prerna  Objet : Re:
> > [RABBITMQ/QPID-JMS/VHOST] failed to connect to a virtual host
> >
> > So, I think what you are seeing here is essentially a bug in the
> > RabbtMQ AMQP 1.0 plugin.  IIRC (and it's been a while) they
> > incorrectly assume an equivalence between the notion of terminus
> > durability in AMQP 1.0 and Queue durability in AMQP 0-9-1.
> >
> > The log message you see:
> >
> > 2021-02-12 14:50:48.451 [error] <0.21151.0> Channel error on
> > connection <0.21128.0> (127.0.0.1:49982 -> 127.0.0.1:5672, vhost: '/', user:
> > 'guest'), channel 2:
> > operation queue.declare caused a channel exception precondition_failed:
> > inequivalent arg 'durable' for queue 'vval' in vhost '/': received 'false'
> > but current is 'true'
> >
> > is basically from their AMQP 0-9-1 engine and talking about a
> > requirement in AMQP 0-9-1 that when asserting the existence of a queue
> > you must correctly specify whether it is durable or not.  These
> > concepts do not have an equivalent in AMQP 1.0.
> >
> >  (Terminus durability can be thought of as something like "durable
> > subscriptions" in JMS...  A non-durable terminus (which is what the
> > JMS client creates) does not imply that the queue it is linking to
> > needs to be non-durable - JMS consumers are not normally durable
> > subscriptions, so durability of the terminus is false).  We've let
> > them know about this bug before, but they didn't seem to believe that
> > fixing it was a priority at the time.
> >
> > -- Rob
> >
> > On Fri, 12 Feb 2021 at 15:05, KOELMAN Herbert <
> > herbert.koel...@soprasteria.com> wrote:
> >
> > > I have tried this broker URL setting and it's not working. Can this
> > > be a bug in version :
> > > 
> > > org.apache.qpid
> > > qpid-jms-client
> > > 0.55.0
> > > 
> > >
> > > Java QPID connexion code: JmsConnectionFactory qpidFactory = new
> > > org.apache.qpid.jms.JmsConnectionFactory("amqp://localhost:5672/amqp
> > > .v
> > > host=test");
> > >
> > > Rabbit's log:
> > > 2021-02-12 14:50:47.650 [info] <0.21096.0> accepting AMQP connection
> > > <0.21096.0> (127.0.0.1:49982 -> 127.0.0.1:5672)
> > > 2021-02-12 14:50:48.451 [error] <0.21151.0> Channel error on
> > > connection <0.21128.0> (127.0.0.1:49982 -> 127.0.0.1:5672, vhost:
> > > '/',
> > user:
> > > 'guest'), channel 2:
> > > operation queue.declare caused a channel exception precondition_failed:
> > > inequivalent arg 'durable' for queue 'vval' in vhost '/': received
> > 'false'
> > > but current is 'true'
> > > 2021-02-12 14:50:48.452 [warning] <0.21125.0> Closing session for
> > > connection <0.21096.0>:
> > > {'v1_0.error',{symbol,<<"amqp:precondition-failed">>},{utf8,<<"PRECO
> > > ND
> > > ITION_FAILED
> > > - inequivalent arg 'durable' for queue 'vval' in vhost '/': received
> > > 'false' but current is 

Re: broker j REST API getMessageContent help

[Oleksandr Rudyy]

Hi,
As per error message "Operation 'getMessageContent' can only be
performed over a secure (HTTPS) connection", you need to use https in
order to call getMessageContent. The message content can contain
sensitive private information.  In order to protect that information
from eye dropping a secure transport is required by default. You can
remove this restriction by setting attribute
allowConfidentialOperationsOnInsecureChannels to true on HTTP port.

The statistics queueDepthMessages=0 indicate that there is no message
on the queue. Thus, an operation getMessingInfo returns an empty
array: [].

Kind Regards,
Alex

On Thu, 11 Feb 2021 at 20:48, bltw15  wrote:
>
> Thank you for pointing that out Alex.
>
> I tried again with curl ( I was using Postman)
> curl --user guest -X POST -d '{"messageId":1}'
> http://localhost:8080/api/latest/queue/default/default/TempQueue344060fa-b39c-4953-87bd-b98567f61e4e/getMessageContent
> Enter host password for user 'guest':
> {
>   "errorMessage" : "Operation 'getMessageContent' can only be performed over
> a secure (HTTPS) connection"
> }
>
> can you point me to what it is I'm missing?
>
> getMessingInfo returns an empty array: []
>
> Although I think there are messages getting into the queue, but may be it's
> also blocked from getting the content for the same reason above?
> Statistics:
> availableBytes  0
> availableBytesHighWatermark 7080
> availableMessages   0
> availableMessagesHighWatermark  3
> bindingCount1
> consumerCount   1
> consumerCountWithCredit 1
> oldestMessageAge0
> persistentDequeuedBytes 0
> persistentDequeuedMessages  0
> persistentEnqueuedBytes 0
> persistentEnqueuedMessages  0
> queueDepthBytes 0
> queueDepthBytesHighWatermark9440
> queueDepthMessages  0
> queueDepthMessagesHighWatermark 4
> totalDequeuedBytes  121445600
> totalDequeuedMessages   51460
> totalEnqueuedBytes  121445600
> totalEnqueuedMessages   51460
> totalExpiredBytes   0
> totalExpiredMessages0
> totalMalformedBytes 0
> totalMalformedMessages  0
> unacknowledgedBytes 0
> unacknowledgedMessages  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
>

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

Re: broker j REST API getMessageContent help

[Oleksandr Rudyy]

Hi,

It seems that you invoked getMessageContent API using either method
POST or PUT rather than GET.

If PUT/POST is required to use, you need to specify operation
parameters in a message body. Something like

curl --user admin -X POST -d '{"messageId":1}'
http://localhost:8080/api/latest/queue/default/default/TempQueue148d546b-ee1d-4d6d-ba60-f5964f4a5aa2/getMessageContent

You can only set operation parameters as a query string with GET method.


curl --user admin -X GET
http://localhost:8080/api/latest/queue/default/default/TempQueue148d546b-ee1d-4d6d-ba60-f5964f4a5aa2/getMessageContent?messageId=1

As for message id values, you can get message ids by invoking
operation /api/latestgetMessageInfo.

Kind Regards,
Alex

On Wed, 10 Feb 2021 at 08:45, bltw15  wrote:
>
> I'm trying to retrieve message content from the queue, but can't seem to get
> it right. What is an example of using getMessageContent, and where can I
> find the messageId?
>
> http://localhost:8080/api/latest/queue/default/default/TempQueue148d546b-ee1d-4d6d-ba60-f5964f4a5aa2/getMessageContent?messageId=1
>
> return:
>   "errorMessage" : "Cannot parse body"
>
> http://localhost:8080/api/latest/queue/default/default/TempQueue148d546b-ee1d-4d6d-ba60-f5964f4a5aa2
> return:
> {
> "id": "e358e151-a8ec-48cc-a7b2-de33d67a0e0e",
> "name": "TempQueue148d546b-ee1d-4d6d-ba60-f5964f4a5aa2",
> "type": "standard",
>
> ...
>
>
>
>
> --
> 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
>

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

Re: [External] Re: Queries on Qpid setup

[Oleksandr Rudyy]

Hi Rajesh,
If required the HTTP port can be configured with a support of both TCP
and TLS transports. Though, managing Broker via plain HTTP would be
inherently insecure, as the credentials would be sent in plain sign
and could be easily intercepted.
Thus, in order to secure your Broker, it is strongly recommended to use
HTTPS for both UI and REST API calls.

Kind Regards,
Alex

On Thu, 4 Feb 2021 at 19:25, Kumar Mishra, Rajesh
 wrote:
>
> Hi Team,
>
> We have enable the TLS on HTTP port, we want to fource user to use HTTPS for 
> web, but we also calling some APIs and we don't want to use https here.
>
> WEB - https://qpid-host.com:8080
> for APIs call we want to use - http://qpid-host.com:8080/api-end-point or 
> http://localhost:8080/api-end-point
>
> Colud you please help me with the configuration.
>
>
> Thanks,
> Rajesh Mishra
> 
> From: Malyala, Kirankumar 
> Sent: Tuesday, November 17, 2020 9:29 AM
> To: Kumar Mishra, Rajesh ; Grover, Rahul 
> ; Kumari, Arti A. ; 
> Mitra, Dibbojyoti 
> Cc: Sharma, Tulsi Ram 
> Subject: FW: [External] Re: Queries on Qpid setup
>
> Hi All,
>
> FYI
>
> Regards,
> Kirankumar Malyala
>
> -Original Message-
> From: Oleksandr Rudyy 
> Sent: Tuesday, November 17, 2020 4:02 AM
> To: users@qpid.apache.org
> Subject: Re: [External] Re: Queries on Qpid setup
>
> Hi Kirankumar,
> There is a typo in cipher suite names: the GSM is used instead of GCM.
> Thus, the correct cipherSuiteWhiteList would be:
>
> "qpid.security.tls.cipherSuiteWhiteList":
> "[\"(TLS|SSL)_AES_128_GCM_SHA256\",\"(TLS|SSL)_AES_256_GCM_SHA384\",\"(TLS|SSL)_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384\"]"
>
>
> Please note that cipher suites TLS_AES_128_GCM_SHA256 and
> TLS_AES_256_GCM_SHA384 have been introduced in JDK11 for TLSv1.3. They cannot 
> be used with TLSv1.2. The only TLSv1.2 cipher suite in the list is 
> TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384.
>
> Regarding encryption of replication traffic I do not have any 
> documentation/recommendation on how to set-up  the ssh tunnels.
>
> KInd Regards,
> Alex
>
> On Mon, 16 Nov 2020 at 14:54, Malyala, Kirankumar 
>  wrote:
>
> > Hi Alex,
> >
> > 1)We are using Qpid 7.1.6 version. When we add below context in our
> > Port map getting SSL handshake error, working fine only for
> > "qpid.security.tls.protocolWhiteList": "TLSv1.2".
> >
> >  "qpid.security.tls.protocolWhiteList": "TLSv1.2",  > WORKING
> > "qpid.security.tls.cipherSuiteWhiteList":
> > "[\"(TLS|SSL)_AES_128_GSM_SHA256\",\"(TLS|SSL)_AES_256_GSM_SHA384\",\"(TLS|SSL)_ECDHE_ECDSA_WITH_AES_256_GSM_SHA384\"]"
> > > NOT WORKING
> >
> > 2)Also, please let us know which approach would be best for encrypting
> > replicas (SSH tunneling, S Tunnel or IPSec) in Qpid setup and share
> > it's configuration documentation/procedure.
> >
> > Regards,
> > Kirankumar Malyala
> >
> > -Original Message-
> > From: Oleksandr Rudyy 
> > Sent: Wednesday, November 11, 2020 12:03 AM
> > To: users@qpid.apache.org
> > Subject: Re: [External] Re: Queries on Qpid setup
> >
> > Hi Kirankumar,
> >
> > The context variable can be set on any configured object. For example,
> > you can set context variables in the attribute "context" of Broker
> > configured object or/and Port configured object.
> > The children configured objects inherit context settings from their
> > parents. Thus, the Port configured object inherits all context
> > settings from the Broker as Broker is a parent of the Port.
> > The context settings can be overridden on the child configured object
> > if required. For example, you can set the context variable
> > "qpid.security.tls.protocolAllowList" on the Broker to
> > "[\"TLSv1.2\",\"TLSv1.3\"]" to allow only TLSv1.2 and TLSv1.3 and
> > override it on the Port to  "[\\"TLSv1.3\"]" in order to restrict the
> > port connections to TLSv1.3. Another port object without overridden
> > context variable "qpid.security.tls.protocolAllowList" would inherit
> > the support of
> > TLSv1.2 and TLSv1.3 from the broker.
> >
> > As mentioned above, the context variables are kept in the attributes
> > "context" as a "map "of string keys and values. You can create your
> > initial configuration and define the context variables in the
> > "context" attribute as illustrat

Re: High Qpid Dequeue latency

[Oleksandr Rudyy]

Hi Ram,

I think that achieving a low latency (<100ms) all time could be a tricky
thing in a java broker. The full GC "stop the world" pauses can suspend
message delivery for seconds if not more. Though, the JVM GC can be tuned
to minimize a number of "stop the world" pauses and their duration which
might give you a relatively good average latency.

As for the described messaging use case, I agree that an increase of a
number of queues can cause a latency increase due to a design of the
application.  As far as I understood (please correct me if I am wrong),  20
MessageListeners are shared among N queue consumers.  If there are more
than 20 queues with messages, it could be that the prefetched messages
could be sitting waiting on the respective consumers blocked by the
MessageListeners processing 20 messages at a time. If a number of queues is
increased further, the more messages could be waiting for their turn to be
processed by the 20 MessageListeners.

The Qpid Broker-J itself can contribute to the latency increase with an
increase of queues and their consumers as it would need to handle more
connections and consumers. You are right, the Qpid Broker-J implements a
round-robin message delivery and a "fair" message distribution among
connected consumers. If you are interested in the implementation details,
you can find broker documentation at [1] describing how the consumer works.

As for improving commit time, I would like to suggest looking into newer
versions (8.0.x) of the Broker-J. There were some changes  made in
transaction code which can improve transaction performance for persistent
messages. Apart from that, I cannot think on top of my head about anything
else which might improve latency for the described architecture.

Kind Regards,
Alex

[1]
https://github.com/apache/qpid-broker-j/blob/master/doc/developer-guide/src/main/markdown/consumer-queue-interactions.md


On Mon, 11 Jan 2021 at 17:55, rammantripragada 
wrote:

> Hello Qpid Experts,
>
> We are looking for using qpid (broker-j v7.0.7 & very old client 0.16
> version ) for low dequeue latency messaging. There are app servers which
> send messages to broker and then these messages are dequeued back to the
> same set of app servers. We have created some N number of queues and for
> each queue there are consumers on each app server (will be say around 100
> app servers) which dequeue message using MessageListener (onMessage())
> interface . We created 20 listener ( jms session ) per app server and *each
> listener listens to all the queues*. We did perf run to figure out the
> dequeue latency  and we found that as the number of queues to which
> messages
> were getting enqueued concurrently were increasing, the dequeue latency was
> increasing.
>
> 
>
> The increase in dequeue latency with increase in queues seems to be due to
> the consumer dequeue pattern that we have where each listener (consumer)
> listens to all the queues. It appears that Qpid sends current available
> messages on the queues to the listeners in a round robin manner. The
> current
> way in which we register all listeners to all queues causes qpid to send
> all
> the available messages across the queues to a single consumer (listener) at
> a time in a round robin manner between all the listeners.
> E.g if we have say L1, L2& L3 as listeners and Q1, Q2, Q3 as queues. Each
> of
> the listener subscribes to all the 3 queues. Now when messages arrive on
> queue Q1, Q2, Q3,  qpid sends messages from Q1, Q2, Q3 to L1 first and next
> set of messages (max 1 from each queue as we have a prefetch limit of 1) to
> L2 and later L3 in a round robin manner.
>
> <
> http://qpid.2158936.n2.nabble.com/file/t396552/Screenshot_2020-12-09_at_3.png>
>
>
> We also found that each time jmssession.commit() was called on the listener
> to get the next message it was taking around 13ms as P95 value.  So if the
> listener L1 receives 3 messages m1, m2, m3 from Q1, Q2, Q3 then the dequeue
> latency of the second msg will be 13ms more than the first and the third
> message will be around 26ms more.  With increase in queues, more messages
> will be received by one consumer and the dequeue latency will increase.
>
> I need advice from the qpid experts for the following:
>
> 1. Is the above explanation on the behavior for increase in dequeue latency
> as the number of queues to which messages are enqueued increases is
> correct?
> 2. Is this 13ms commit time normal and can this be tuned further. Is there
> any way using MessageListener so that we can get all the messages in one
> shot rather than calling commit on the session to get the next message on
> the listener. So that we can reduce the overhead of commit time for each
> message dequeued next on the listener.
> 3. Also could you please let me know what is the best pattern we can follow
> to achieve low dequeue latency (<100ms) with higher number of queues. If we
> have one listener per 

[RESULT][VOTE] Release Qpid Broker-J 7.1.11

[Oleksandr Rudyy]

There were 3 binding +1 votes and 1 non-binding +1 community vote. The vote
has passed.

The voting thread can be found here:
https://lists.apache.org/thread.html/r0e9ae619f541e2cad2c05ae3940ee07f7603f570a55f5b437ad53190%40%3Cusers.qpid.apache.org%3E

I will add the release bundles to the dist release repo and promote the
maven artefacts from
staging repo into maven central. The website will be updated once the
artefacts
have had time to sync to the mirrors and maven central.

Kind Regards,
Alex

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

[Oleksandr Rudyy]

There were 3 binding +1 votes and 1 non-binding +1 community vote. The vote
has passed.

The voting thread can be found here:
https://lists.apache.org/thread.html/rb5ff22cecae27e5baf8b25a0f082d1a218035d106f8d73deba09310a%40%3Cusers.qpid.apache.org%3E

I will add the archives to the dist release repo and release the maven
staging repo shortly. The website will be updated once the artefacts
have had time to sync to the mirrors and maven central.

Kind Regards,
Alex

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

Re: Configuring logging in JSON

[Oleksandr Rudyy]

Hi Brian,

The supported file logger attributes can be found in the "API
Documentation". The link to API documentation is available from the top
horizontal menu in the Web Management Console.

The supported attributes are
maxFileSize number read/write
compressOldFiles boolean read/write
rollDaily boolean read/write
rollOnRestart boolean read/write
maxHistory number read/write
layout string read/write
fileName string read/write

The maxFileSize is set in MBs. The Web Management Console displays a hint
describing the size units.

Thus, a configuration for a broker file logger with a name "test", maximum
log files size 256MB, maximum number of log files 20 and compression would
look like below

{
"name" : "test",
"type" : "File",
"compressOldFiles" : true,
"fileName" : "${qpid.work_dir}/log/test.logs",
"maxFileSize" : "256",
"maxHistory" : 20,
 
}

Kind Regards,
Alex

On Thu, 7 Jan 2021 at 17:18, Brian Vollmer 
wrote:

> Hi!
> I want to configure things like max file size and add compression via the
> Broker J JSON config. Looking at the source, I tried to guess what the
> attribute names would be. Is this right?
>
>  "brokerloggers" : [ {
> "name" : "logfile",
> "type" : "File",
> "maxFileSize" : 50,
> "maxHistory" : 10,
> "compressOldFiles" : true,
> "fileName" : "/var/log/aws/collector/qpid.log",
>
> What units are used for max file size?
>
> Thank you,
> Brian Vollmer
>
>
>
> --
> 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 Qpid Broker-J 7.1.11

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran tests from source bundle
* started broker
* used web management console to create and bind queue
* ran HelloWorld examples with JMS clients for AMQP 0-x and AMQP 1.0

On Wed, 6 Jan 2021 at 00:48, Oleksandr Rudyy  wrote:

> Hi all,
>
> I built release artefacts for Qpid Broker-J version 7.1.11 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/7.1.11-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1213
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12349512
>
> Kind Regards,
> Alex
>
> 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-1213
> 
> 
> 
>
> -
> 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 8.0.3

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built broker successfully from source bundle
* ran successfully unit and integration tests using default profile and JDK8
* started broker and created queue via web management console
* published and received messages using JMS client for AMQP 1.0

On Wed, 6 Jan 2021 at 00:00, Oleksandr Rudyy  wrote:

> Hi all,
>
> I built release artefacts for Qpid Broker-J version 8.0.3 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/8.0.3-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1212
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12349276
>
> Kind Regards,
> Alex
>
> 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-1212
> 
> 
> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

[VOTE] Release Qpid Broker-J 7.1.11

[Oleksandr Rudyy]

Hi all,

I built release artefacts for Qpid Broker-J version 7.1.11 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/7.1.11-rc1/

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

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

Kind Regards,
Alex

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



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

[VOTE] Release Qpid Broker-J 8.0.3

[Oleksandr Rudyy]

Hi all,

I built release artefacts for Qpid Broker-J version 8.0.3 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/8.0.3-rc1/

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

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

Kind Regards,
Alex

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



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

Re: Does Qpid cpp client support authentication with XOAUTH2 SASL mechanism ?

[Oleksandr Rudyy]

Hi all,

I made xouth2 authentication working with the cyrus plugin
"cyrus-sasl-xoauth2".

I am not sure what exactly went wrong when I built and installed
cyrus-sasl-xoauth2 using default settings.
After re-building the cyrus-sasl-xoauth2 plugin as shown below and
registering the built libraries in /etc/ld.so.conf,
the OAUTH2 authentication started working for me. I was able to use the
Qpid cpp client for sending and receiving messages against Qpid Broker-J
using OAUTH2 authentication.

My built commands (on fedora 33)
./configure --prefix=/usr --libdir=/usr/lib64
--with-plugindir=/usr/lib64/sasl2
sed -i 's%pkglibdir = ${CYRUS_SASL_PREFIX}/lib/sasl2%pkglibdir =
${CYRUS_SASL_PREFIX}/lib64/sasl2%' Makefile
make
sudo make install

Kind Regards,
Alex

On Tue, 29 Dec 2020 at 19:32, Oleksandr Rudyy  wrote:

> Hi folks,
>
> I tried to authenticate a qpid-cpp client using XOAUTH2 SASL mechanism
> agains Qpid Broker-J but it did not work for me.
>
> I assumed that cyrus-sasl-xoauth2 (
> https://github.com/moriyoshi/cyrus-sasl-xoauth2.git) might work with
> qpid-cpp client as its SASL layer is built on top of cyrus-sals.
>
> Thus, I built cyrus-sasl-xoauth2 from sources and installed it on my
> fedora 33 into /usr/lib/sasl2.
>
> I tried to run client example hello_world using
>
> export QPID_SSL_CERT_DB=sql:./nssdb
> export LD_LIBRARY_PATH=/usr/lib/sasl2:.
> export QPID_LOG_ENABLE="trace+"
>
> ./examples/messaging/hello_world localhost:5671 'test;{create:always}'
> '{username:,password:,transport:ssl}'
>
> In the above, i specified my id and access token under  and
>  respectively.
>
> An authentication had failed for me with the following trace logs:
>
> 2020-12-29 19:24:45 [Security] debug SslConnector created for 0-10
> 2020-12-29 19:24:45 [System] info Connecting: 192.168.1.102:5671
> 2020-12-29 19:24:45 [Client] debug RECV [[192.168.1.102:desktop:5671]]:
> INIT(0-10)
> 2020-12-29 19:24:45 [Security] trace RECV [[192.168.1.102:desktop:5671]]:
> Frame[BEbe; channel=0; {ConnectionStartBody:
> server-properties={product:V2:7:str16(unknown),qpid.build:V2:7:str16(unknown),qpid.features:[{V2:17:str16(qpid.jms-selector)}]list([{V2:17:str16(qpid.jms-selector)}]),qpid.federation_tag:V2:36:str16(d00c463d-05b4-4f9b-9926-03229b53c8b9),qpid.instance_name:V2:6:str16(Broker),qpid.message_compression_supported:V2:4:str16(true),qpid.queue_lifetime_supported:V2:4:str16(true),qpid.virtualhost_properties_supported:V2:4:str16(true),version:V2:14:str16(9.0.0-SNAPSHOT)};
> mechanisms=str16{V2:7:str16(XOAUTH2)}; locales=str16{V2:5:str16(en_US)}; }]
> 2020-12-29 19:24:45 [Security] debug CyrusSasl::start(XOAUTH2)
> 2020-12-29 19:24:45 [Security] debug external SSF detected and set to 128
> 2020-12-29 19:24:45 [Security] debug min_ssf: 0, max_ssf: 256
> 2020-12-29 19:24:45 [System] debug Exception constructed: Can't
> authenticate using XOAUTH2
> 2020-12-29 19:24:45 [Client] warning Closing connection due to Can't
> authenticate using XOAUTH2
> 2020-12-29 19:24:45 [Security] trace SENT [[192.168.1.102:desktop:5671]]:
> Frame[BEbe; channel=0; {ConnectionCloseBody: reply-code=501;
> reply-text=Can't authenticate using XOAUTH2; }]
> 2020-12-29 19:24:45 [Security] trace RECV [[192.168.1.102:desktop:5671]]:
> Frame[BEbe; channel=0; {ConnectionCloseOkBody: }]
> 2020-12-29 19:24:45 [System] debug Exception constructed: Can't
> authenticate using XOAUTH2
>
> It seems that XOAUTH2 SASL authentication might not be supported, unless I
> am doing something wrong...
>
> Is there any way to make XOAUTH2 authentication working with a qpid-cpp
> client?
>
> Kind Regards,
> Alex
>
>

Does Qpid cpp client support authentication with XOAUTH2 SASL mechanism ?

[Oleksandr Rudyy]

Hi folks,

I tried to authenticate a qpid-cpp client using XOAUTH2 SASL mechanism
agains Qpid Broker-J but it did not work for me.

I assumed that cyrus-sasl-xoauth2 (
https://github.com/moriyoshi/cyrus-sasl-xoauth2.git) might work with
qpid-cpp client as its SASL layer is built on top of cyrus-sals.

Thus, I built cyrus-sasl-xoauth2 from sources and installed it on my fedora
33 into /usr/lib/sasl2.

I tried to run client example hello_world using

export QPID_SSL_CERT_DB=sql:./nssdb
export LD_LIBRARY_PATH=/usr/lib/sasl2:.
export QPID_LOG_ENABLE="trace+"

./examples/messaging/hello_world localhost:5671 'test;{create:always}'
'{username:,password:,transport:ssl}'

In the above, i specified my id and access token under  and
 respectively.

An authentication had failed for me with the following trace logs:

2020-12-29 19:24:45 [Security] debug SslConnector created for 0-10
2020-12-29 19:24:45 [System] info Connecting: 192.168.1.102:5671
2020-12-29 19:24:45 [Client] debug RECV [[192.168.1.102:desktop:5671]]:
INIT(0-10)
2020-12-29 19:24:45 [Security] trace RECV [[192.168.1.102:desktop:5671]]:
Frame[BEbe; channel=0; {ConnectionStartBody:
server-properties={product:V2:7:str16(unknown),qpid.build:V2:7:str16(unknown),qpid.features:[{V2:17:str16(qpid.jms-selector)}]list([{V2:17:str16(qpid.jms-selector)}]),qpid.federation_tag:V2:36:str16(d00c463d-05b4-4f9b-9926-03229b53c8b9),qpid.instance_name:V2:6:str16(Broker),qpid.message_compression_supported:V2:4:str16(true),qpid.queue_lifetime_supported:V2:4:str16(true),qpid.virtualhost_properties_supported:V2:4:str16(true),version:V2:14:str16(9.0.0-SNAPSHOT)};
mechanisms=str16{V2:7:str16(XOAUTH2)}; locales=str16{V2:5:str16(en_US)}; }]
2020-12-29 19:24:45 [Security] debug CyrusSasl::start(XOAUTH2)
2020-12-29 19:24:45 [Security] debug external SSF detected and set to 128
2020-12-29 19:24:45 [Security] debug min_ssf: 0, max_ssf: 256
2020-12-29 19:24:45 [System] debug Exception constructed: Can't
authenticate using XOAUTH2
2020-12-29 19:24:45 [Client] warning Closing connection due to Can't
authenticate using XOAUTH2
2020-12-29 19:24:45 [Security] trace SENT [[192.168.1.102:desktop:5671]]:
Frame[BEbe; channel=0; {ConnectionCloseBody: reply-code=501;
reply-text=Can't authenticate using XOAUTH2; }]
2020-12-29 19:24:45 [Security] trace RECV [[192.168.1.102:desktop:5671]]:
Frame[BEbe; channel=0; {ConnectionCloseOkBody: }]
2020-12-29 19:24:45 [System] debug Exception constructed: Can't
authenticate using XOAUTH2

It seems that XOAUTH2 SASL authentication might not be supported, unless I
am doing something wrong...

Is there any way to make XOAUTH2 authentication working with a qpid-cpp
client?

Kind Regards,
Alex

Re: [VOTE] Release Apache Qpid JMS 0.56.0

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran tests successfully from source bundle
* ran successfully Qpid Broker-J integration tests on master branch using
staged JMS client artifacts (mvn clean verify -DskipITs=false
-Pjava-bdb.1-0 -DskipTests)

On Mon, 14 Dec 2020 at 17:11, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.56.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.56.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1211
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12349431
>
> 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-1211
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.56.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [External] Re: Queries on Qpid setup

[Oleksandr Rudyy]

Hi Kirankumar,
If the broker port is configured with TLSv1.2, it will not accept
connection using any other TLS protocol. Thus, it is really not required to
provide any specific TLSv1.2 settings on the client side. Though, the JMS
client for AMQP 1.0 supports connection options to enable and/or disable
specific TLS protocols and cipher suites. You can use them to restrict the
TLS protocols and cipher suites to the required ones. Here are the
corresponding option descriptions from the client documentation [1]:

* transport.enabledCipherSuites The cipher suites to enable, comma
separated. No default, meaning the context default ciphers are used. Any
disabled ciphers are removed from this.
* transport.disabledCipherSuites The cipher suites to disable, comma
separated. Ciphers listed here are removed from the enabled ciphers. No
default.
* transport.enabledProtocols The protocols to enable, comma separated. No
default, meaning the context default protocols are used. Any disabled
protocols are removed from this.
* transport.disabledProtocols The protocols to disable, comma separated.
Protocols listed here are removed from the enabled protocols. Default is
"SSLv2Hello,SSLv3".

In general, you  need to configure TLS transport on a client connection URL
by simply setting protocol part of URL to amqps as in an example below

amqps://myhost.mydomain:5671

If a self-signed certificate is used, you need to provide a trustore with
all required certificates including intermediate ones.
You can utilize connection URL options transport.trustStoreLocation and
transport.trustStorePassword to set a path to the java keystore file with
the certificates and keystore password respectively. For example,

amqps://myhost.mydomain:5671?transport.trustStoreLocation=/path/to/trust-store.pkcs12=transport


An example of connection URL with enabled TLSv1.2 is provided below

amqps://myhost.mydomain:5671?transport.trustStoreLocation=/path/to/trust-store.pkcs12=transport=TLSv1.2

For more information about connection options please check client
documentation at [1].

I guess that you are asking about an example of how to configure a
connection factory spring bean using spring xml. Please, correct me if I am
wrong here.

There are multiple ways you can configure the connection factory bean in
spring framework. Please refer spring documentation [2] for more details.

Here is just an example illustrating the approach when jndi properties file
(jndi.properties) with connection factory settings is used to define the
connection URL:

You can declare bean PropertiesFactoryBean to load Qpid client JNDI
configuration from a file in classpath as below


  


Alternatively it can be done as below



Than, you can create a JNDI template bean referencing the jndiConfiguration
bean


  


The connection factory bean can be created using spring
JndiObjectFactoryBean




${qpid.connection.factory.jndi.name}



I hope the above should help you with your client set-up.

As for the BDB HA error, the  image was stripped from the email. Please
resend the stack trace of the problem.

Kind Regards,
Alex

[1]
http://qpid.apache.org/releases/qpid-jms-0.54.0/docs/index.html#ssl-transport-configuration-options
[2] https://docs.spring.io/spring-framework/docs/2.5.x/reference/jms.html


On Wed, 18 Nov 2020 at 07:48, Malyala, Kirankumar
 wrote:

> Hi Alex,
>
>
>
> 1)   Could you provide us details how we can configure TLS 1.2 for
> our JMS client in JmsConnectionFactory bean using XML file.
>
> 2)   When we try to set up BDB_HA, we are getting the following
> error.
>
>
>
>
>
> Please let me know if we are missing something.
>
>
>
> Regards,
>
> Kirankumar Malyala
>
>
>
> -Original Message-
> From: Oleksandr Rudyy 
> Sent: Tuesday, November 17, 2020 4:02 AM
> To: users@qpid.apache.org
> Subject: Re: [External] Re: Queries on Qpid setup
>
>
>
> Hi Kirankumar,
>
> There is a typo in cipher suite names: the GSM is used instead of GCM.
>
> Thus, the correct cipherSuiteWhiteList would be:
>
>
>
> "qpid.security.tls.cipherSuiteWhiteList":
>
>
> "[\"(TLS|SSL)_AES_128_GCM_SHA256\",\"(TLS|SSL)_AES_256_GCM_SHA384\",\"(TLS|SSL)_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384\"]"
>
>
>
>
>
> Please note that cipher suites TLS_AES_128_GCM_SHA256 and
>
> TLS_AES_256_GCM_SHA384 have been introduced in JDK11 for TLSv1.3. They
> cannot be used with TLSv1.2. The only TLSv1.2 cipher suite in the list is
> TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384.
>
>
>
> Regarding encryption of replication traffic I do not have any
> documentation/recommendation on how to set-up  the ssh tunnels.
>
>
>
> KInd Regards,
>
> Alex
>
>
>
> On Mon, 16 Nov 2020 at 14:54, Malyala, Kirankumar <

Re: [External] Re: Queries on Qpid setup

[Oleksandr Rudyy]

Hi Kirankumar,
There is a typo in cipher suite names: the GSM is used instead of GCM.
Thus, the correct cipherSuiteWhiteList would be:

"qpid.security.tls.cipherSuiteWhiteList":
"[\"(TLS|SSL)_AES_128_GCM_SHA256\",\"(TLS|SSL)_AES_256_GCM_SHA384\",\"(TLS|SSL)_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384\"]"


Please note that cipher suites TLS_AES_128_GCM_SHA256 and
TLS_AES_256_GCM_SHA384 have been introduced in JDK11 for TLSv1.3. They
cannot be used with TLSv1.2. The only TLSv1.2 cipher suite in the list is
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384.

Regarding encryption of replication traffic I do not have any
documentation/recommendation on how to set-up  the ssh tunnels.

KInd Regards,
Alex

On Mon, 16 Nov 2020 at 14:54, Malyala, Kirankumar
 wrote:

> Hi Alex,
>
> 1)We are using Qpid 7.1.6 version. When we add below context in our Port
> map getting SSL handshake error, working fine only for
> "qpid.security.tls.protocolWhiteList": "TLSv1.2".
>
>  "qpid.security.tls.protocolWhiteList": "TLSv1.2",  > WORKING
> "qpid.security.tls.cipherSuiteWhiteList":
> "[\"(TLS|SSL)_AES_128_GSM_SHA256\",\"(TLS|SSL)_AES_256_GSM_SHA384\",\"(TLS|SSL)_ECDHE_ECDSA_WITH_AES_256_GSM_SHA384\"]"
> > NOT WORKING
>
> 2)Also, please let us know which approach would be best for encrypting
> replicas (SSH tunneling, S Tunnel or IPSec) in Qpid setup and share it's
> configuration documentation/procedure.
>
> Regards,
> Kirankumar Malyala
>
> -Original Message-
> From: Oleksandr Rudyy 
> Sent: Wednesday, November 11, 2020 12:03 AM
> To: users@qpid.apache.org
> Subject: Re: [External] Re: Queries on Qpid setup
>
> Hi Kirankumar,
>
> The context variable can be set on any configured object. For example, you
> can set context variables in the attribute "context" of Broker configured
> object or/and Port configured object.
> The children configured objects inherit context settings from their
> parents. Thus, the Port configured object inherits all context settings
> from the Broker as Broker is a parent of the Port.
> The context settings can be overridden on the child configured object if
> required. For example, you can set the context variable
> "qpid.security.tls.protocolAllowList" on the Broker to
> "[\"TLSv1.2\",\"TLSv1.3\"]" to allow only TLSv1.2 and TLSv1.3 and override
> it on the Port to  "[\\"TLSv1.3\"]" in order to restrict the port
> connections to TLSv1.3. Another port object without overridden context
> variable "qpid.security.tls.protocolAllowList" would inherit the support of
> TLSv1.2 and TLSv1.3 from the broker.
>
> As mentioned above, the context variables are kept in the attributes
> "context" as a "map "of string keys and values. You can create your initial
> configuration and define the context variables in the "context" attribute
> as illustrated in the example below:
>
> {
>   "name" : "${broker.name}",
>   "modelVersion" : "7.1",
>   "context": {
> "qpid.security.tls.protocolAllowList": "[\"TLSv1.2\",\"TLSv1.3\"]",
> "qpid.security.tls.cipherSuiteAllowList":
>
> "[\"(TLS|SSL)_AES_128_GSM_SHA256\",\"TLS|SSL)_AES_256_GSM_SHA384\",\"TLS|SSL)_ECDHE_ECDSA_WITH_AES_256_GSM_SHA384\"]"
>   },
>
>   ...
>   "ports": [{
> "name" : "AMQP",
> "port" : "${qpid.amqp_port}",
> "context": {
>   "qpid.security.tls.protocolAllowList": "[\"TLSv1.3\"]",
> },
>...
>},
>...
>   ]
> }
>
> In the example above, the context variables
> "qpid.security.tls.protocolAllowList" and
> "qpid.security.tls.cipherSuiteAllowList" are defined on the broker level.
> The port "AMQP" has its own "context" attribute where
> "qpid.security.tls.protocolAllowList" is overridden. Thus, the port "AMQP"
> will have "qpid.security.tls.protocolAllowList" defined on the port and
> "qpid.security.tls.cipherSuiteAllowList" inherited from the Broker.
>
> I hope that the example above helps you to understand the context variable
> settings.
>
> You can update the context variables using REST API. Though, the TLS needs
> to be configured first on the HTTP port in order to use REST API.
>
>
> Kind Regards,
> Alex
>
>
>
>
> On Tue, 10 Nov 2020 at 08:47, Malyala, Kirankumar
>  wrote:
&

Re: [VOTE] Release Apache Qpid Proton-J 0.33.8

[Oleksandr Rudyy]

+1

* built and ran tests successfully from source bundle
* ran successfully Qpid Broker-J integration tests on master branch using
JMS client 0.54.0 and staged 0.33.8 proton-j artifacts


On Fri, 13 Nov 2020 at 18:30, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.33.8 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.8-rc1/
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1209
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12349374
>
> 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-1209
> 
> 
>   
>
> The dependency for proton-j would then be:
>
>   
> org.apache.qpid
> proton-j
> 0.33.8
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [External] Re: Queries on Qpid setup

[Oleksandr Rudyy]

Hi Kirankumar,

The context variable can be set on any configured object. For example, you
can set context variables in the attribute "context" of Broker configured
object or/and Port configured object.
The children configured objects inherit context settings from their
parents. Thus, the Port configured object inherits all context settings
from the Broker as Broker is a parent of the Port.
The context settings can be overridden on the child configured object if
required. For example, you can set the context variable
"qpid.security.tls.protocolAllowList" on the Broker to
"[\"TLSv1.2\",\"TLSv1.3\"]" to allow only TLSv1.2 and TLSv1.3 and override
it on the Port to  "[\\"TLSv1.3\"]" in order to restrict the port
connections to TLSv1.3. Another port object without overridden context
variable "qpid.security.tls.protocolAllowList" would inherit the support of
TLSv1.2 and TLSv1.3 from the broker.

As mentioned above, the context variables are kept in the attributes
"context" as a "map "of string keys and values. You can create your initial
configuration and define the context variables in the "context" attribute
as illustrated in the example below:

{
  "name" : "${broker.name}",
  "modelVersion" : "7.1",
  "context": {
"qpid.security.tls.protocolAllowList": "[\"TLSv1.2\",\"TLSv1.3\"]",
"qpid.security.tls.cipherSuiteAllowList":
"[\"(TLS|SSL)_AES_128_GSM_SHA256\",\"TLS|SSL)_AES_256_GSM_SHA384\",\"TLS|SSL)_ECDHE_ECDSA_WITH_AES_256_GSM_SHA384\"]"
  },

  ...
  "ports": [{
"name" : "AMQP",
"port" : "${qpid.amqp_port}",
"context": {
  "qpid.security.tls.protocolAllowList": "[\"TLSv1.3\"]",
},
   ...
   },
   ...
  ]
}

In the example above, the context variables
"qpid.security.tls.protocolAllowList" and
"qpid.security.tls.cipherSuiteAllowList" are defined on the broker level.
The port "AMQP" has its own "context" attribute where
"qpid.security.tls.protocolAllowList" is overridden. Thus, the port "AMQP"
will have "qpid.security.tls.protocolAllowList" defined on the port and
"qpid.security.tls.cipherSuiteAllowList" inherited from the Broker.

I hope that the example above helps you to understand the context variable
settings.

You can update the context variables using REST API. Though, the TLS needs
to be configured first on the HTTP port in order to use REST API.


Kind Regards,
Alex




On Tue, 10 Nov 2020 at 08:47, Malyala, Kirankumar
 wrote:

> Hi Alex,
>
> Thank you for your help. This is useful to look into the areas where we
> wanted clarity.
> I want to clear a few things from the points which you have mentioned.
>
> As you mentioned, the TLS version can set in multiple ways through context
> variable. Could you explain how we can set in
> JVM settings
> config.json
>
> Please share the code if you have it.
>
> Also, related to ssh tunnel configuration, could you share with us any
> existing references which have used ssh tunneling and master/replica
> concept. Then, it would be easier for us to mold it as per our requirement.
>
> Regards,
> Kirankumar Malyala
>
>
> -Original Message-
> From: Oleksandr Rudyy 
> Sent: Tuesday, November 10, 2020 5:24 AM
> To: users@qpid.apache.org
> Subject: Re: [External] Re: Queries on Qpid setup
>
> Hi Kirankumar,
> The AMQP and HTTP ports of Qpid Broker-J support TLS and plain TCP
> transports.
>
> In order to enable TLS on broker HTTP or/and AMQP ports Keystore configured
> object(s) needs to be configured.
> The keystore object should contain a private key and certificates
> (including intermediates if required).
>
> A number of Keystore types is supported on the broker:
> * FileKeyStore - in this type of Keystore a java keystore is used
> underneath to hold the private key and certificates
> * NonJavaKeyStore - used to configure private key and certificates
> directly in PEM or DER formats
>
> The Broker allows users to quickly create a self-signed certificate with a
> special type of Keystore called "AutoGeneratedSelfSigned" (with Oracle JDK
> or OpenJDK).
>
> The TLS protocols and TLS cipher suites can be customised (if required)
> using special context variables:
> * qpid.security.tls.protocolAllowList
> * qpid.security.tls.protocolDenyList
> * qpid.security.tls.cipherSuiteAllowList
> * qpid.security.tls.cipherSuiteDenyList
> or
> * qpid.security.tls.protocolWhiteList
> * qpid.security.tls.protocolBlackList
> * qpid.security.tls.cipherSuiteWhiteLi

Re: [External] Re: Queries on Qpid setup

[Oleksandr Rudyy]

Hi Kirankumar,
The AMQP and HTTP ports of Qpid Broker-J support TLS and plain TCP
transports.

In order to enable TLS on broker HTTP or/and AMQP ports Keystore configured
object(s) needs to be configured.
The keystore object should contain a private key and certificates
(including intermediates if required).

A number of Keystore types is supported on the broker:
* FileKeyStore - in this type of Keystore a java keystore is used
underneath to hold the private key and certificates
* NonJavaKeyStore - used to configure private key and certificates directly
in PEM or DER formats

The Broker allows users to quickly create a self-signed certificate with a
special type of Keystore called "AutoGeneratedSelfSigned" (with Oracle JDK
or OpenJDK).

The TLS protocols and TLS cipher suites can be customised (if required)
using special context variables:
* qpid.security.tls.protocolAllowList
* qpid.security.tls.protocolDenyList
* qpid.security.tls.cipherSuiteAllowList
* qpid.security.tls.cipherSuiteDenyList
or
* qpid.security.tls.protocolWhiteList
* qpid.security.tls.protocolBlackList
* qpid.security.tls.cipherSuiteWhiteList
* qpid.security.tls.cipherSuiteBlackList

Before 7.1.9 only "white/black" list terminology was supported. Starting
from version 7.1.9 the alternative names "allow/deny" lists can be used. In
version 9.0 the "allow/deny" lists completely replace "white/black" list
terminology.

For example, you can allow only TLSv1.3 with JDK11 by setting context
variable qpid.security.tls.protocolAllowList to "TLSv1.3". You can specify
the allowed or denied values using regular expressions represented as JSON
stringified lists.
For example, you can limit allowed cipher suites to only some of them by
setting qpid.security.tls.cipherSuiteAllowList to
"[\"(TLS|SSL)_AES_128_GSM_SHA256\",\"TLS|SSL)_AES_256_GSM_SHA384\",\"TLS|SSL)_ECDHE_ECDSA_WITH_AES_256_GSM_SHA384\"]".
The same applies to deny lists.

The context variable can be set in multiple ways:
* as JVM settings
* as command line arguments (for example, ./bin/qpid-server -prop
qpid.security.tls.protocolAllowList=TLSv1.3 )
* in a properties file system.properties (it needs to be in broker
classpath)
* as configured object context variables (for example, context variable set
on the Broker object using REST API)


The Qpid Broker HA  is based on Oracle BDB JE. Unfortunately the BDB JE
does not support TLS transport. The data replication is unencrypted.
Potentially, you can use SSH tunnels, but that requires configuring tunes
between each of HA nodes, as the nodes  communicate with each other. I
believe that it should be possible to configure SSH tunnels, though I
cannot give you any useful advice on how to do that.

You can download Qpid Broker distribution files from Qpid Download page at
http://qpid.apache.org/download.html .

KInd Regards,
Alex


On Fri, 6 Nov 2020 at 04:50, Malyala, Kirankumar
 wrote:

> Hi Alex,
>
> We are using broker-j (for java). As of now, we are exploring on version 7.
> Please do let us know if you want any other information.
>
> Regards,
> Kirankumar Malyala
>
> -Original Message-
> From: Oleksandr Rudyy 
> Sent: Friday, November 6, 2020 5:44 AM
> To: users@qpid.apache.org
> Subject: [External] Re: Queries on Qpid setup
>
> This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with
> links and attachments.
>
> Hi Kirankumar,
> Could you please clarify what exactly Qpid broker are you trying to use?
> There are two brokers in Qpid project: c++ broker and broker-j (for java).
>
> Are you using Qpid Broker-J?
>
> Kind regards,
> Alex
>
> On Thu, 5 Nov 2020 at 08:05, Malyala, Kirankumar
>  wrote:
>
> > Hi Team,
> >
> > We have been doing some POC on Qpid. While working on the
> > configuration, we came across multiple blockers which we have mentioned
> below.
> >
> >
> >   *   How to use a specific version of TLS encryption for Qpid if we
> > deploy on VM.
> >   *   We understood from the Qpid documentation that we have to deploy
> > broker on multiple VM's to create a group and introduce master/replica
> > nodes. Any SOP on this part ?
> >   *   How to apply SSL/TLS encryption to replicas in the group consists
> of
> > master and replica nodes using SSH tunnel/IPsec.
> >   *   How can we fetch file in Apache
> >
> > Please let us know if some one from your team can guide us on these
> points.
> >
> > Regards,
> > Kirankumar Malyala
> >
> > 
> >
> > This message is for the designated recipient only and may contain
> > privileged, proprietary, or otherwise confidential information. If you
> > have received it in error, please notify the sender immedia

Re: Queries on Qpid setup

[Oleksandr Rudyy]

Hi Kirankumar,
Could you please clarify what exactly Qpid broker are you trying to use?
There are two brokers in Qpid project: c++ broker and broker-j (for java).

Are you using Qpid Broker-J?

Kind regards,
Alex

On Thu, 5 Nov 2020 at 08:05, Malyala, Kirankumar
 wrote:

> Hi Team,
>
> We have been doing some POC on Qpid. While working on the configuration,
> we came across multiple blockers which we have mentioned below.
>
>
>   *   How to use a specific version of TLS encryption for Qpid if we
> deploy on VM.
>   *   We understood from the Qpid documentation that we have to deploy
> broker on multiple VM's to create a group and introduce master/replica
> nodes. Any SOP on this part ?
>   *   How to apply SSL/TLS encryption to replicas in the group consists of
> master and replica nodes using SSH tunnel/IPsec.
>   *   How can we fetch file in Apache
>
> Please let us know if some one from your team can guide us on these points.
>
> Regards,
> Kirankumar Malyala
>
> 
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy. Your privacy is important to us.
> Accenture uses your personal data only in compliance with data protection
> laws. For further information on how Accenture processes your personal
> data, please see our privacy statement at
> https://www.accenture.com/us-en/privacy-policy.
>
> __
>
> www.accenture.com
>

[RESULT][VOTE] Release Qpid Broker-J 8.0.2

[Oleksandr Rudyy]

There were 3 binding +1 votes and 2 non-binding +1 community votes. The vote
has passed.

The voting thread can be found here:
https://lists.apache.org/thread.html/rc05669160907c87c7e748a6357f99b7316bec383e81d1b868b82325e%40%3Cusers.qpid.apache.org%3E

I will add the release bundles to the dist release repo and promote the
maven artefacts from
staging repo into maven central. The website will be updated once the
artefacts
have had time to sync to the mirrors and maven central.

Kind Regards,
Alex

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

[Oleksandr Rudyy]

+1

* Verified signatures and checksums
* Built successfully from source bundle
* Ran successfully unit and integration tests using default profile and JDK8
* Started broker
* Created queue via web management console
* Published and received test messages using JMS client for AMQP 1.0

On Sun, 18 Oct 2020 at 22:48, Oleksandr Rudyy  wrote:

> Hi folks,
>
> I built release artefacts for Qpid Broker-J version 7.1.10 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/7.1.10-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1207
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12348861
>
> Kind Regards,
> Alex
>
> 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-1207
> 
> 
> 
>
> -
> 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 8.0.2

[Oleksandr Rudyy]

+1

* Verified signatures and checksums
* Built successfully from source bundle
* Ran successfully unit and integration tests using default profile and JDK8
* Started broker
* Created queue via web management console
* Published and received test messages using JMS client for AMQP 1.0

[VOTE] Release Qpid Broker-J 8.0.2

[Oleksandr Rudyy]

Hi folks,

I built release artefacts for Qpid Broker-J version 8.0.2 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/8.0.2-rc1/

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

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

Kind Regards,
Alex

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



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

[VOTE] Release Qpid Broker-J 7.1.10

[Oleksandr Rudyy]

Hi folks,

I built release artefacts for Qpid Broker-J version 7.1.10 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/7.1.10-rc1/

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

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

Kind Regards,
Alex

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



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

[ANNOUNCE] Apache Qpid Broker-J 8.0.1 released

[Oleksandr Rudyy]

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

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 a number of improvements and bug fixes. The release
notes can be found at:
http://qpid.apache.org/releases/qpid-broker-j-8.0.1/release-notes.html

Thanks to all involved,
Qpid Team

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

[RESULT][VOTE] Release Qpid Broker-J 8.0.1

[Oleksandr Rudyy]

There were 4 binding +1 votes and 1 non-binding +1 community vote. The vote
has passed.

The voting thread can be found here:
https://lists.apache.org/thread.html/r87755a47bc6c84a3fb67c8e910dac49e7e528fed670121794bd1ebb2%40%3Cusers.qpid.apache.org%3E

I will add the release bundles to the dist release repo and promote the
maven artefacts from
staging repo into maven central. The website will be updated once the
artefacts
have had time to sync to the mirrors and maven central.

Kind Regards,
Alex

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

[Oleksandr Rudyy]

+1

* Verified signatures and checksums
* Built successfully from source bundle
* Ran successfully unit and integration tests using default profile and JDK8
* Started broker
* Created queue via web management console
* Published test messages using JMS client for AMQP 1.0
* Scraped successfully broker metrics with locally running prometheus
server (version 2.21.0)

On Tue, 15 Sep 2020 at 01:37, Oleksandr Rudyy  wrote:

> Hi guys,
>
> I built release artefacts for Qpid Broker-J version 8.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/8.0.1-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1205/
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12347793
>
> Kind Regards,
> Alex
>
> 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-1205
> 
> 
> 
>
> -
> 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 7.1.9

[Oleksandr Rudyy]

+1

* Verified signatures and checksums
* Built successfully from source bundle
* Ran successfully unit and integration tests using default profile and JDK8
* Started broker
* Created queue via web management console
* Published test messages using JMS client for AMQP 1.0
* Scraped successfully broker metrics with locally running prometheus
server (version 2.21.0)


On Tue, 15 Sep 2020 at 00:55, Oleksandr Rudyy  wrote:

> Hi folks,
>
> I built release artefacts for Qpid Broker-J version 7.1.9 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/7.1.9-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1204
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12347794
>
> Kind Regards,
> Alex
>
> 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-1204
> 
> 
> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

[VOTE] Release Qpid Broker-J 8.0.1

[Oleksandr Rudyy]

Hi guys,

I built release artefacts for Qpid Broker-J version 8.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/8.0.1-rc1/

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

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

Kind Regards,
Alex

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



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

[VOTE] Release Qpid Broker-J 7.1.9

[Oleksandr Rudyy]

Hi folks,

I built release artefacts for Qpid Broker-J version 7.1.9 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/7.1.9-rc1/

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

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

Kind Regards,
Alex

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



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

Re: [VOTE] Release Apache Qpid JMS 0.54.0

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built successfully from sources with running all unit tests
* ran successfully Qpid Broker-J integration tests on master branch using
staged client artifacts


On Thu, 13 Aug 2020 at 14:42, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.54.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.54.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1203
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12348626
>
> 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-1203
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.54.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Apache Qpid JMS 0.53.0

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built successfully from a source bundle with running all tests
* ran successfully Qpid Broker-J integration tests on a master branch using
staged client artifacts


On Fri, 24 Jul 2020 at 17:38, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.53.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.53.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1202
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12348372
>
> 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-1202
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.53.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [NOTICE] Jenkins CI server change, manual job migrations required

[Oleksandr Rudyy]

Hi Roobie,

Thanks for the update.
I will try to migrate Qpid Broker-J jobs over next week-end.

Kind Regards,
Alex

On Fri, 24 Jul 2020 at 13:30, Robbie Gemmell 
wrote:

> The Jenkins setup at https://builds.apache.org is being replaced,
> including a server migration to a new Cloudbees hosted Jenkins primary
> at https://ci-builds.apache.org (both names will go there after the
> old setup is turned off).
>
> We must manually migrate any jobs we want to keep to the new system.
>
> The old system is being switched off on August 15th, but with worker
> nodes already gradually being migrated to the new setup now as
> appropriate to balance demand from new migrated jobs.
>
> I asked for a Qpid folder and for all committers to have access to the
> jobs, where they will live under:
> https://ci-builds.apache.org/job/Qpid/
>
> Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/
>
> I plan to migrate all the Qpid JMS and Proton-J jobs myself and I've
> done a couple as a test. I don't plan on migrating most other jobs so
> if you want to keep them then please migrate them.
>
> Full initial details are at [1], with more in other threads on
> builds@a.o [2], such as the plugin installation request thread [3] for
> any required plugins not yet installed (not sure we have any
> requirements here though).
>
> Robbie
>
> [1]
> https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E
> [2] https://lists.apache.org/list.html?bui...@apache.org
> [3]
> https://lists.apache.org/thread.html/r37c73263595b93c61c3d9b44e88a57f63edd28afa9aba3047259f4a4%40%3Cbuilds.apache.org%3E
>
> -
> 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.33.6

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built successfully from source bundle with running all tests (using JDK8)
* ran successfully Qpid Broker-J integration tests (on master branch) using
JMS client 0.49.0 together with staged 0.33.6 proton-j artifacts





On Tue, 21 Jul 2020 at 17:28, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.33.6 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.6-rc1/
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1201
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12348343
>
> 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-1201
> 
> 
>   
>
> The dependency for proton-j would then be:
>
>   
> org.apache.qpid
> proton-j
> 0.33.6
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Apache Qpid JMS 0.52.0

[Oleksandr Rudyy]

+1

* Verified signatures and checksums
* Built and ran tests from source bundle
* Ran Qpid Broker-J integration tests with staged client artefacts on a
master branch

On Wed, 3 Jun 2020 at 17:21, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.52.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.52.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1200
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12348162
>
> 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-1200
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.52.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Apache Qpid Proton-J 0.33.5

[Oleksandr Rudyy]

+1

* Verified signatures and checksums
* Built and ran test successfully from source bundle
* Ran Qpid Broker-J integration tests on master branch using proton-j
0.33.5 staged artefacts and Qpid JMS Client 0.51.0



On Fri, 29 May 2020 at 17:00, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.33.5 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.5-rc1/
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1198
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12347865
>
> 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-1198
> 
> 
>   
>
> The dependency for proton-j would then be:
>
>   
> org.apache.qpid
> proton-j
> 0.33.5
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

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

[Oleksandr Rudyy]

Hi Gordon,
Thanks for reporting the issues with tests from test suite
FailoverMethodTest.
The tests are supposed to test singleserver and roundrobin failover
methods. The way they test it is a bit weird.

The connection URL contains 2 broker entries but only one broker is
running. The second broker is not running and random free port is used as a
second broker entry. When the first broker is stopped the failover
functionality is supposed to try use 3 attempts to try establishing
connectivity with a second broker with a delay of 2 seconds between each
retry. The test tries to verify that it takes expected time for the
failover before it gives up and throw an exception.

It looks like that in you environment opening a socket to a second failover
port (with no broker listening) might took longer than expected and tests
took more than 60 seconds to run instead of expected time of 6 - 11 seconds.
I am not sure what is causing the issue. Though, it looks to me that it is
a test issue. Possibly, running a broker on a second port might help to fix
the problem. I will try to look into it tomorrow.

Kind Regards,
Alex






On Fri, 29 May 2020 at 22:43, Gordon Sim  wrote:

> On 29/05/2020 9:14 pm, Robbie Gemmell wrote:
> > You need to set a profile to enable them, e.g -Pbroker-j
>
> Thanks Robbie!
>
> Running the cpp profile, I see errors in failover tests and then the
> tests seem to just hang after that (nothing obvious to me from either
> jstack or pstack on the broker which appears idle).
>
> > [INFO] Running org.apache.qpid.systest.connection.FailoverMethodTest
> > [ERROR] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed:
> 134.204 s <<< FAILURE! - in
> org.apache.qpid.systest.connection.FailoverMethodTest
> > [ERROR]
> testFailoverSingleDelay(org.apache.qpid.systest.connection.FailoverMethodTest)
> Time elapsed: 66.088 s  <<< FAILURE!
> > java.lang.AssertionError: Failover took more than 9 seconds:(66056)
> >   at
> org.apache.qpid.systest.connection.FailoverMethodTest.testFailoverSingleDelay(FailoverMethodTest.java:165)
> >
> > [ERROR]
> testFailoverRoundRobinDelay(org.apache.qpid.systest.connection.FailoverMethodTest)
> Time elapsed: 68.083 s  <<< FAILURE!
> > java.lang.AssertionError: Failover took more than 11 seconds:(68082)
> >   at
> org.apache.qpid.systest.connection.FailoverMethodTest.testFailoverRoundRobinDelay(FailoverMethodTest.java:115)
> >
> > [INFO] Running org.apache.qpid.systest.connection.FailoverBehaviourTest
>
> with the broker-j profile I don't see any failures but I do see 23
> skipped tests (out of 163)
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

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

[Oleksandr Rudyy]

Hi Robbie,

It is a test issue. I committed a fix for the test in commit
d37a4935de01999bdf96ba2b46b3874b78901fd1 [1].

The test failure is caused by "too optimistic" retry value of 1. It seems
it took longer for the virtual host to restart and a single retry attempt
was used before the virtual host transited back into an ACTIVE state
causing the test to fail.
After changing falilove settings to more "realistic", the test is passing
for both 0-10 and 0-9 AMQP protocols.

Thus, it is not a show stopper. Please, ignore this test failure.

Kind Regards,
Alex


[1]
https://github.com/apache/qpid-jms-amqp-0-x/commit/d37a4935de01999bdf96ba2b46b3874b78901fd1

On Fri, 29 May 2020 at 13:17, Robbie Gemmell 
wrote:

> I ran some tests.
>
> The good:
> - Verified the signature and checksum files.
> - Used "mvn apache-rat:check" to check the headers in the source archive.
> - Verified LICENCE and NOTICE present in the archives.
> - Ran the Broker-J master build + mms.0-10 systests using staged
> client on JDK8 and JDK11, all fine.
>
> The bad:
> - Ran the build and 0-10 systests on JDK8 and JDK11. Saw a test
> failure in both cases:
> [ERROR]
> testAccountRotationViaConnectAttemptListenerOnFailover(org.apache.qpid.systest.connection.ConnectionFactoryTest)
>  Time elapsed: 10.238 s  <<< FAILURE!
>
>
> ConnectionFactoryTest.testAccountRotationViaConnectAttemptListenerOnFailover:294->restartBrokerAndWaitForFailover:357
>
> The same test is failing in CI on 0-10 and 0-9-1 profiles:
>
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-JMS-AMQP-0-x-Broker-J-TestMatrix/45/#showFailuresLink
>
> I havent looked into it, but I think it would be good to ascertain the
> cause of the failures before deciding whether its a blocking issue or
> not. I believe its a new test so it is a regression of sorts.
>
> Robbie
>
> On Thu, 28 May 2020 at 21:30, Oleksandr Rudyy  wrote:
> >
> > Hi,
> > I created a release candidate build for new minor version 6.4.0 of Qpid
> JMS
> > for AMQP 0-x.
> > The release introduces a number of improvements including an improvement
> > allowing to rotate credentials using extension mechanism similar to the
> one
> > available in JMS Client for AMQP 1.0.
> >
> > Please give it a test out and vote accordingly.
> >
> > The source and binary bundles can be taken from:
> > https://dist.apache.org/repos/dist/dev/qpid/jms-amqp-0-x/6.4.0-RC1
> >
> > The maven artifacts are also staged at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1197
> >
> > The JIRAs currently assigned are:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12345500
> >
> > Regards,
> > Alex
> >
> > P.S. If you want to test it out using maven, you can temporarily add this
> > to your project pom to access the staging repo:
> >
> > 
> > 
> >   staging
> >   
> > https://repository.apache.org/content/repositories/orgapacheqpid-1197
> 
> > 
> > 
> >
> > The dependency for the client itself would then be:
> >
> > 
> > org.apache.qpid
> > qpid-client
> > 6.4.0
> > 
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

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

[Oleksandr Rudyy]

+1

* built and ran tests successfully from source bundle
* verified signatures and checksums
* ran rat check successfully
* ran successfully Qpid Broker integration tests on master branch using
staged client artefacts and maven profiles java-bdb.0-10 and java-bdb.0-9


On Thu, 28 May 2020 at 21:29, Oleksandr Rudyy  wrote:

> Hi,
> I created a release candidate build for new minor version 6.4.0 of Qpid
> JMS for AMQP 0-x.
> The release introduces a number of improvements including an improvement
> allowing to rotate credentials using extension mechanism similar to the one
> available in JMS Client for AMQP 1.0.
>
> Please give it a test out and vote accordingly.
>
> The source and binary bundles can be taken from:
> https://dist.apache.org/repos/dist/dev/qpid/jms-amqp-0-x/6.4.0-RC1
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1197
>
> The JIRAs currently assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12345500
>
> Regards,
> Alex
>
> P.S. If you want to test it out using maven, you can temporarily add this
> to your project pom to access the staging repo:
>
> 
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1197
> 
> 
> 
>
> The dependency for the client itself would then be:
>
> 
> org.apache.qpid
> qpid-client
> 6.4.0
> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

[VOTE] Release Apache Qpid JMS AMQP 0-x 6.4.0

[Oleksandr Rudyy]

Hi,
I created a release candidate build for new minor version 6.4.0 of Qpid JMS
for AMQP 0-x.
The release introduces a number of improvements including an improvement
allowing to rotate credentials using extension mechanism similar to the one
available in JMS Client for AMQP 1.0.

Please give it a test out and vote accordingly.

The source and binary bundles can be taken from:
https://dist.apache.org/repos/dist/dev/qpid/jms-amqp-0-x/6.4.0-RC1

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

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12345500

Regards,
Alex

P.S. If you want to test it out using maven, you can temporarily add this
to your project pom to access the staging repo:



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



The dependency for the client itself would then be:


org.apache.qpid
qpid-client
6.4.0


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

Re: XOAUTH2 SASL Mechanism and token expiration

[Oleksandr Rudyy]

Robbie,

Thanks for pointing out into  JmsConnectionExtensions. That is exactly what
I was looking for.

Kind Regards,
Alex

On Wed, 13 May 2020 at 18:08, Robbie Gemmell 
wrote:

> The client has extensions for providing credentials at each connection
> point, e.g:
>
> https://github.com/apache/qpid-jms/blob/master/qpid-jms-client/src/main/java/org/apache/qpid/jms/JmsConnectionExtensions.java#L74-L89
>
> https://github.com/apache/qpid-jms/blob/master/qpid-jms-client/src/test/java/org/apache/qpid/jms/integration/SaslIntegrationTest.java#L590
>
> On Wed, 13 May 2020 at 17:18, Oleksandr Rudyy  wrote:
> >
> > Hi folks,
> > The current JMS clients' support for OAUTH2 based authentication has a
> > significant limitation when it is used in a production environment with
> > short-lived tokens.
> > When OAUTH2 access token expires, there is no way to update the token on
> an
> > existing connection. The user would need to generate a new token and
> create
> > a new connection. The failover feature cannot be used, as when the token
> > expires, the failover functionality would try to re-establish
> connectivity
> > with an old expired token.
> >
> > I would like to start a discussion to improve the OAUTH2 based
> > authentication support in both JMS clients for AMQP 1.0 and AMQP 0-x. I
> > think it makes sense to provide a similar OAUTH2 authentication features
> in
> > both clients.
> >
> > I created a confluence page [1] where I summarised some approaches how to
> > solve the problem.
> >
> > Essentially, the solution can involve the following changes
> >
> >- extend the JMS API with ability to update the credentials
> >- extend the JMS API with a hook to plug  OAUTH2 implementation to
> >obtain an access token directly on connection opening. That would
> allow
> >users to create their own implementations for getting OAUTH2 token
> >
> > In the confluence page I described the following possible solutions for
> the
> > issue
> >
> >1. Add CredentialSupplier hook to supply the credentials
> >2. Observe authentication failure and update credentials on
> notification
> >3. Introduce a special failover mechanism
> >4. Generate token inside of the client via special pluggable mechanism
> >
> > I am sure there could be better ways to address the issue.
> > The pooled connection factory implementations are also affected by the
> > token expiration issue.
> >
> > What would be the best way to fix a limitation of current support for
> > OAUTH2?
> >
> > Kind Regards,
> > Alex
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/qpid/XOAUTH2+SASL+Mechanism+and+token+expiration
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

XOAUTH2 SASL Mechanism and token expiration

[Oleksandr Rudyy]

Hi folks,
The current JMS clients' support for OAUTH2 based authentication has a
significant limitation when it is used in a production environment with
short-lived tokens.
When OAUTH2 access token expires, there is no way to update the token on an
existing connection. The user would need to generate a new token and create
a new connection. The failover feature cannot be used, as when the token
expires, the failover functionality would try to re-establish connectivity
with an old expired token.

I would like to start a discussion to improve the OAUTH2 based
authentication support in both JMS clients for AMQP 1.0 and AMQP 0-x. I
think it makes sense to provide a similar OAUTH2 authentication features in
both clients.

I created a confluence page [1] where I summarised some approaches how to
solve the problem.

Essentially, the solution can involve the following changes

   - extend the JMS API with ability to update the credentials
   - extend the JMS API with a hook to plug  OAUTH2 implementation to
   obtain an access token directly on connection opening. That would allow
   users to create their own implementations for getting OAUTH2 token

In the confluence page I described the following possible solutions for the
issue

   1. Add CredentialSupplier hook to supply the credentials
   2. Observe authentication failure and update credentials on notification
   3. Introduce a special failover mechanism
   4. Generate token inside of the client via special pluggable mechanism

I am sure there could be better ways to address the issue.
The pooled connection factory implementations are also affected by the
token expiration issue.

What would be the best way to fix a limitation of current support for
OAUTH2?

Kind Regards,
Alex

[1]
https://cwiki.apache.org/confluence/display/qpid/XOAUTH2+SASL+Mechanism+and+token+expiration

Re: [VOTE] Release Apache Qpid JMS 0.51.0

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran tests successfully from source bundle
* ran successfully integration tests for Qpid Broker-J on master branch
using staged artefacts


On Tue, 21 Apr 2020 at 16:01, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a 0.51.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.51.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1196
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12347785
>
> 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-1196
> 
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.51.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: Rolling logs with date-stamped name to archive?

[Oleksandr Rudyy]

Hi Kristofor,

The logging functionality in Qpid Broker-j version 6.0 and above is based
on logback framework. The log4j option is not available. Though it is not
that difficult to implement BrokerLogger and VirtualHostLogger
implementations utilizing log4j. If you decide to go with your own logging
implementation, I would suggest to upgrade broker to version 8.0 or 7.1.
These versions have a better separation of logging dependencies.
Only modules qpid-broker, qpid-broker-plugins-logging-logback and
qpid-broker-plugins-jdbc-logging-logback depend on logback. These are
optional modules.

You can build your own loggers for log4j, and run your Qpid broker using
broker-core, your own logging implementations and other required broker
plugins.

Kind Regards,
Alex



You can b


On Mon, 20 Apr 2020 at 18:02, Kristofor Horst  wrote:

> All,
>
> I configured a broker logger today for Java 6.1.4 version broker.
>
> I did not see options to customize the file name to include a timestamp
> when
> it is either created/rolled - only when the daily option is checked and
> that
> does not seem correct to my purpose, rolling at 10MB.
>
> I also wish to have the rolled files write to an alternative back up
> location that is not the local log directory, where I will later pull the
> files off host to storage. I do not believe this was a possible option with
> the UI.
>
> For example, if I write my logs to /qpid-work/log then I want my rolled
> files to go to /qpid-work/log/archives where I will then run another
> process
> that moves them off host.
>
> These are options if I were to use slf4j logging into log4j - which I am
> unsure how to enable to override the broker logging.
>
> Are these are configurable options in the standard logger? I am happy to
> use
> those.
> If these are not options in the standard logger, I would like some
> direction
> to swap to the log4j logging, which I could not find in the documentation
> for the broker.
>
> Thanks! -Kristofor
>
>
>
> --
> 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 Qpid Broker-J 7.0.9

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran tests from source bundle
* started broker
* used web management console to create and bind queue
* ran HelloWorld examples with JMS clients for AMQP 0-x and AMQP 1.0


On Fri, 3 Apr 2020 at 16:19, Oleksandr Rudyy  wrote:

> Hi folks,
>
> I built release artefacts for Qpid Broker-J version 7.0.9 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/7.0.9-rc1/
>
> The maven artifacts are also staged at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1195
>
> The new version brings a number of improvements and bug fixes.
> You can find the full list of JIRAs included into the release here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12345722
>
> Kind Regards,
> Alex
>
> 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-1195
> 
> 
> 
>
> -
> 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.33.4

[Oleksandr Rudyy]

+1

* verified signatures and checksums
* built and ran tests from source bundle
* ran Qpid Broker-J system tests on master branch using JMS 0.49/0.50 and
proton-j 0.33.4 staged artefacts


On Thu, 2 Apr 2020 at 17:53, Robbie Gemmell 
wrote:

> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.33.4 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.33.4-rc1/
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1194
>
> The JIRAs assigned are:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12345995
>
> 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-1194
> 
> 
>   
>
> The dependency for proton-j would then be:
>
>   
> org.apache.qpid
> proton-j
> 0.33.4
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

[VOTE] Release Qpid Broker-J 7.0.9

[Oleksandr Rudyy]

Hi folks,

I built release artefacts for Qpid Broker-J version 7.0.9 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/7.0.9-rc1/

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

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

Kind Regards,
Alex

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



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

Re: Poisoned message on qpid broker-j with a client that does prefetch

[Oleksandr Rudyy]

Hi Jeremy,

The message delivery counter is incremented when the receiver settles the
delivery with Rejected or Modified outcomes.
The Modified outcome can be applied when the delivery is settled without
reaching a terminal state (Modified is a default outcome for the queue
sender termini) and when the receiving link is detached with close=true.

I guess that the receiving link was closed with prefetched messages. As
result, the delivery count was incremented for all prefetched messages.

Setting prefetch to 0 can minimise the risk of message deletion on reaching
delivery count limit due to a link close with prefetched messages.

Kind regards,
Alex




On Wed, 25 Mar 2020 at 10:46, jeremy  wrote:

> Hello,
>
> We are using qpid broker-j version 7.1.6, and testing the poisoned message
> feature.
> From the doc, we saw that it is based on the maximum delivery count, and we
> were wondering how the client side prefetch will impact this. For example,
> qpid jms does a prefetch of 1000 messages by default. Also, if there is a
> dispatch router between the client and broker, it will prefetch 250
> messages
> by default.
>
> The scenario that we tested is the following:
> The cluster:
> - qpid jms client
> - 1 qpid dispatch router with autolinks
> - 1 qpid broker-j
>
> We sent 250 messages to a queue, which was configured to have max delivery
> count = 1.
> A consumer then, consumed one message, and was closed.
> We observed that all the remaining 249 messages were considered as poisoned
> and deleted.
> Even with a delivery count that is higher than 1, we still risk facing
> this,
> if we have several consumers not consuming all the messages.
>
> We were wondering if the prefetch has been taken into account. It made more
> sense if the poisoned message was based on rejected deliveries instead of
> delivery count. This way, if the client could not process the message, he
> rejects it explicitely, and upon reaching the maximum, the message will be
> deleted.
>
>
> Thanks,
> Jeremy
>
>
>
> -
> Cheers,
> Jeremy
> --
> 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: JSON file schema

[Oleksandr Rudyy]

Hi,

There is no schema document for configured object attributes.
You can find the supported attribute descriptions in broker documentation
'API documentation' available as part of Web Management Console. You need
to open Web Management Console and navigate to 'API Documentation' from top
menu: Documentation->API Documentation.

In the pop up window you can select category and find on the category page
all common and type specific attributes. Apart from attributes, you can
find there statistics and supported operations and operation parameters.

Kind Regards,
Alex



On Fri, 27 Mar 2020 at 12:37, Grossvater  wrote:

> Hello,
>
> I am working with broker-j embedded. Though I went through the
> documentation (
> http://qpid.apache.org/releases/qpid-broker-j-7.1.8/book/index.html) I am
> not able to find the exact name of supported JSON attributes. The
> documentation talks about them with descriptive names (e.g for virtual
> host, Store Path/JDBC URL & co) but not the exact JSON key.
> Where could I find this information?
>
> Thanks,
>