Re: How to enable SSL on Apache Qpid Broker-J

[Tomas Vavricka]

Hi Welly,

The image did not go through. Could you please post the log messages (in text) 
related to the invalid keystore?

To enable SSL, you need to configure the port with the following:
* Set the existing 'External' authentication provider
* Select SSL transport
* Set the existing keystore
* Optionally, set the existing truststore if mutual authentication is required

Further details can be found in the broker documentation: 
https://qpid.apache.org/releases/qpid-broker-j-9.2.0/book/Java-Broker-Management-Managing-Ports.html

Example keystore configuration JSON:

{
  "id" : "0e7f7a71-7fb4-4258-8af3-6271ab18e540",
  "name" : "keystore-amqps",
  "description" : "/path/to/keystore-amqps.p12",
  "type" : "FileKeyStore",
  "desiredState" : "ACTIVE",
  "state" : "ACTIVE",
  "durable" : true,
  "lifetimePolicy" : "PERMANENT",
  "certificateAlias" : "hostname",
  "certificateDetails" : [ ],
  "certificateExpiryCheckFrequency" : 1,
  "certificateExpiryWarnPeriod" : 30,
  "keyManagerFactoryAlgorithm" : "SunX509",
  "keyStoreType" : "pkcs12",
  "lastOpenedTime" : 1727947703448,
  "password" : "12345678",
  "path" : "/path/to/keystore-amqps.p12",
  "storeUrl" : "/path/to/keystore-amqps.p12",
  "useHostNameMatching" : true,
  "lastUpdatedBy" : "admin",
  "lastUpdatedTime" : 1727947721705,
  "createdTime" : 1727947702840
}

Regards,
Tomas

On 2024/10/02 18:17:43 Welly Hong wrote:
> Hi support team,
> 
> We are trying to enable SSL on Apache Qpid Broker-J. However, we always got 
> invalid Key Store. Please advise how to enable SSL on Apache Qpid Broker-J.
> 
> [cid:image001.png@01DB14D5.79F94350]
> 
> Thanks,
> 
> Welly
> 
> 
> Important Information
> 
> This email message (and any attachments) are intended only for the personal 
> and confidential use of the designated and intended recipient and may contain 
> privileged, proprietary, trade secret or other forms of confidential 
> information. If you are not the intended recipient of this email, you are 
> hereby notified that any review, dissemination, distribution, printing, 
> copying or other use of the information in this email (or in any attachments) 
> is strictly prohibited.  If you have received this email in error or by 
> mistake, then (i) immediately notify us that you have received this email in 
> error by replying to this email or by telephoning 212-830-5200 and (ii) 
> immediately thereafter, delete this email (and all attachments) and any 
> copies of it.  We reserve the right to monitor, review and retain the content 
> of all email communications sent and received by us.
> 
>  
> 
> Reich & Tang Deposit Networks, LLC, Reich & Tang Deposit Solutions, LLC and 
> Total Deposit Solutions, LLC (each d/b/a R&T; Deposit Solutions) and Stable 
> Custody Group II LLC (“Stable”), each a Delaware limited liability company, 
> and/or their affiliates (together, “R&T;”) provide administrative, 
> recordkeeping, agency and/or other services to banks, credit unions, trust 
> companies, wealth management firms, broker-dealers and other institutions 
> with respect to deposit placement and sweep programs, including the Demand 
> Deposit Marketplace® (DDM®) program administered by Stable and the R&T; 
> Insured Deposits (RTID®) programs, as well as other services. R&T;’s services 
> are provided subject to the terms and conditions of the written agreements 
> entered between R&T; and its client with respect to those service, and R&T; 
> provides no representations or warranties, express or implied, except as 
> expressly set forth in those written agreements. Click here 
>  for R&T;’s legal and other disclosures. R&T; is 
> not an FDIC or NCUA-insured institution. FDIC and NCUA deposit insurance only 
> covers the failure of an FDIC or NCUA-insured institution, respectively. 
> Certain conditions must be satisfied for FDIC and NCUA pass-through deposit 
> insurance coverage to apply. Click here  
> for a list of the FDIC and NCUA-insured institutions with which R&T; has a 
> business relationship for the placement of deposits under the DDM and RTID 
> programs, and into which a participating institution may place deposits 
> (subject to the program terms and conditions and any opt-outs by the 
> participating institution and/or its customers). While the DDM and RTID 
> programs provide access to an expanded level of FDIC or NCUA insurance 
> coverage on funds placed into deposit accounts at FDIC or NCUA-insured 
> institutions under the programs (up to the program limit and subject to 
> program terms and FDIC and NCUA laws and regulations, including pass-through 
> insurance coverage requirements), the DDM and RTID programs, themselves, as 
> well as R&T;’s other service offerings (including LMS, FPL and R&T; Bank 
> Monitor), are not insured or guaranteed by the FDIC or NCUA, are not 
> deposits, and may lose value in certain circumstances as described in the 
> program/service terms.  R&T; is not 

Re: [VOTE] Release Apache Qpid JMS 1.12.1

[Tomas Vavricka]

+1

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

Regards,
Tomas

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

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

Re: [VOTE] Release Apache Qpid JMS 2.6.1

[Tomas Vavricka]

+1

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

Regards,
Tomas

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

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

Re: Questions related to memstore, jvm and direct memory

[Tomas Vavricka]

Hi Vinita,

I hope these answers help you.

1)

VirtualHostNode primarily deals with the configuration of virtual hosts. JSON 
type indicates that the configuration will be stored in JSON format 
(https://qpid.apache.org/releases/qpid-broker-j-9.2.0/book/Java-Broker-Management-Managing-Virtualhost-Nodes.html#Java-Broker-Management-Managing-Virtualhost-Nodes-Types).

VirtualHost focuses on processing and storing messages. BDB type indicates that 
the messages will be stored in BDB 
(https://qpid.apache.org/releases/qpid-broker-j-9.2.0/book/Java-Broker-Management-Managing-Virtualhosts.html#Java-Broker-Management-Managing-Virtualhosts-Types).

2)

They are not tied up because it allows flexibility. For instance, one might 
want the configuration to be lightweight (e.g., JSON format) but the message 
storage to be more robust (e.g., BDB). This separation allows users to 
configure them independently based on performance, scalability, and persistence 
requirements.

4)

Choosing the right message store type depends on the expected usage. For 
example, if performance is critical but persistence is not required, the memory 
store is the best option. If persistent messages are needed, you will need to 
use a BDB, Derby, or JDBC message store.

3, 5, 6)

How the heap and direct memory are utilized depends on the structure of the 
messages being sent.

There is a simple formula that provides a rough estimate of memory usage 
(https://qpid.apache.org/releases/qpid-broker-j-9.2.0/book/Java-Broker-Runtime-Memory.html#d0e9611).

7)

The producer sends messages to a queue, and any consumer with the proper 
permissions can consume them. The producer may send messages without knowing 
which consumer will handle them, and the consumer can be from any session, not 
necessarily the one that produced the message. Consumers can receive messages 
either synchronously (waiting for the message) or asynchronously (processing 
messages as they arrive). This decoupling allows for scalability and 
flexibility, as multiple consumers can receive messages from the same queue, or 
a single consumer can process messages from multiple producers.

Regards,
Tomas

On 2024/09/13 07:14:32 Vinita Meka wrote:
> Hi Qpid users,
> 
> I'm new to Qpid and wanted to understand a few basic things apart from what
> broker book provides.
> 
> 1. What does it mean to have a JSON type virtual host node and BDB type
> virtual host?
> 2. Why aren't they tied up together by default like the name?
> 3. If I'm sending non persistent messages with no ttl and default priority
> from Qpid jms client 2.5.0 to the durable priority queues(around 12k queues
> in total), I understand all queues will be stored in the bdb memstore but
> what about the messages will they be in jvm heap memory or direct memory?
> 4. Also, is there any guidelines on how to choose the message store?
> 5. The non persistent messages when sent to the broker, where will the
> broker store these messages? Is it in jvm heap or direct memory? Or does it
> store the soft references in jvm heap and the actual message in direct
> memory?
> 6. If I bombard with a lot of messages to a queue with no consumers will
> the jvm heap oom out in case of non persistent messages? Or the direct
> memory is affected before jvm, assuming the jvm heap size is more than
> double the size of direct memory?
> 7. What does it mean to be able to produce a message from any session and
> receive sync or async using a consumer setup with any session? Why isn't it
> 1-1 like the producing session should only be able to consume? I'm asking
> because of I'm setting up sessions and producing the messages will there be
> any affinity based on the session I used to setup the consumer?
> 
> Regards,
> Vinita
> 

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

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2024/09/20 18:34:24 Robbie Gemmell wrote:
> Hi folks,
> 
> I have put together a spin for a 2.6.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
> 
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/2.6.0-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1280
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12353786
> 
> 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-1280
> 
>   
> 
> The dependency for the client itself would then be:
> 
>   
> org.apache.qpid
> qpid-jms-client
> 2.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: [VOTE] Release Apache Qpid JMS 1.12.0

[Tomas Vavricka]

+1

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

Regards,
Tomas

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

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2024/09/17 16:46:51 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M22 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-M22-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1278
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12354958
> 
> 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-1278
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M22
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M22
>    
> 
> -- 
> 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: JMS 2.x Delivery Delay - House keeping check period change

[Tomas Vavricka]

Hi Bryan,

The Virtual Host Housekeeping checks on the Broker-J server handle various 
maintenance tasks, such as checking file system space, checking the status of 
messages, processing delayed messages, purging expired ones, firing age-related 
alerts, etc..

Reducing the Virtual Host Housekeeping check period to 3 seconds will cause 
these tasks to be performed more frequently. If the broker has a large volume 
of messages in its queues, this increased frequency could lead to higher CPU 
and memory utilization. While this may not be an issue for most systems, it may 
be beneficial to monitor the broker’s performance, particularly under heavy 
(peak) load conditions.

Best regards,
Tomas

On 2024/08/14 13:37:04 Bryan Dixon wrote:
> We have an application using qpid-jms-client 2.5 and JMS 2.x Delivery Delay 
> feature.   Our application delays are fairly quick - 5 to 10 seconds.  
> Broker-J was delivering messages after around 20+ seconds instead of 5-10 
> seconds.   After enabling debug logging on the Broker-J server, I found that 
> a Housekeeping thread appeared to deliver these delayed messages.  So I 
> changed the Virtual Host House keeping check period (ms) setting to 3 seconds 
> (3000 milliseconds) and that seemed to fix the delivery of messages to be 
> more timely, and messages were delivered close to the delay of 5 to 10 
> seconds the application needed.   I wanted to make sure this change to the 
> Housekeeping setting was the appropriate change to make since 3 seconds is 
> quite a bit shorter than the default of 30 seconds.   Will this setting 
> change cause any adverse effects on the Broker-J server itself?
> 
> We are running Broker-J 9.0.0 with Java 11 on Windows Server 2019.
> 
> Bryan
> 

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

Re: QPID Broker-J 8.0.6 XSS vulnerability in path

[Tomas Vavricka]

Hi,

Thanks for reporting. I created QPID-8675 JIRA to address the issue.

https://issues.apache.org/jira/browse/QPID-8675

Regards,
Tomas

On 2024/07/08 18:02:46 Indraneel Dey wrote:
> Hello,
> 
> Our application uses QPID Broker-J and one of our users recently made us
> aware of an XSS vulnerability. The application seems to be vulnerable to a
> "reflected XSS attack" for the Management channel.
> 
> Sending a request in the form of
> "{management-endpoint}/some-script-containing-alert" results in a response
> of the form of "Unknown path 'some-script-containing-alert'. Please read
> the api docs at ...". The part of the URL, "some-script-containing-alert",
> can contain any malicious script which is reflected in the response as is,
> and can be exploited for an XSS attack.
> 
> I looked at QPID-6022 but the fix therein seems to have been insufficient.
> It seems that similar fixes are also required in following files for both
> "Unknown File" and "Unknown Path":
> 
> *
> broker-plugins/management-http/src/main/java/org/apache/qpid/server/management/plugin/servlet/RootServlet.java
> *
> broker-plugins/management-http/src/main/java/org/apache/qpid/server/management/plugin/servlet/DefinedFileServlet.java
> 
> Thank you for your attention to this matter
> 
> regards,
> Indraneel Dey
> 

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

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2024/07/15 21:44:58 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M21 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-M21-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1277
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12354452
> 
> 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-1277
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M21
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M21
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

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

[Tomas Vavricka]

+1

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

Tomas

On 2024/04/08 23:04:24 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M10 Qpid 
> proton-dotnet release,
> please give it a test out and vote accordingly.
> 
> Tests can be run using the build script in the source archive:
> 
> "./build.sh podman-test" or "./build.sh docker-test"
> 
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M10-rc1/
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12353498
> 
> Regards
> 
> -- 
> Tim Bish
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

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

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2024/03/25 18:13:45 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M20 Qpid protonJ2 
> release,
> please give it a test out and vote accordingly.
> 
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M20-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1276
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12354130
> 
> Regards
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>    
>      
>    staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1276
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M20
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M20
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

[ANNOUNCE] Apache Qpid Broker-J 9.2.0 released

[Tomas Vavricka]

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

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

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

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

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

Thanks to all involved,
Qpid Team

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

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

[Tomas Vavricka]

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

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

Regards,
Tomas

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

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

[Tomas Vavricka]

+1

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

Tomas

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

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

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

[Tomas Vavricka]

Hi all,

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

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

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

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

Regards,
Tomas

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


  
staging

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


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

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

[Tomas Vavricka]

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

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

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

[Tomas Vavricka]

Hi Alex,

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

Regards,
Tomas

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

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

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

[Tomas Vavricka]

+1

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

Tomas

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

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

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

[Tomas Vavricka]

Hi all,

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

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

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

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

Regards,
Tomas

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


  
staging

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


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

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

[Tomas Vavricka]

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

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

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

[Tomas Vavricka]

Hi all,

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

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

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

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

Regards,
Tomas

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


  
staging

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


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

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

[Tomas Vavricka]

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

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

Re: [VOTE] Release Qpid Broker-J 9.2.0

[Tomas Vavricka]

Hi Robbie,

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

Regards,
Tomas

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

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

[VOTE] Release Qpid Broker-J 9.2.0

[Tomas Vavricka]

Hi all,

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

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

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

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

Regards,
Tomas

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


  
staging

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


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

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

[Tomas Vavricka]

+1

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

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

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

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2024/01/08 17:08:51 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M19 Qpid protonJ2 
> release,
> please give it a test out and vote accordingly.
> 
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M19-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1271
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12353988
> 
> Regards
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>    
>      
>    staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1271
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M19
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M19
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

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

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2023/11/01 14:22:37 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M18 Qpid protonJ2 
> release,
> please give it a test out and vote accordingly.
> 
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M18-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1270
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12353499
> 
> Regards
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>    
>      
>    staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1270
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M18
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M18
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

Re: [VOTE] Release Apache Qpid JMS 2.5.0

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2023/10/26 16:46:27 Robbie Gemmell wrote:
> Hi folks,
> 
> I have put together a spin for a 2.5.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
> 
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/2.5.0-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1269
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12353391
> 
> Regards,
> Robbie
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1269
> 
>   
> 
> The dependency for the client itself would then be:
> 
>   
> org.apache.qpid
> qpid-jms-client
> 2.5.0
>   
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

Re: [VOTE] Release Apache Qpid JMS 1.11.0

[Tomas Vavricka]

+1

On 2023/10/30 08:41:04 Tomas Vavricka wrote:
> * Verified the signature and checksum files
> * Verified LICENCE and NOTICE files in archives
> * Verified source license headers by 'mvn apache-rat:check'
> * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 
> (11.0.20.1) and OpenJDK Java 17 (17.0.8) on Ubuntu 22.04.2
> 
> Regards,
> Tomas
> 
> On 2023/10/26 16:08:56 Robbie Gemmell wrote:
> > Hi folks,
> > 
> > I have put together a spin for a 1.11.0 Qpid JMS client release,
> > please give it a test out and vote accordingly.
> > 
> > The staged source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/jms/1.11.0-rc1/
> > 
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1268
> > 
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12353390
> > 
> > Regards,
> > Robbie
> > 
> > P.S. If you want to test it out using maven (e.g with the examples
> > src, or your own things), you can temporarily add this to your poms to
> > access the staging repo:
> > 
> >   
> > 
> >   staging
> >   
> > https://repository.apache.org/content/repositories/orgapacheqpid-1268
> > 
> >   
> > 
> > The dependency for the client itself would then be:
> > 
> >   
> > org.apache.qpid
> > qpid-jms-client
> > 1.11.0
> >   
> > 
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> > 
> > 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

Re: [VOTE] Release Apache Qpid JMS 1.11.0

[Tomas Vavricka]

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

Regards,
Tomas

On 2023/10/26 16:08:56 Robbie Gemmell wrote:
> Hi folks,
> 
> I have put together a spin for a 1.11.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
> 
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.11.0-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1268
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12353390
> 
> Regards,
> Robbie
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1268
> 
>   
> 
> The dependency for the client itself would then be:
> 
>   
> org.apache.qpid
> qpid-jms-client
> 1.11.0
>   
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

[ANNOUNCE] Apache Qpid Broker-J 9.1.0 released

[Tomas Vavricka]

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

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

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

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

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

Thanks to all involved,
Qpid Team

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

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

[Tomas Vavricka]

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

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

Regards,
Tomas

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

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

[Tomas Vavricka]

+1

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

Tomas

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

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

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

[Tomas Vavricka]

Hi all,

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

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

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

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

Regards,
Tomas

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



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



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

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

[Tomas Vavricka]

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

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

Re: [VOTE] Release Qpid Broker-J 9.1.0

[Tomas Vavricka]

Hi Alex,

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

Environment and failed test results below:

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

-Pjava-bdb.1-0

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

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

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

Daniil created Pull requests below to fix the failing tests. 

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

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

Regards,
Tomas

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

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

Re: [VOTE] Release Qpid Broker-J 9.1.0

[Tomas Vavricka]

+1

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

Tomas

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

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

[VOTE] Release Qpid Broker-J 9.1.0

[Tomas Vavricka]

Hi all,

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

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

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

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

Regards,
Tomas

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



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



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

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

[Tomas Vavricka]

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

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

Re: [VOTE] Release Qpid Broker-J 9.0.1

[Tomas Vavricka]

Hi Robbie,

thank you very much for testing and comments.

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

Regards,
Tomas

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

[VOTE] Release Qpid Broker-J 9.0.1

[Tomas Vavricka]

Hi all,

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

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

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

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

Regards,
Tomas

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



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



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

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

[Tomas Vavricka]

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

Regards,
Tomas

On 2023/06/26 16:54:28 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M16 Qpid ProtonJ2 
> release,
> please give it a test out and vote accordingly.
> 
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M16-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1261
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12353206
> 
> Regards
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>    
>      
>    staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1261
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M16
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M16
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

Re: [VOTE] Release Apache Qpid JMS 1.9.0

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2023/05/17 16:44:40 Robbie Gemmell wrote:
> Hi folks,
> 
> I have put together a spin for a 1.9.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
> 
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.9.0-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1259
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12352747
> 
> Regards,
> Robbie
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1259
> 
>   
> 
> The dependency for the client itself would then be:
> 
>   
> org.apache.qpid
> qpid-jms-client
> 1.9.0
>   
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

Re: [VOTE] Release Apache Qpid JMS 2.3.0

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2023/05/17 17:41:15 Robbie Gemmell wrote:
> I have put together a spin for a 2.3.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
> 
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/2.3.0-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1260
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524&version=12352748
> 
> Regards,
> Robbie
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1260
> 
>   
> 
> The dependency for the client itself would then be:
> 
>   
> org.apache.qpid
> qpid-jms-client
> 2.3.0
>   
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

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

[Tomas Vavricka]

+1

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

Regards,
Tomas

On 2023/05/02 17:27:36 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M15 Qpid ProtonJ2 
> release,
> please give it a test out and vote accordingly.
> 
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M15-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1258
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12353134
> 
> Regards
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>    
>      
>    staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1258
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M15
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M15
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M13 (RC1)

[Tomas Vavricka]

+1

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

On 2023/03/27 19:03:53 Timothy Bish wrote:
> Hi folks,
> 
> I have put together a release candidate for a 1.0.0-M13 Qpid ProtonJ2 
> release,
> please give it a test out and vote accordingly.
> 
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M13-rc1/
> 
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1256
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12352763
> 
> Regards
> 
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
> 
>    
>      
>    staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1256
>      
>    
> 
> The dependency for the protocol engine or the client itself would then be:
> 
>    
>      org.apache.qpid
>      protonj2
>      1.0.0-M13
>    
>    
>      org.apache.qpid
>      protonj2-client
>      1.0.0-M13
>    
> 
> -- 
> Tim Bish
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

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

[Tomas Vavricka]

+1

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

Tomas

On 2023/03/02 18:00:04 Robbie Gemmell wrote:
> Hi folks,
> 
> I have put together a spin for a Qpid Proton-J 0.34.1 release, please
> test it and vote accordingly.
> 
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.34.1-rc1/
> 
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1255
> 
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12352971
> 
> Regards,
> Robbie
> 
> P.S. If you want to test things out using maven with your own build
> you can temporarily add this to your poms to access the staging repo:
> 
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1255
> 
>   
> 
> The dependency for proton-j would then be:
> 
>   
> org.apache.qpid
> proton-j
> 0.34.1
>   
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
> 

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

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

[Tomas Vavricka]

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

Regards,
Tomas

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

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

[ANNOUNCE] Apache Qpid Broker-J 9.0.0 released

[Tomas Vavricka]

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

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

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

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

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

Thanks to all involved,
Qpid Team

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

[Tomas Vavricka]

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

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

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

Regards,
Tomas

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

[Tomas Vavricka]

+1

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

Tomas

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

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

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

[Tomas Vavricka]

Hi all,

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

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

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

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

Regards,
Tomas

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



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

Re: [VOTE] Release Qpid Broker-J 9.0.0

[Tomas Vavricka]

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

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

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

Re: [VOTE] Release Qpid Broker-J 9.0.0

[Tomas Vavricka]

Hi Robbie,

thank you very much for testing and comments.

The points mentioned should be fixed in main branch.

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

Regards,
Tomas

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

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

[Tomas Vavricka]

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