Re: Starting ActiveMQ 5.18.x preparation/update

[Jean-Baptiste Onofré]

Hi,

Those are valid points:
1. For Jakarta, I plan to change the dep and rename on dedicated
branch (5.19.x). The intention is to introduce breaking change here
(as spring or camel did).
2. Spring 6: you are right for JDK 17 (I forgot this part). Jakarta
namespace depends of the spring module in use.
spring-beans/spring-core doesn't change here. spring-jms, etc yes they
changed. I did the change on the broker first (as it uses
spring-aop/spring-beans/spring-core). But that's correct, better to
postpone to 5.19.x.
3. I'm doing a full pass on the tests, also reevaluating the profiles.
I will share some details.

I will update Jira with the releases plan.

Thanks,
Regards
JB

On Tue, Jan 10, 2023 at 12:40 PM Christopher Shannon
 wrote:
>
> JB,
>
> I was writing up a response when I saw Robbies and I have the same
> questions.
>
> What is your plan for handling the Jakarta namespace? Are you just using
> Maven to generate another module that's a copy of activemq-client?
>
> Also, you said Spring 6 is not very difficult and could be in 5.18.x but
> doesn't Spring 6 require Jakarta and JDK 17 (as Robbie pointed out)? So if
> you wanted to include support for that for 5.18.x wouldn't that also imply
> we have to have the Jakarta changes too? Also, I haven't tested with JDK 17
> but I assume the broker should be compatible with it at runtime (also
> required for Spring 6). We could also easily add a Jenkins job for JDK 17
> if we haven't already.
>
> Speaking of which, it looks like the Jenkins build has had a lot of
> failures and has been unhappy with the Advisory tests since back in
> November which is odd as it's complaining about JMX (instance already
> exists). I just re-kicked off a 5.17.x build so will see if it happens
> again but may need to fix something. Running the tests by itself locally
> work fine.
>
> On Tue, Jan 10, 2023 at 6:28 AM Robbie Gemmell 
> wrote:
>
> > Would the plan be to have these first 5.18 releases marked as e.g.
> > alphas to set people's expectations appropriately around it not yet
> > implementing most of JMS 2's new functionality, only some of the new
> > 'simplified' API? Or are the PRs going to pick up on completing [more
> > of] the impl first?
> >
> > Doesnt Spring 6 require Java 17, and so anything using it would
> > similarly? Is the thinking to change the minimum globally, or e.g just
> > for specific bits using it and then e.g have divergent requirements
> > for build (17+) and runtime (11+ or 17+ depending on what bits you
> > use)?
> >
> > Matt's reply was around having separate release branches/streams for
> > java.jms and jakarta.jms namespace support. I think that might be
> > simplest (and potentially also allowing for different JVM handling
> > between them) at this stage, I'm doing that elsewhere, though there
> > are certainly also tradeoffs to it vs alternatives. You were proposing
> > something different here, can you flesh out your original idea for
> > comparison? Had you implemented something?
> >
> > On Sun, 8 Jan 2023 at 07:19, Jean-Baptiste Onofré  wrote:
> > >
> > > Hi guys,
> > >
> > > I started to work on ActiveMQ 5.18.x major release preparation.
> > >
> > > Basically, I propose to include (as major changes, in addition of all
> > > others more "minor" changes :)):
> > > - JMS 2.x support (mostly client and first part broker)
> > > - Spring 6 update
> > > - Jakarta namespace support
> > >
> > > I should have the first PRs ready for review very soon.
> > >
> > > I would like to propose a first 5.18.0 in Feb.
> > >
> > > Thoughts ?
> > > Regards
> > > JB
> >

Starting ActiveMQ 5.18.x preparation/update

[Jean-Baptiste Onofré]

Hi guys,

I started to work on ActiveMQ 5.18.x major release preparation.

Basically, I propose to include (as major changes, in addition of all
others more "minor" changes :)):
- JMS 2.x support (mostly client and first part broker)
- Spring 6 update
- Jakarta namespace support

I should have the first PRs ready for review very soon.

I would like to propose a first 5.18.0 in Feb.

Thoughts ?
Regards
JB

Re: Regarding backward compatibility of ActiveMQ-5.17.2

[Jean-Baptiste Onofré]

Hi

- Yes, the clients (5.16.x) are compatible with 5.17.x broker
- Java 11 is required broker side, client using Java8 (with previous
AMQ 5.16.x version) for instance can use 5.17.x broker without problem
- No concrete matrix as it's backward compatible in term of protocol.
We plan a compatibility matrix for 5.18.x where we plan to support JMS
2.x preview.

Regards
JB

On Thu, Dec 8, 2022 at 8:26 AM Gupta, Kshitij
 wrote:
>
> Hello - Apache AMQ Support Team,
>
> I am using ActiveMQ – 5.16.5 and 5.19.5 client libraries to hit ActiveMQ – 
> 5.17.2 server in my Enterprise Application. Regarding this I have few below 
> questions regarding it backward compatibility –
>
>
>   1.  Will ActiveMQ Server – 5.17.2 be backward compatible to ActiveMQ – 
> 5.16.5 and 5.19.5 clients ?
>   2.  My ActiveMQ clients are running on Java8 that will hit 5.17.2 Server 
> where Java11 is the requirement, will this going to create any compatibility 
> issues ?
>   3.  Is there any backward compatibility matrix being maintained by Apache – 
> AMQ where I can check for compatibility configurations ?
>
>
> I came across these support contacts on https://activemq.apache.org/contact. 
> Please let me know if I am sending my queries on the correct channel, or else 
> please help me to direct to the correct community support channels where I 
> can raise these questions.
>
>
> Thanks
> Kshitij Gupta
> Senior Software Engineer
> Nuance India Pvt. Ltd.
>

Re: [EXTERNAL] Re: Regarding backward compatibility of ActiveMQ-5.17.2

[Jean-Baptiste Onofré]

With clients, I don't see any issue.

If you use brokers in a network of brokers (using )
with brokers forwarding message to other brokers, as it uses client
behind the hood, it should be ok.

Regards
JB

On Thu, Dec 8, 2022 at 11:20 AM Gupta, Kshitij
 wrote:
>
> Actually I am using activemq-broker-5.16.5 and activemq-client-5.15.9 at my 
> client code, with ActiveMQ – 5.17.2 server. Although I checked messages are 
> being enqueued and dequeued successfully.
>
> Do you see any issues on broker and clients to be on different versions for 
> 5.17.2 server ?
>
>
> Thanks
> Kshitij
>
>
>
> From: Jean-Baptiste Onofré 
> Date: Thursday, 8 December 2022 at 3:39 PM
> To: dev@activemq.apache.org 
> Cc: users-h...@activemq.apache.org , 
> dev-h...@activemq.apache.org , Kulkarni, Vinay 
> , Kumawat, Tapan 
> Subject: [EXTERNAL] Re: Regarding backward compatibility of ActiveMQ-5.17.2
> CAUTION: This Email is from an EXTERNAL source. Ensure you trust this sender 
> before clicking on any links or attachments.
>
> --
> Hi
>
> - Yes, the clients (5.16.x) are compatible with 5.17.x broker
> - Java 11 is required broker side, client using Java8 (with previous
> AMQ 5.16.x version) for instance can use 5.17.x broker without problem
> - No concrete matrix as it's backward compatible in term of protocol.
> We plan a compatibility matrix for 5.18.x where we plan to support JMS
> 2.x preview.
>
> Regards
> JB
>
> On Thu, Dec 8, 2022 at 8:26 AM Gupta, Kshitij
>  wrote:
> >
> > Hello - Apache AMQ Support Team,
> >
> > I am using ActiveMQ – 5.16.5 and 5.19.5 client libraries to hit ActiveMQ – 
> > 5.17.2 server in my Enterprise Application. Regarding this I have few below 
> > questions regarding it backward compatibility –
> >
> >
> >   1.  Will ActiveMQ Server – 5.17.2 be backward compatible to ActiveMQ – 
> > 5.16.5 and 5.19.5 clients ?
> >   2.  My ActiveMQ clients are running on Java8 that will hit 5.17.2 Server 
> > where Java11 is the requirement, will this going to create any 
> > compatibility issues ?
> >   3.  Is there any backward compatibility matrix being maintained by Apache 
> > – AMQ where I can check for compatibility configurations ?
> >
> >
> > I came across these support contacts on 
> > https://urldefense.com/v3/__https://activemq.apache.org/contact__;!!L7QdHkQ!hWZVxnJ8RPcVTnVLxFe8VvsmtGTP2fOJxsfUoYDflzKksDNvaidKR2mRB4SiV6BtqcBrjrDKZFfOdGs$<https://urldefense.com/v3/__https:/activemq.apache.org/contact__;!!L7QdHkQ!hWZVxnJ8RPcVTnVLxFe8VvsmtGTP2fOJxsfUoYDflzKksDNvaidKR2mRB4SiV6BtqcBrjrDKZFfOdGs$>
> >  . Please let me know if I am sending my queries on the correct channel, or 
> > else please help me to direct to the correct community support channels 
> > where I can raise these questions.
> >
> >
> > Thanks
> > Kshitij Gupta
> > Senior Software Engineer
> > Nuance India Pvt. Ltd.
> >

[ANNOUNCE] Apache ActiveMQ 5.17.3 has been released!

[Jean-Baptiste Onofré]

The Apache ActiveMQ team is pleased to announce the ActiveMQ 5.17.3 release.

This release includes several updates, fixes and improvements, especially:
 - upgrade to Spring 5.3.23
 - upgrade to Jetty  9.4.49.v20220914
 - upgrade to log4j 2.19.0
 - fix jolokia access configuration file loading on Windows platform
 - and much more !

Downloads are now available at:
https://activemq.apache.org/components/classic/download/

You can also take a look on the full Release Notes at:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352201

Enjoy!
Regards
The ActiveMQ team

[RESULT][VOTE] Apache ActiveMQ 5.17.3

[Jean-Baptiste Onofré]

Hi all,

this vote passed with the following result:

+1 (binding): Timothy Bish, Christopher Shannon, JB Onofré, Clebert Suconic
+1 (non binding): François Papon, Matt Pavlovich

I'm promoting the artifacts on Maven Central and dist.apache.org, then
I will update Jira and the website and I will send the announcement.

Thanks all for your vote!

Regards
JB

On Tue, Nov 29, 2022 at 4:31 PM Jean-Baptiste Onofré  wrote:
>
> Hi all,
>
> I submit the ActiveMQ 5.17.3 release to your vote.
>
> This release includes 32 fixes and improvements, especially:
> - Fix ActiveMQ Console on Karaf 4.4.x
> - Fix Jolokia startup on Windows platform
> - Upgrade to Spring 5.3.23
> - Upgrade to Jackson 2.14.0
> - and much more!
>
> Please take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352201
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1267/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.3/
>
> Git tag: activemq-5.17.3
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards

Re: [VOTE] Apache ActiveMQ Artemis 2.27.1 release

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Mon, Nov 28, 2022 at 10:54 PM Clebert Suconic
 wrote:
>
> I would like to propose an Apache ActiveMQ Artemis 2.27.1 release
>
>
> This is a bug fix release,
>
> I would like to highlight these 3 bug fixes:
>
> - AMQP Large Message over Bridges were broken
> - Rollback of massive transactions would take a long time to process
> - Improvements to auto-create and auto-delete queues.
>
> For a full release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352610=12315920
>
>
> Ths git commit report is here:
> https://activemq.apache.org/components/artemis/download/commit-report-2.27.1
>
>
> Source and binary distributions can be found here:
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.27.1/
>
>
> The Maven repository is here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1266
>
> In case you want to give it a try with the maven repo on examples:
> https://activemq.apache.org/components/artemis/documentation/hacking-guide/validating-releases.html
>
>
> The source tag:
> https://gitbox.apache.org/repos/asf/activemq-artemis.git;a=tag;h=refs/tags/2.27.1
>
>
> I will update the website after the vote has passed.
>
>
> [ ] +1 approve this release
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
> Here's my +1 (binding)
>
>
>
> --
> Clebert Suconic

[VOTE] Apache ActiveMQ 5.17.3

[Jean-Baptiste Onofré]

Hi all,

I submit the ActiveMQ 5.17.3 release to your vote.

This release includes 32 fixes and improvements, especially:
- Fix ActiveMQ Console on Karaf 4.4.x
- Fix Jolokia startup on Windows platform
- Upgrade to Spring 5.3.23
- Upgrade to Jackson 2.14.0
- and much more!

Please take a look on the Release Notes for details:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352201

Maven Staging Repository:
https://repository.apache.org/content/repositories/orgapacheactivemq-1267/

Dist Staging Repository:
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.3/

Git tag: activemq-5.17.3

Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks !
Regards

ActiveMQ 5.17.3 on vote today

[Jean-Baptiste Onofré]

Hi guys

We just have one pending Jira for 5.17.3 release.
I gonna fix that today (windows platform specific issue).

I plan to submit 5.17.3 release to vote tonight my time.

Regards
JB

Re: [VOTE] Apache ActiveMQ 5.17.3

[Jean-Baptiste Onofré]

+1 (binding)

Casting my own vote ;)

Regards
JB

On Tue, Nov 29, 2022 at 4:31 PM Jean-Baptiste Onofré  wrote:
>
> Hi all,
>
> I submit the ActiveMQ 5.17.3 release to your vote.
>
> This release includes 32 fixes and improvements, especially:
> - Fix ActiveMQ Console on Karaf 4.4.x
> - Fix Jolokia startup on Windows platform
> - Upgrade to Spring 5.3.23
> - Upgrade to Jackson 2.14.0
> - and much more!
>
> Please take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352201
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1267/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.3/
>
> Git tag: activemq-5.17.3
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards

Re: ASF Board Report

[Jean-Baptiste Onofré]

Hi Bruce,

I think replying to a "call for report" email is OK.

Regards
JB

On Tue, Jan 17, 2023 at 5:27 PM Bruce Snyder  wrote:
>
> I just realized that we were notified about our board report too late to
> even submit the report as the meeting is scheduled to take place tomorrow.
> So, let's plan on submitting it for next month's ASF board meeting.
>
> How do we want to go about gathering the board report contributions for
> this and future reports? GitHub? Responses to this message?
>
> Bruce
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E http://bsnyder.org/ 

Re: [VOTE] Apache ActiveMQ Artemis 2.27.0

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

Le mer. 9 nov. 2022 à 03:33, Justin Bertram  a écrit :

> I would like to propose an Apache ActiveMQ Artemis 2.27.0 release.
>
> New and noteworthy items in 2.27.0:
>
>  - Fix for CVE-2022-42889 (Apache Commons Text vulnerability)
>  - Logging implementation moved to Apache Log4j 2 (internally using SLF4J)
>  - New upgrade command to help users migrate from previous versions
>
> The release notes can be found here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920=12352246
>
> Ths git commit report is here:
>
> https://activemq.apache.org/components/artemis/download/commit-report-2.27.0
>
> Source and binary distributions can be found here:
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.27.0/
>
> The Maven repository is here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1265
>
> In case you want to give it a try with the maven repo on examples:
>
> https://activemq.apache.org/components/artemis/documentation/hacking-guide/validating-releases.html
>
> The source tag:
>
> https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;a=tag;h=refs/tags/2.27.0
>
> I will update the website after the vote has passed.
>
>
> [ ] +1 approve this release
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Here's my +1
>
>
> Justin
>

Re: [HEADSUP] Moving forward on 5.18.0 release

[Jean-Baptiste Onofré]

Hi Matt,

Great ! Thanks ! I'm on several fixes/Jira as well.

Regards
JB

On Tue, Mar 7, 2023 at 11:07 PM Matt Pavlovich  wrote:
>
> Hi JB-
>
> Sounds good, I’ve started cleaning up JIRA and PRs. I’ll get my stuff merged 
> and sorted out here in the next 1-2 days.
>
> Thanks!
> Matt Pavlovich
>
> > On Mar 4, 2023, at 11:44 PM, Jean-Baptiste Onofré  wrote:
> >
> > Hi,
> >
> > Now 5.17.4 has been released, I propose to move forward on 5.18.0 release.
> >
> > The target is to submit this release to vote at the end of next week.
> >
> > Thanks,
> > Regards
> > JB
>

[VOTE] Apache ActiveMQ 5.18.0 release

[Jean-Baptiste Onofré]

Hi,

After several weeks of work, I'm glad to submit ActiveMQ 5.18.0 to
your vote. This release is a major milestone for ActiveMQ bringing
major changes:
- JMS 2 API support (client)
- support Jakarta namespace (client)
- a lot of dependency updates and fixes
- and much much more!

You can take a look on the Release Notes for details:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351380

Maven Staging Repository:
https://repository.apache.org/content/repositories/orgapacheactivemq-1275/

Dist Staging Repository:
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.0/

Git tag: activemq-5.18.0

Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks !
Regards
JB

Re: [VOTE] Apache ActiveMQ 5.18.0 release

[Jean-Baptiste Onofré]

I agree, let's update the JMS2 page and I will include a note on the
announcement/release notes.

Regards
JB

On Thu, Mar 23, 2023 at 3:32 PM Matt Pavlovich  wrote:
>
> Chris-
>
> Good point re Jakarta and the need to communicate specifics. I’ll work to 
> update the JMS2 page to include notes about the Jakarta support.
>
> -Matt
>
> > On Mar 23, 2023, at 8:54 AM, Christopher Shannon 
> >  wrote:
> >
> > Also for anyone who is looking at the release and is testing and isn't
> > aware on the state of the JMS 2.0 client and the new Jakarta client...It's
> > not complete and there is some info here: https://activemq.apache.org/jms2
> >
> > Currently the clients only support some of the new API methods so far so
> > not everything will work. Also if testing using the Jakarta client be aware
> > it's just a repackaging so it also doesn't support everything and it can't
> > be used in the same JVM as an embedded broker because the broker still uses
> > the old JMS apis so there would be conflicts.
> >
> > The release notes page and any other communication like on that jms2 link
> > will need to make sure to document  very carefully what exactly is and
> > isn't supported in each release in regards to the JMS 2.0 and Jakarta APIs.
> >
> > On Wed, Mar 22, 2023 at 3:47 AM Francois Papon 
> > 
> > wrote:
> >
> >> +1 (non-binding)
> >>
> >> Thanks!
> >>
> >> regards,
> >>
> >> François
> >>
> >> On 19/03/2023 18:26, Jean-Baptiste Onofré wrote:
> >>> Hi,
> >>>
> >>> After several weeks of work, I'm glad to submit ActiveMQ 5.18.0 to
> >>> your vote. This release is a major milestone for ActiveMQ bringing
> >>> major changes:
> >>> - JMS 2 API support (client)
> >>> - support Jakarta namespace (client)
> >>> - a lot of dependency updates and fixes
> >>> - and much much more!
> >>>
> >>> You can take a look on the Release Notes for details:
> >>>
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351380
> >>>
> >>> Maven Staging Repository:
> >>>
> >> https://repository.apache.org/content/repositories/orgapacheactivemq-1275/
> >>>
> >>> Dist Staging Repository:
> >>> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.0/
> >>>
> >>> Git tag: activemq-5.18.0
> >>>
> >>> Please vote to approve this release:
> >>> [ ] +1 Approve the release
> >>> [ ] -1 Don't approve the release (please provide specific comments)
> >>>
> >>> This vote will be open for at least 72 hours.
> >>>
> >>> Thanks !
> >>> Regards
> >>> JB
> >>
>

Re: [VOTE] Apache ActiveMQ 5.18.0 release

[Jean-Baptiste Onofré]

Gentle reminder, we would need an additional binding vote to have this
release vote pass.

Thanks !
Regards
JB

On Sun, Mar 19, 2023 at 6:26 PM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> After several weeks of work, I'm glad to submit ActiveMQ 5.18.0 to
> your vote. This release is a major milestone for ActiveMQ bringing
> major changes:
> - JMS 2 API support (client)
> - support Jakarta namespace (client)
> - a lot of dependency updates and fixes
> - and much much more!
>
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351380
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1275/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.0/
>
> Git tag: activemq-5.18.0
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

[RESULT][VOTE] Apache ActiveMQ 5.18.0 release

[Jean-Baptiste Onofré]

Hi everyone,

This vote passed with the following result:

+1 (binding): Christopher Shannon, JB Onofré, Timothy Bish
+1 (non binding): Jamie Goodyear, Matt Pavlovich, JL Monteiro, François Papon

I'm promoting the artifacts on Maven Central and dist.apache.org, and
update Jira.
Then, I will prepare the announcement (update website, email, ...).

Thanks all for your vote!

Regards
JB

On Sun, Mar 19, 2023 at 6:26 PM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> After several weeks of work, I'm glad to submit ActiveMQ 5.18.0 to
> your vote. This release is a major milestone for ActiveMQ bringing
> major changes:
> - JMS 2 API support (client)
> - support Jakarta namespace (client)
> - a lot of dependency updates and fixes
> - and much much more!
>
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351380
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1275/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.0/
>
> Git tag: activemq-5.18.0
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

[ANN] Apache ActiveMQ 5.18.0 has been released!

[Jean-Baptiste Onofré]

The ActiveMQ team is pleased to announce Apache ActiveMQ 5.18.0 release.

This release is an important milestone for the ActiveMQ project, providing:
- JMS 2.0 client support with both javax.jms and jakarta.jms
namespaces (see https://activemq.apache.org/jms2 for details)
- JDK11+ support
- Spring 5.3.x support
- a lot of dependency updates, including CVE fixes (xstream 1.4.20, ...)
- improvements in a lot of areas (JAAS authentication, redelivery
policy, REST API, ...)

You can find details on the Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351380

You can download ActiveMQ 5.18.0 here:
https://activemq.apache.org/components/classic/download/

Enjoy!
---
The Apache ActiveMQ team

Re: [VOTE] Apache ActiveMQ 5.18.0 release

[Jean-Baptiste Onofré]

+1 (binding)

Obviously I did a bunch of tests with standalone brokers scenarios.

Regards
JB

On Sun, Mar 19, 2023 at 6:26 PM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> After several weeks of work, I'm glad to submit ActiveMQ 5.18.0 to
> your vote. This release is a major milestone for ActiveMQ bringing
> major changes:
> - JMS 2 API support (client)
> - support Jakarta namespace (client)
> - a lot of dependency updates and fixes
> - and much much more!
>
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351380
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1275/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.0/
>
> Git tag: activemq-5.18.0
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

[RESULT][VOTE] Apache ActiveMQ 5.17.4 release

[Jean-Baptiste Onofré]

Hi,

this vote passe with the following result:

+1 (binding): Christopher Shannon, JB Onofré, Robbie Gemmell, Tim Bish
+1 (non binding): Jamie Goodyear, Matt Pavlovich, François Papon

I'm promoting the artifacts on Maven Central and dist.apache.org, I
will update Jira and the website, and I will send the announcement.

Thanks all for your vote!

Regards
JB

On Wed, Feb 22, 2023 at 9:06 AM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> I submit ActiveMQ 5.17.4 to your vote. This release includes several
> fixes, improvements and a lot of dependency updates, especially:
> - add JOLOKIA_CONF env variable in wrapper configuration
> - potential race condition in the store while creating new destinations
> - fix reentrant lock in the broker configuration runtime
> - upgrade to xstream 1.4.20
> - upgrade to Spring 5.3.25
> - and much more!
>
> You can a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352481
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1270/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.4/
>
> Git tag: activemq-5.17.4
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

[VOTE] Apache ActiveMQ 5.17.4 release

[Jean-Baptiste Onofré]

Hi,

I submit ActiveMQ 5.17.4 to your vote. This release includes several
fixes, improvements and a lot of dependency updates, especially:
- add JOLOKIA_CONF env variable in wrapper configuration
- potential race condition in the store while creating new destinations
- fix reentrant lock in the broker configuration runtime
- upgrade to xstream 1.4.20
- upgrade to Spring 5.3.25
- and much more!

You can a look on the Release Notes for details:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352481

Maven Staging Repository:
https://repository.apache.org/content/repositories/orgapacheactivemq-1270/

Dist Staging Repository:
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.4/

Git tag: activemq-5.17.4

Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks !
Regards
JB

[ANN] Apache ActiveMQ 5.17.4 has been released!

[Jean-Baptiste Onofré]

The ActiveMQ team is pleased to announce Apache ActiveMQ 5.17.4 release.

ActiveMQ 5.17.4 includes several fixes, improvements, and dependency
updates as well, especially:
- add JOLOKIA_CONF env variable in wrapper configuration
- potential race condition in the store while creating new destinations
- fix reentrant lock in the broker configuration runtime
- upgrade to xstream 1.4.20
- upgrade to Spring 5.3.25
- and much more!

You can find details on the Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352481

You can download ActiveMQ 5.17.4 here:
https://activemq.apache.org/components/classic/download/

Enjoy!

Regards
---
The Apache ActiveMQ team

[HEADSUP] Moving forward on 5.18.0 release

[Jean-Baptiste Onofré]

Hi,

Now 5.17.4 has been released, I propose to move forward on 5.18.0 release.

The target is to submit this release to vote at the end of next week.

Thanks,
Regards
JB

Re: [RESULT][VOTE] Apache ActiveMQ 5.16.6 release

[Jean-Baptiste Onofré]

Agree, I will do a new time (we already replied to few users on the
mailing list announcing that it's an last/exceptional release).

Regards
JB

On Thu, Feb 16, 2023 at 5:59 PM Robbie Gemmell  wrote:
>
> The announcement should be crystal clear on the status of 5.16.x,
> given it was already announced finished in May 2022and this time
> we should remove it from the download page promptly.
>
> On Thu, 16 Feb 2023 at 15:37, Jean-Baptiste Onofré  wrote:
> >
> > Hi everyone,
> >
> > this vote passed with the following result:
> >
> > +1 (binding): Christopher Shannon, JB Onofré, Robbie Gemmell
> > +1 (non binding): Bruce, Jean-Louis Monteiro, François Papon, Jamie
> > Goodyear, Matt Pavlovich, Murali Krishna, Cesar Hernandez
> >
> > I'm promoting the artifacts on Maven Central and dist.apache.org, then
> > I will update Jira and website, and I will do the announcement.
> >
> > Thanks all for your vote!
> >
> > FYI, ActiveMQ 5.17.4 vote will start soon (before the end of the week)!
> >
> > Regards
> > JB
> >
> > On Fri, Feb 10, 2023 at 4:56 PM Jean-Baptiste Onofré  
> > wrote:
> > >
> > > Hi guys,
> > >
> > > We receive several requests to provide a new (final) ActiveMQ 5.16.6
> > > release, including few security fixes/improvements.
> > >
> > > So, I submit ActiveMQ 5.16.6 release to your vote. This one should be
> > > the last version on the 5.16.x series, inviting our users to upgrade
> > > to at least 5.17.x (or 5.18.x that should be available soon).
> > >
> > > Please take a look on the Release Notes for details:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351793
> > >
> > > Maven Staging Repository:
> > > https://repository.apache.org/content/repositories/orgapacheactivemq-1269/
> > >
> > > Dist Staging Repository:
> > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.16.6/
> > >
> > > Git tag: activemq-5.16.6
> > >
> > > Please vote to approve this release:
> > > [ ] +1 Approve the release
> > > [ ] -1 Don't approve the release (please provide specific comments)
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Thanks !
> > > Regards
> > > JB

[RESULT][VOTE] Apache ActiveMQ 5.16.6 release

[Jean-Baptiste Onofré]

Hi everyone,

this vote passed with the following result:

+1 (binding): Christopher Shannon, JB Onofré, Robbie Gemmell
+1 (non binding): Bruce, Jean-Louis Monteiro, François Papon, Jamie
Goodyear, Matt Pavlovich, Murali Krishna, Cesar Hernandez

I'm promoting the artifacts on Maven Central and dist.apache.org, then
I will update Jira and website, and I will do the announcement.

Thanks all for your vote!

FYI, ActiveMQ 5.17.4 vote will start soon (before the end of the week)!

Regards
JB

On Fri, Feb 10, 2023 at 4:56 PM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> We receive several requests to provide a new (final) ActiveMQ 5.16.6
> release, including few security fixes/improvements.
>
> So, I submit ActiveMQ 5.16.6 release to your vote. This one should be
> the last version on the 5.16.x series, inviting our users to upgrade
> to at least 5.17.x (or 5.18.x that should be available soon).
>
> Please take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351793
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1269/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.16.6/
>
> Git tag: activemq-5.16.6
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: [VOTE] Apache ActiveMQ 5.17.4 release

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Feb 22, 2023 at 9:06 AM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> I submit ActiveMQ 5.17.4 to your vote. This release includes several
> fixes, improvements and a lot of dependency updates, especially:
> - add JOLOKIA_CONF env variable in wrapper configuration
> - potential race condition in the store while creating new destinations
> - fix reentrant lock in the broker configuration runtime
> - upgrade to xstream 1.4.20
> - upgrade to Spring 5.3.25
> - and much more!
>
> You can a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352481
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1270/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.4/
>
> Git tag: activemq-5.17.4
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

[ANN] Apache ActiveMQ 5.16.6 has been released!

[Jean-Baptiste Onofré]

The ActiveMQ team is pleased to announce Apache ActiveMQ 5.16.6 release.

NB: this should be the last release on the 5.16.x series, we strongly
invite all users to update to ActiveMQ 5.17.x series.

ActiveMQ 5.16.6 includes several fixes, improvements, and dependency
updates as well, especially:
- fixes on the LDAP authentication module
- fixes high CPU usage when closing many consumers
- a bunch of dependency upgrades

You can find details on the Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351793

You can download ActiveMQ 5.16.6 here:
https://activemq.apache.org/components/classic/download/

Enjoy!

Regards
---
The Apache ActiveMQ team

Re: [PROPOSAL] Jakarta approach for ActiveMQ 5.x broker

[Jean-Baptiste Onofré]

> >> -javax modules in 5.19.x
> >>
> >> Option 2: Add -javax modules to 5.19.x and support 2 LTS branches
> >>
> >> Thanks,
> >> Matt Pavlovich
> >>
> >>> On Apr 5, 2023, at 9:20 AM, Christopher Shannon 
> >>>  wrote:
> >>>
> >>> All fair points Robbie. I'd still like to leave the jakarta client in
> >>> 5.18.x just as it gives some compatibility for clients only even if it's
> >>> going to go away in 5.19.x.
> >>>
> >>> So how about the following:
> >>>
> >>> 5.18.x - Still javax support with just a jakarta client. This can be a 
> >>> long
> >>> term LTS, at least for bug fixes. We will probably want to backport some
> >>> features too for a while.
> >>> 5.19.x - Becomes Jakarta API only. Still support JDK 11 and by default
> >>> would still have Spring 5.3.x but will be of course compatible with Spring
> >>> 6 and Spring boot 3, etc.
> >>> 5.20.x - By this release JDK 21 LTS should be out so I say we bump to
> >>> require JDK 17 (we can bump other things like Jetty/Spring 6 at the same
> >>> time)
> >>>
> >>> We could also bump to JDK 17 for 5.19.x if it's too much of a pain to
> >>> support JDK 11 but I think it should be doable.
> >>>
> >>> In terms of which features are actually supported/implemented for the new
> >>> APIs is another discussion. Obviously each release would add more. I
> >>> haven't had time yet to look more into shared subscriptions but likely 
> >>> we'd
> >>> leverage the existing composite destination/virtual topics that exist in
> >>> the broker to support it but I'm not sure if it would be client/broker 
> >>> side
> >>> etc.
> >>>
> >>> Thoughts?
> >>>
> >>> On Wed, Apr 5, 2023 at 8:59 AM Robbie Gemmell 
> >>> wrote:
> >>>
> >>>> No extra -javax client module module. People wanting Jakarta client
> >>>> support would use 5.19.x. People wanting javax client support would
> >>>> just use 5.18.x as they would today. I'd even consider removing the
> >>>> extra 5.18.x -jakarta client module personally (could be super nice
> >>>> and add a maven relocation for it to the initial 5.19.0 release to
> >>>> point them back to the normal client module, though as its not in
> >>>> widespread use and doesnt even work yet, a need for that is unclear).
> >>>>
> >>>> I dont particularly care what version it is called. However I will say
> >>>> I dont think it would particularly be any more unusual to call it
> >>>> 5.19.x vs 5.18.x than it was with many other more impactful changes
> >>>> that have been made in 5.n -> 5.n+1 releases in the past ~15 years.
> >>>> While awkward in some ways, its actually probably a more trivial
> >>>> change in the end compared to many prior changes in that time. Folks
> >>>> that want to update their stuff to the new API make a trivial version
> >>>> number update. Folks that dont, will not. Actual implementation
> >>>> behaviours would remain the same, unlike with many 5.x bumps. Could
> >>>> jump it to 5.30.x to separate and align with supporting Jakarta
> >>>> Messaging 3 ;)
> >>>>
> >>>> On Wed, 5 Apr 2023 at 12:31, Christopher Shannon
> >>>>  wrote:
> >>>>>
> >>>>> So if 5.19.x just becomes Jakarta API (and not new modules) then I 
> >>>>> assume
> >>>>> we would just have an extra client module for javax? Basically the
> >>>> inverse
> >>>>> of 5.18.x (where we primarily use javax and have a jakarta client 
> >>>>> module)
> >>>>>
> >>>>> I guess that will be fine but it is pretty unusual to make such a large
> >>>>> breaking API change without bumping major versions. I would argue that
> >>>>> should really be a 6.0 release but everyone knows how that conversation
> >>>>> would go with versioning so I guess we are stuck on 5.19.x
> >>>>>
> >>>>> On Wed, Apr 5, 2023 at 5:17 AM Jean-Baptiste Onofré 
> >>>> wrote:
> >>>>>
> >>>>>> Hi
> >>>>>>
> >>>>>> Agree, it was basically my proposal

Re: [PROPOSAL] Jakarta approach for ActiveMQ 5.x broker

[Jean-Baptiste Onofré]

x modules would be a way to simplify managing a
> > Spring 6 + JDK 17 + javax build without a separate branch and set of
> > releases
> > >>
> > >> A table of potential combinations:
> > >>
> > >> 5.18.x - Spring 5 + JDK 11 + javax (client and broker)
> > >> 5.18.x (-jakarta client) - Spring 5 + JDK 11 + jakarta (client-only)
> > >> 5.19.x - Spring 6 + JDK 17 + jakarta (client and broker)
> > >> 5.19.x (-javax modules) - Spring 6 + JDK 17 + javax (client and broker)
> > >>
> > >>
> > >> Based on all the above, I think the discussion could be reduced to a
> > couple practical options:
> > >>
> > >> Option 1: Gap versions and support 3 (or more) LTS branches and do not
> > do  -javax modules in 5.19.x
> > >>
> > >> Option 2: Add -javax modules to 5.19.x and support 2 LTS branches
> > >>
> > >> Thanks,
> > >> Matt Pavlovich
> > >>
> > >>> On Apr 5, 2023, at 9:20 AM, Christopher Shannon <
> > christopher.l.shan...@gmail.com> wrote:
> > >>>
> > >>> All fair points Robbie. I'd still like to leave the jakarta client in
> > >>> 5.18.x just as it gives some compatibility for clients only even if
> > it's
> > >>> going to go away in 5.19.x.
> > >>>
> > >>> So how about the following:
> > >>>
> > >>> 5.18.x - Still javax support with just a jakarta client. This can be a
> > long
> > >>> term LTS, at least for bug fixes. We will probably want to backport
> > some
> > >>> features too for a while.
> > >>> 5.19.x - Becomes Jakarta API only. Still support JDK 11 and by default
> > >>> would still have Spring 5.3.x but will be of course compatible with
> > Spring
> > >>> 6 and Spring boot 3, etc.
> > >>> 5.20.x - By this release JDK 21 LTS should be out so I say we bump to
> > >>> require JDK 17 (we can bump other things like Jetty/Spring 6 at the
> > same
> > >>> time)
> > >>>
> > >>> We could also bump to JDK 17 for 5.19.x if it's too much of a pain to
> > >>> support JDK 11 but I think it should be doable.
> > >>>
> > >>> In terms of which features are actually supported/implemented for the
> > new
> > >>> APIs is another discussion. Obviously each release would add more. I
> > >>> haven't had time yet to look more into shared subscriptions but likely
> > we'd
> > >>> leverage the existing composite destination/virtual topics that exist
> > in
> > >>> the broker to support it but I'm not sure if it would be client/broker
> > side
> > >>> etc.
> > >>>
> > >>> Thoughts?
> > >>>
> > >>> On Wed, Apr 5, 2023 at 8:59 AM Robbie Gemmell <
> > robbie.gemm...@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> No extra -javax client module module. People wanting Jakarta client
> > >>>> support would use 5.19.x. People wanting javax client support would
> > >>>> just use 5.18.x as they would today. I'd even consider removing the
> > >>>> extra 5.18.x -jakarta client module personally (could be super nice
> > >>>> and add a maven relocation for it to the initial 5.19.0 release to
> > >>>> point them back to the normal client module, though as its not in
> > >>>> widespread use and doesnt even work yet, a need for that is unclear).
> > >>>>
> > >>>> I dont particularly care what version it is called. However I will say
> > >>>> I dont think it would particularly be any more unusual to call it
> > >>>> 5.19.x vs 5.18.x than it was with many other more impactful changes
> > >>>> that have been made in 5.n -> 5.n+1 releases in the past ~15 years.
> > >>>> While awkward in some ways, its actually probably a more trivial
> > >>>> change in the end compared to many prior changes in that time. Folks
> > >>>> that want to update their stuff to the new API make a trivial version
> > >>>> number update. Folks that dont, will not. Actual implementation
> > >>>> behaviours would remain the same, unlike with many 5.x bumps. Could
> > >>>> jump it to 5.30.x to separate and align with supporting Jakarta
> > >

Re: ASF board report due in two days!

[Jean-Baptiste Onofré]

+1

it looks good, thanks !

Sorry I was busy and didn't have time to add content to the report.

Regards
JB

On Wed, Apr 12, 2023 at 12:34 PM Robbie Gemmell
 wrote:
>
> I fleshed out the report with the stats + releases etc detail, tweaked
> the earlier additions from Justin and Matt, and reflowed things so it
> can be submitted directly via Whimsy.
>
> https://github.com/apache/activemq-website/commit/8035b7148bba966f8d72aba682fc8a118cdecbbf
>
> https://github.com/apache/activemq-website/blob/8035b7148bba966f8d72aba682fc8a118cdecbbf/src/team/reports/DRAFT-ActiveMQ-board-report.txt
>
> Robbie
>
> On Tue, 11 Apr 2023 at 20:36, Bruce Snyder  wrote:
> >
> > So far, there have been zero contributions to the board report and it's due
> > tomorrow. Please contribute to this month's board report so I can submit it
> > tomorrow.
> >
> > Bruce
> >
> > On Mon, Apr 10, 2023 at 11:36 AM Bruce Snyder 
> > wrote:
> >
> > > It looks like we got notified late again regarding this month's board
> > > report and it's due in two days!
> > >
> > > Please provide your contributions for this board report by adding them to
> > > the following file already in the git repo:
> > >
> > >
> > > https://github.com/apache/activemq-website/blob/main/src/team/reports/DRAFT-ActiveMQ-board-report.txt
> > >
> > >
> > > Bruce
> > >
> > > --
> > > perl -e 'print
> > > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E > > http://bsnyder.org/ 
> > >
> >
> >
> > --
> > perl -e 'print
> > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E > http://bsnyder.org/ 

[ANN] Apache ActiveMQ 5.18.1 has been released!

[Jean-Baptiste Onofré]

The ActiveMQ team is pleased to announce Apache ActiveMQ 5.18.1 release.

This release is a maintenance release on the 5.18.x series.
It especially fixes an issue with the activemq-client-jakarta artifact.

You can find details on the Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352969

You can download ActiveMQ 5.18.1 here:
https://activemq.apache.org/components/classic/download/

Enjoy!
---
The Apache ActiveMQ team

Re: activemq-client-jakarta 5.18.1 not published on Maven

[Jean-Baptiste Onofré]

Hi,

The vote is not closed yet. As soon as we close the vote and announce
5.18.1 release, it will be available on Maven Central.

Regards
JB

On Fri, Apr 14, 2023 at 9:33 AM Christian Winkler
 wrote:
>
> Hi all.
>
> I found that the 5.18.1 release of activemq-client-jakarta is not published 
> on Maven.
> The only version that can be found there so far is the broken 5.18.0
> https://mvnrepository.com/artifact/org.apache.activemq/activemq-client-jakarta
> Is this intentionally?
>
> Best regards
> Christian Winkler

[RESULT][VOTE] Apache ActiveMQ 5.18.1 release

[Jean-Baptiste Onofré]

Hi all,

this vote passed with the following result:

+1 (binding): Christopher Shannon, JB Onofré, Timothy Bish
+1 (non binding): Jean-Louis Monteiro, François Papon, Matt Pavlovich,
Jamie Goodyear

I'm promoting the artifacts on Maven Central and dist.apache.org, then
I will update Jira and the website, and I will announce the release.

Thanks all for your vote!

Regards
JB

On Tue, Apr 11, 2023 at 11:26 AM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> I submit Apache ActiveMQ 5.18.1 release to your vote. This release
> fixes activemq-client-jakarta where the META-INF/services file was
> missing in the artifact.
>
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352969
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1278/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.1/
>
> Git tag: activemq-5.18.1
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: [PROPOSAL] Jakarta approach for ActiveMQ 5.x broker

[Jean-Baptiste Onofré]

Hi,

I agree with the plan but why not keep 5.19.0-SNAPSHOT on main ?
We have the activemq-5.18.x branch already that could be LTS where we
keep javax namespace.

Regards
JB

On Thu, Mar 30, 2023 at 7:54 PM Matt Pavlovich  wrote:
>
> Hello All-
>
> I started building a jakarta-based broker for ActiveMQ 5.x and propose the 
> following steps to manage the change.
>
> Background:
>
> Jakarta support in ActiveMQ 5.x is going to pull in JDK 17, Spring 6, Jakarta 
> EE 9, Servlet 5.x, and Jetty 11. That is quite a bit of change, and I suggest 
> we leave a ‘gap version’ in case we need to make any incremental updates to 
> 5.18.x series along the way.
>
> 1. Rename main to 5.20.0-SNAPSHOT
> 2. Commit broker-related jakarta, servlet, jetty, spring, etc changes to main
> 3. Create new ‘-javax’ broker modules to support a 
> apache-activemq-javax-5.20.0-bin.tar.gz package using re-packaging of the 
> jakarta artifacts.
> 4. Leave 5.19.x as a ‘gap version’ in case it is needed for 5.18.x changes
>
> Thanks,
> Matt Pavlovich

[VOTE] Apache ActiveMQ 5.18.1 release

[Jean-Baptiste Onofré]

Hi,

I submit Apache ActiveMQ 5.18.1 release to your vote. This release
fixes activemq-client-jakarta where the META-INF/services file was
missing in the artifact.

You can take a look on the Release Notes for details:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352969

Maven Staging Repository:
https://repository.apache.org/content/repositories/orgapacheactivemq-1278/

Dist Staging Repository:
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.1/

Git tag: activemq-5.18.1

Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks !
Regards
JB

Re: [VOTE] Apache ActiveMQ 5.18.1 release

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Apr 11, 2023 at 11:26 AM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> I submit Apache ActiveMQ 5.18.1 release to your vote. This release
> fixes activemq-client-jakarta where the META-INF/services file was
> missing in the artifact.
>
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352969
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1278/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.1/
>
> Git tag: activemq-5.18.1
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: [PROPOSAL] Jakarta approach for ActiveMQ 5.x broker

[Jean-Baptiste Onofré]

ging this up. We definitely need to figure out a
> > >>> path
> > >>>>> forward as there is a lot of confusion about this still and users are
> > >>>>> getting bit by it when trying to upgrade to Spring 6 and Spring boot
> > 3.
> > >>>>>
> > >>>>> Ultimately I think we will need to support both javax and jakarta for
> > >>>> quite
> > >>>>> a while because while some users are going to want to use newer
> > >>>>> technologies that require jakarta (like Spring 6 ) others will be
> > happy
> > >>>> to
> > >>>>> stay on the old APIs for a while. So the question becomes what is the
> > >>>> best
> > >>>>> way to do that. I do think that some sort of repackaging is probably
> > >>> the
> > >>>>> way to go like we did for the client but to do it for all the
> > relevant
> > >>>>> modules and release both.  We can keep 5.18.x as a long running
> > branch
> > >>> to
> > >>>>> back port but it would still be nice if the latest worked for either
> > >>> API
> > >>>>> (ie 5.19.x). I'm thinking more about it and we can probably just do
> > it
> > >>> in
> > >>>>> 5.19.x and don't need a gap version.
> > >>>>>
> > >>>>> I can see 3 ways to release both:
> > >>>>>
> > >>>>> *1) Create duplicate modules (like we did with  the client for
> > jakarta
> > >>> in
> > >>>>> 5.18.x). *This works but means a lot of extra modules to maintain but
> > >>> is
> > >>>>> probably the most flexible as you can do custom things in each module
> > >>>>> easily. We could create BOM files for people to use to import the
> > right
> > >>>>> things to keep things consistent.
> > >>>>>
> > >>>>> 
> > >>>>> org.apache.activemq
> > >>>>> activemq-broker-javax
> > >>>>> 5.19.0
> > >>>>> 
> > >>>>>
> > >>>>> 
> > >>>>> org.apache.activemq
> > >>>>> activemq-broker-jakarta
> > >>>>> 5.19.0
> > >>>>> 
> > >>>>>
> > >>>>> *2) Don't add new modules, just keep the same ones but have each
> > module
> > >>>>> build 2 jars using classifiers. *We could just have each module
> > build 2
> > >>>>> jars and repackage.  My primary concern about sharing the same module
> > >>> for
> > >>>>> both APIs would be if the Jakarta API becomes different enough that
> > >>>>> repackaging doesn't work due to changes between it and javax but we
> > >>> might
> > >>>>> still be able to make this work by having each classified jar only
> > pull
> > >>>> in
> > >>>>> certain things.
> > >>>>>
> > >>>>> 
> > >>>>> org.apache.activemq
> > >>>>> activemq-broker
> > >>>>> 5.19.0
> > >>>>> javax
> > >>>>> 
> > >>>>>
> > >>>>> 
> > >>>>> org.apache.activemq
> > >>>>> activemq-broker
> > >>>>> 5.19.0
> > >>>>> jakarta
> > >>>>> 
> > >>>>>
> > >>>>> *3) Just build with a different version (this is what Guava does with
> > >>> jre
> > >>>>> and android). *This is probably the most annoying as you would need
> > to
> > >>>>> re-package and then I guess use a different version when building.
> > >>>>>
> > >>>>> 
> > >>>>> org.apache.activemq
> > >>>>> activemq-broker
> > >>>>> 5.19.0-javax
> > >>>>> 
> > >>>>>
> > >>>>> 
> > >>>>> org.apache.activemq
> > >>>>> activemq-broker
> > >>>>> 5.19.0-jakarta
> > >>>>> 
> > >>>>>
> > >>>>>
> > >>>>> On Thu, Mar 30, 2023 at 4:06 PM Endre Stølsvik 
> > >>>> wrote:
> > >>>>>
> > >>>>>> From a lurker position here, I just wanted to point out that Jetty
> > is
> > >>>>>> evidently making a version 12 which will support both javax. and
> > >>>> jakarta.
> > >>>>>> in the same server.
> > >>>>>> https://www.eclipse.org/jetty/download.php
> > >>>>>>
> > >>>>>> Kind regards,
> > >>>>>> Endre
> > >>>>>>
> > >>>>>>
> > >>>>>> On Thu, Mar 30, 2023 at 9:54 PM Jean-Baptiste Onofré <
> > j...@nanthrax.net
> > >>>>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> Hi,
> > >>>>>>>
> > >>>>>>> I agree with the plan but why not keep 5.19.0-SNAPSHOT on main ?
> > >>>>>>> We have the activemq-5.18.x branch already that could be LTS where
> > we
> > >>>>>>> keep javax namespace.
> > >>>>>>>
> > >>>>>>> Regards
> > >>>>>>> JB
> > >>>>>>>
> > >>>>>>> On Thu, Mar 30, 2023 at 7:54 PM Matt Pavlovich  > >
> > >>>>>> wrote:
> > >>>>>>>>
> > >>>>>>>> Hello All-
> > >>>>>>>>
> > >>>>>>>> I started building a jakarta-based broker for ActiveMQ 5.x and
> > >>> propose
> > >>>>>>> the following steps to manage the change.
> > >>>>>>>>
> > >>>>>>>> Background:
> > >>>>>>>>
> > >>>>>>>> Jakarta support in ActiveMQ 5.x is going to pull in JDK 17, Spring
> > >>> 6,
> > >>>>>>> Jakarta EE 9, Servlet 5.x, and Jetty 11. That is quite a bit of
> > >>> change,
> > >>>>>> and
> > >>>>>>> I suggest we leave a ‘gap version’ in case we need to make any
> > >>>>>> incremental
> > >>>>>>> updates to 5.18.x series along the way.
> > >>>>>>>>
> > >>>>>>>> 1. Rename main to 5.20.0-SNAPSHOT
> > >>>>>>>> 2. Commit broker-related jakarta, servlet, jetty, spring, etc
> > >>> changes
> > >>>>>> to
> > >>>>>>> main
> > >>>>>>>> 3. Create new ‘-javax’ broker modules to support a
> > >>>>>>> apache-activemq-javax-5.20.0-bin.tar.gz package using re-packaging
> > of
> > >>>> the
> > >>>>>>> jakarta artifacts.
> > >>>>>>>> 4. Leave 5.19.x as a ‘gap version’ in case it is needed for 5.18.x
> > >>>>>>> changes
> > >>>>>>>>
> > >>>>>>>> Thanks,
> > >>>>>>>> Matt Pavlovich
> > >>>>>>>
> > >>>>>>
> > >>>>
> > >>>>
> > >>>
> >
> >

Re: [VOTE] Apache ActiveMQ 5.16.6 release

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Feb 10, 2023 at 4:56 PM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> We receive several requests to provide a new (final) ActiveMQ 5.16.6
> release, including few security fixes/improvements.
>
> So, I submit ActiveMQ 5.16.6 release to your vote. This one should be
> the last version on the 5.16.x series, inviting our users to upgrade
> to at least 5.17.x (or 5.18.x that should be available soon).
>
> Please take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351793
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1269/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.16.6/
>
> Git tag: activemq-5.16.6
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: [VOTE] Apache ActiveMQ 5.16.6 release

[Jean-Baptiste Onofré]

Gentle reminder: we would need an additional binding vote to get 5.16.6 pass.

Thanks
Regards
JB

On Fri, Feb 10, 2023 at 4:56 PM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> We receive several requests to provide a new (final) ActiveMQ 5.16.6
> release, including few security fixes/improvements.
>
> So, I submit ActiveMQ 5.16.6 release to your vote. This one should be
> the last version on the 5.16.x series, inviting our users to upgrade
> to at least 5.17.x (or 5.18.x that should be available soon).
>
> Please take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351793
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1269/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.16.6/
>
> Git tag: activemq-5.16.6
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: [VOTE] Apache ActiveMQ Artemis 2.28.0

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Jan 31, 2023 at 4:18 PM Clebert Suconic
 wrote:
>
> I would like to propose an Apache ActiveMQ Artemis 2.28.0 release.
>
> I would like to highlight the following changes in this release:
>
> - Page counting improved. We no longer store counters in the journal
> simply relying on paging itself for that
> - We implemented a way to sync mirror from AMQP Broker Connections
>
> For a complete release notes:
> https://activemq.apache.org/components/artemis/download/release-notes-2.28.0
>
> The git commit 
> report:https://activemq.apache.org/components/artemis/download/commit-report-2.28.0
>
>
> Source and binary staged distributions:
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.28.0
>
> The maven repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1268
>
> In case you want to give it a try with the maven repo on examples:
> https://activemq.apache.org/components/artemis/documentation/hacking-guide/validating-releases.html
>
>
> The current release candidate is tagged on the git repository as 2.28.0
>
> I will update the website after the vote has passed
>
> [ ] +1 approve this release
> [ ] -1 disapprove (and why)
> [ ] +0 no opinion (I would appreciate a reason why if this is your
> choice as well)

[VOTE] Apache ActiveMQ 5.16.6 release

[Jean-Baptiste Onofré]

Hi guys,

We receive several requests to provide a new (final) ActiveMQ 5.16.6
release, including few security fixes/improvements.

So, I submit ActiveMQ 5.16.6 release to your vote. This one should be
the last version on the 5.16.x series, inviting our users to upgrade
to at least 5.17.x (or 5.18.x that should be available soon).

Please take a look on the Release Notes for details:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12351793

Maven Staging Repository:
https://repository.apache.org/content/repositories/orgapacheactivemq-1269/

Dist Staging Repository:
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.16.6/

Git tag: activemq-5.16.6

Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks !
Regards
JB

Re: [VOTE] Apache ActiveMQ Artemis 2.29.0

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Thu, Jun 15, 2023 at 1:39 AM Clebert Suconic
 wrote:
>
> I would like to propose an Apache ActiveMQ Artemis 2.29.0 release.
>
> This is a representative workload with 126 JIRAs and 200+ commits with
> a diverse number of committers. Thanks to all who contributed to this
> big release.
>
>
> The release notes can be found here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352880=12315920
>
>
> Ths git commit report is here:
> https://activemq.apache.org/components/artemis/download/commit-report-2.29.0
>
>
> Source and binary distributions can be found here:
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.29.0
>
>
> The Maven repository is here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1279
>
> In case you want to give it a try with the maven repo on examples:
> https://activemq.apache.org/components/artemis/documentation/hacking-guide/validating-releases.html
>
>
> The version has been tagged on git as '2.29.0'
>
> I will update the website after the vote has passed.
>
>
>
> [ ] +1 approve this release
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
> Here's my +1
>
>
> I will keep the Vote open until monday, US EST morning, on June 19th
>
>
> --
> Clebert Suconic

[HEADS-UP] Preparing Apache ActiveMQ 5.18.2 and 5.17.5 releases

[Jean-Baptiste Onofré]

Hi guys,

FYI, we are preparing ActiveMQ 5.18.2 and 5.17.5 before moving forward
on 5.19.x (planned for next month).

I hope to be able to submit 5.18.2 and 5.17.5 releases to vote during
the weekend.

Stay tuned !

Regards
JB

[ANN] Apache ActiveMQ 5.18.2 has been released!

[Jean-Baptiste Onofré]

The ActiveMQ team is pleased to announce Apache ActiveMQ 5.18.2 release.

It’s a maintenance release on the ActiveMQ 5.18.x series, bringing:
- fix potential NPE when removing consumer with selector
- fix composite consumers in a Network of Brokers
- fix memory leak on the STOMP transport when client unsubscribe
- a bunch of dependency updates

You can find details on the Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12353099

You can download ActiveMQ 5.18.2 here:
https://activemq.apache.org/components/classic/download/

Enjoy!

Regards
---
The Apache ActiveMQ team

[ANN] Apache ActiveMQ 5.17.5 has been released!

[Jean-Baptiste Onofré]

The ActiveMQ team is pleased to announce Apache ActiveMQ 5.17.5 release.

It’s a maintenance release on the ActiveMQ 5.17.x series, bringing:

- fix on stale queues when a connection is long to shutdown
- fix on KahaDB where the db files may be larger than the maxLength
configuration
- fix on composite consumers on a Network of Brokers
- fix memory leak on STOMP transport when client unsubscribe
- a bunch of dependency updates

You can find details on the Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352888

You can download ActiveMQ 5.17.5 here:
https://activemq.apache.org/components/classic/download/

Enjoy!

Regards
---
The Apache ActiveMQ team

Re: [DISCUSS] Naming convention for official Docker images

[Jean-Baptiste Onofré]

Thanks all, I will rename apache/activemq to apache/activemq-classic.

Regards
JB

On Mon, Jul 10, 2023 at 3:57 PM Justin Bertram  wrote:
>
> This weekend JB announced [1] the availability of official Docker images
> for ActiveMQ "Classic" in the "apache/activemq" namespace [2].
>
> Perhaps I missed it, but I don't recall (and can't find) any discussion of
> or notification about this. Users will certainly expect images for both
> "Classic" and Artemis so my concern is regarding the namespace. If both
> "Classic" and Artemis share the apache/activemq namespace directly then
> there may eventually be version number conflicts and there certainly will
> be confusion about which version is which.
>
> Before these images are widely adopted I think the namespace should be
> clarified just as it is on the website so that ActiveMQ "Classic" uses
> "apache/activemq/classic" and ActiveMQ Artemis uses
> "apache/activemq/artemis".
>
> Thoughts?
>
>
> Justin
>
> [1] https://lists.apache.org/thread/4cqbm0gsbj184vrp13yorcd2rrbdcsmx
> [2] https://hub.docker.com/r/apache/activemq/tags

Re: [DISCUSS] Naming convention for official Docker images

[Jean-Baptiste Onofré]

Hi Justin,

It has been discussed but not the name specifically.

As we use apache/activemq-artemis, I thought "logical" to use
apache/activemq (but maybe activemq-classic makes more sense).

I'm not sure we will be able to use apache/activemq/classic and
apache/activemq/artemis, but we can definitely use
apache/activemq-classic as apache/activemq-artemis.

I can rename right now.

Thoughts ?

Regards
JB


On Mon, Jul 10, 2023 at 3:57 PM Justin Bertram  wrote:
>
> This weekend JB announced [1] the availability of official Docker images
> for ActiveMQ "Classic" in the "apache/activemq" namespace [2].
>
> Perhaps I missed it, but I don't recall (and can't find) any discussion of
> or notification about this. Users will certainly expect images for both
> "Classic" and Artemis so my concern is regarding the namespace. If both
> "Classic" and Artemis share the apache/activemq namespace directly then
> there may eventually be version number conflicts and there certainly will
> be confusion about which version is which.
>
> Before these images are widely adopted I think the namespace should be
> clarified just as it is on the website so that ActiveMQ "Classic" uses
> "apache/activemq/classic" and ActiveMQ Artemis uses
> "apache/activemq/artemis".
>
> Thoughts?
>
>
> Justin
>
> [1] https://lists.apache.org/thread/4cqbm0gsbj184vrp13yorcd2rrbdcsmx
> [2] https://hub.docker.com/r/apache/activemq/tags

[INFO] Official Docker images available for Apache ActiveMQ

[Jean-Baptiste Onofré]

Hi,

With the new Apache ActiveMQ 5.18.2 and 5.17.5 releases, we now
publish official docker images.

You can find these images directly on Docker Hub:
https://hub.docker.com/r/apache/activemq/tags

You can pull directly the images with:

docker pull apache/activemq:5.18.2

or

docker pull apache/activemq:latest

Enjoy!
Regards
JB

Re: [VOTE] Apache ActiveMQ Artemis 2.30.0

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Jul 21, 2023 at 3:54 PM Justin Bertram  wrote:
>
> I would like to propose an Apache ActiveMQ Artemis 2.30.0 release.
>
> This is mainly a bug-fix release with a few small improvements and a
> handful of dependency upgrades.
>
> The release notes can be found here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920=12353357
>
> Ths git commit report is here:
> https://activemq.apache.org/components/artemis/download/commit-report-2.30.0.html
>
> Source and binary distributions can be found here:
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.30.0/
>
> The Maven repository is here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1367
>
> In case you want to give it a try with the maven repo on examples:
> https://activemq.apache.org/components/artemis/documentation/hacking-guide/validating-releases.html
>
> The source tag:
> https://github.com/apache/activemq-artemis/tree/2.30.0
>
> I will update the website after the vote has passed.
>
>
> [ ] +1 approve this release
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Here's my +1
>
>
> Justin

Re: [INFO] Official Docker images available for Apache ActiveMQ

[Jean-Baptiste Onofré]

Hi,

I moved the images to the new apache/activemq-classic repository.

You can find the available images here:
https://hub.docker.com/r/apache/activemq-classic/tags

Regards
JB

On Sat, Jul 8, 2023 at 7:31 AM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> With the new Apache ActiveMQ 5.18.2 and 5.17.5 releases, we now
> publish official docker images.
>
> You can find these images directly on Docker Hub:
> https://hub.docker.com/r/apache/activemq/tags
>
> You can pull directly the images with:
>
> docker pull apache/activemq:5.18.2
>
> or
>
> docker pull apache/activemq:latest
>
> Enjoy!
> Regards
> JB

Re: Please help -- board report due next week

[Jean-Baptiste Onofré]

Hi Bruce,

Thanks for the report !
It looks good to me. About Classic, you mentioned the two releases we
did in June and the work about "Jakarta broker" planned for 5.19.x.

We will provide more details in the next report (I should have a more
concrete roadmap about 5.19.x just after my vacations).

Regards
JB

On Thu, Aug 3, 2023 at 5:22 PM Bruce Snyder  wrote:
>
> We just received the notice to submit a board report by Tuesday, Aug 8.
>
> Obviously this is a very short timeline, so please contribute sooner rather
> than later via the following file:
>
> https://github.com/apache/activemq-website/blob/main/src/team/reports/DRAFT-ActiveMQ-board-report.txt
>
> All project activity is welcome!
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E http://bsnyder.org/ 

Re: [HEADS-UP] Preparing Apache ActiveMQ 5.18.2 and 5.17.5 releases

[Jean-Baptiste Onofré]

Hi guys,

I did the Jira triage. I have a couple of fixes on the way. It should
be done by tomorrow. I plan to submit releases to vote on Friday this
week.

Regards
JB

On Thu, Jun 15, 2023 at 3:20 PM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> FYI, we are preparing ActiveMQ 5.18.2 and 5.17.5 before moving forward
> on 5.19.x (planned for next month).
>
> I hope to be able to submit 5.18.2 and 5.17.5 releases to vote during
> the weekend.
>
> Stay tuned !
>
> Regards
> JB

Re: [HEADS-UP] Preparing Apache ActiveMQ 5.18.2 and 5.17.5 releases

[Jean-Baptiste Onofré]

Hi François

That's correct.

Right now both 5.17.x and 5.18.x are active.
When 5.19.x will be released, 5.18.x will be LTS and 5.17.x not active anymore.

Regards
JB

On Fri, Jun 16, 2023 at 8:39 AM Francois Papon
 wrote:
>
> Hi JB,
>
> Is the 5.17.x will be no more in maintenance after releasing the 5.19.x?
>
> The idea is to keep only 2 release branch active?
>
> regards,
>
> François
>
> On 15/06/2023 15:20, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > FYI, we are preparing ActiveMQ 5.18.2 and 5.17.5 before moving forward
> > on 5.19.x (planned for next month).
> >
> > I hope to be able to submit 5.18.2 and 5.17.5 releases to vote during
> > the weekend.
> >
> > Stay tuned !
> >
> > Regards
> > JB

Re: [HEADS-UP] Preparing Apache ActiveMQ 5.18.2 and 5.17.5 releases

[Jean-Baptiste Onofré]

Hi guys

I have a release build issue due to maven plugin updates. I'm fixing that.

I will start the votes today when fixed.

Sorry for this delay. Stay tuned!

Regards
JB

On Thu, Jun 15, 2023 at 3:20 PM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> FYI, we are preparing ActiveMQ 5.18.2 and 5.17.5 before moving forward
> on 5.19.x (planned for next month).
>
> I hope to be able to submit 5.18.2 and 5.17.5 releases to vote during
> the weekend.
>
> Stay tuned !
>
> Regards
> JB

Re: [VOTE] Apache ActiveMQ 5.17.5 release

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Jun 28, 2023 at 3:40 PM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> I submit Apache ActiveMQ 5.17.5 release to your vote. This release is
> a maintenance release on the 5.17.x series bringing:
> - fix on stale queues when a connection is long to shutdown
> - fix on KahaDB where the db files may be larger than the maxLength
> configuration
> - fix on composite consumers on NoB
> - fix memory leak on STOMP transport when clients unsubscribe
> - a bunch of dependency updates
>
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352888
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1284/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.5/
>
> Git tag: activemq-5.17.5
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: [VOTE] Apache ActiveMQ 5.18.2 release

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Jun 28, 2023 at 7:44 AM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> I submit Apache ActiveMQ 5.18.2 release to your vote. This release is
> a maintenance release on the 5.18.x series bringing:
> - fix potential NPE when removing consumer with selector
> - fix composite consumers in a NoB
> - fix memory leak on the STOMP transport when client unsubscribe
> - a bunch of dependency updates
>
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12353099
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1283/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.2/
>
> Git tag: activemq-5.18.2
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: [VOTE] Apache ActiveMQ 5.18.2 release

[Jean-Baptiste Onofré]

Hi Chris

Thanks for fixing that. Yes, it's "just" the test, so I propose to
continue the release (it's already fixed for next release cycle).

Regards
JB

On Fri, Jun 30, 2023 at 12:44 AM Christopher Shannon
 wrote:
>
> FYI for anyone reviewing the release, I noticed that there is a test
> failure in JournalCorruptionEofIndexRecoveryTest but it's the test itself.
> There's already a fix in main here
> https://github.com/apache/activemq/commit/cfbea60d6d but the backport got
> missed.
>
> Since it's just the test that is broken I think it's fine to continue the
> release as is.
>
> On Thu, Jun 29, 2023 at 11:09 AM Matt Pavlovich  wrote:
>
> > +1 (non-binding) successfully ran internal test suite
> >
> > Thanks JB!
> >
> > Matt Pavlovich
> >
> > > On Jun 28, 2023, at 12:44 AM, Jean-Baptiste Onofré 
> > wrote:
> > >
> > > Hi,
> > >
> > > I submit Apache ActiveMQ 5.18.2 release to your vote. This release is
> > > a maintenance release on the 5.18.x series bringing:
> > > - fix potential NPE when removing consumer with selector
> > > - fix composite consumers in a NoB
> > > - fix memory leak on the STOMP transport when client unsubscribe
> > > - a bunch of dependency updates
> > >
> > > You can take a look on the Release Notes for details:
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12353099
> > >
> > > Maven Staging Repository:
> > >
> > https://repository.apache.org/content/repositories/orgapacheactivemq-1283/
> > >
> > > Dist Staging Repository:
> > > https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.2/
> > >
> > > Git tag: activemq-5.18.2
> > >
> > > Please vote to approve this release:
> > > [ ] +1 Approve the release
> > > [ ] -1 Don't approve the release (please provide specific comments)
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Thanks !
> > > Regards
> > > JB
> >
> >

[RESULT][VOTE] Apache ActiveMQ 5.17.5 release

[Jean-Baptiste Onofré]

Hi,

this vote passed with the following result:

+1 (binding): Chris Shannon, JB Onofré, Tim Bish
+1 (non binding): Jamie Goodyear, François Papon, Jean-Louis Monteiro,
Matt Pavlovich

I'm promoting the artifacts on Maven Central and dist.apache.org. I
will update the website and do the announcement.

Thanks all for your vote!

Regards
JB

On Wed, Jun 28, 2023 at 3:40 PM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> I submit Apache ActiveMQ 5.17.5 release to your vote. This release is
> a maintenance release on the 5.17.x series bringing:
> - fix on stale queues when a connection is long to shutdown
> - fix on KahaDB where the db files may be larger than the maxLength
> configuration
> - fix on composite consumers on NoB
> - fix memory leak on STOMP transport when clients unsubscribe
> - a bunch of dependency updates
>
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352888
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1284/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.5/
>
> Git tag: activemq-5.17.5
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

[RESULT][VOTE] Apache ActiveMQ 5.18.2 release

[Jean-Baptiste Onofré]

Hi,

this vote passed with the following result:

+1 (binding): Chris Shannon, JB Onofré, Tim Bish
+1 (non binding): Jamie Goodyear, François Papon, Jean-Louis Monteiro,
Matt Pavlovich

I'm promoting the artifacts on Maven Central and dist.apache.org. I
will update the website and do the announcement.

Thanks all for your vote!

Regards
JB

On Wed, Jun 28, 2023 at 7:44 AM Jean-Baptiste Onofré  wrote:
>
> Hi,
>
> I submit Apache ActiveMQ 5.18.2 release to your vote. This release is
> a maintenance release on the 5.18.x series bringing:
> - fix potential NPE when removing consumer with selector
> - fix composite consumers in a NoB
> - fix memory leak on the STOMP transport when client unsubscribe
> - a bunch of dependency updates
>
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12353099
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1283/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.2/
>
> Git tag: activemq-5.18.2
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

[VOTE] Apache ActiveMQ 5.18.2 release

[Jean-Baptiste Onofré]

Hi,

I submit Apache ActiveMQ 5.18.2 release to your vote. This release is
a maintenance release on the 5.18.x series bringing:
- fix potential NPE when removing consumer with selector
- fix composite consumers in a NoB
- fix memory leak on the STOMP transport when client unsubscribe
- a bunch of dependency updates

You can take a look on the Release Notes for details:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12353099

Maven Staging Repository:
https://repository.apache.org/content/repositories/orgapacheactivemq-1283/

Dist Staging Repository:
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.18.2/

Git tag: activemq-5.18.2

Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks !
Regards
JB

[VOTE] Apache ActiveMQ 5.17.5 release

[Jean-Baptiste Onofré]

Hi guys,

I submit Apache ActiveMQ 5.17.5 release to your vote. This release is
a maintenance release on the 5.17.x series bringing:
- fix on stale queues when a connection is long to shutdown
- fix on KahaDB where the db files may be larger than the maxLength
configuration
- fix on composite consumers on NoB
- fix memory leak on STOMP transport when clients unsubscribe
- a bunch of dependency updates

You can take a look on the Release Notes for details:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352888

Maven Staging Repository:
https://repository.apache.org/content/repositories/orgapacheactivemq-1284/

Dist Staging Repository:
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.17.5/

Git tag: activemq-5.17.5

Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks !
Regards
JB

Re: Remove Jackson from ActiveMQ classic

[Jean-Baptiste Onofré]

Hi,

We discussed this already in the past. IMHO, we can replace jackson by
just sax (no need to use JSON-B regarding our usage).

That sasid, I don't see any huge issue with Jackson: it works fine and
we keep the versions up to date to fix CVE.

The only interesting move would be to use SAX parsing directly instead
of a mapper.

Regards
JB

On Tue, May 16, 2023 at 12:17 PM Jean-Louis Monteiro
 wrote:
>
> Hi all,
>
> Jackson seems to be frequently affected by CVEs and it's really a pain for
> users.
>
> Looks like Jackson is only used in the WebConsole to read/write a few
> attributes. I'm sure we can get rid of it and either use a standard API so
> one can plugin any implementation, or just write down a utility class to
> parse the small attribute we have to.
>
> thoughts?
>
> I'm happy to do a PR to remove it if that's the consensus.
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com

Re: Remove Jackson from ActiveMQ classic

[Jean-Baptiste Onofré]

FYI, Romain provided a PR to use Apache Johnson while ago:
https://github.com/apache/activemq/pull/308

The PR is fine (I already tested when submitted), it just needs a rebase.
If we agree, I can move forward on this one.

Regards
JB

On Wed, May 17, 2023 at 4:04 AM Justin Bertram  wrote:
>
> For what it's worth, Artemis uses JSON-P [1] since it's a standard, simple
> API. We use Apache Johnzon for the implementation. It does everything we
> need given our relatively basic use-cases.
>
> Additionally, we wrap the API so that all the broker code can use the
> wrapper and the wrapper can be modified to work in Java EE or Jakarta EE
> environments.
>
>
> Justin
>
> [1]
> https://javaee.github.io/javaee-spec/javadocs/javax/json/package-summary.html
>
> On Tue, May 16, 2023 at 6:02 PM Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
> > Yes, this keeps coming up and as JB said I don't see a problem with
> > Jackson, it can be updated for CVEs and works very well and is quite
> > feature rich in case we need it.
> >
> > If we are going to do any JSON serialization I don't want to re-invent the
> > wheel and create our own serializer, so we should at least use an existing
> > library, even if we make it pluggable like JSON-B.
> >
> > There's alternatives too like Gson if we wanted something
> > smaller/lightweight.
> >
> > On Tue, May 16, 2023 at 3:11 PM Jean-Baptiste Onofré 
> > wrote:
> >
> > > Hi,
> > >
> > > We discussed this already in the past. IMHO, we can replace jackson by
> > > just sax (no need to use JSON-B regarding our usage).
> > >
> > > That sasid, I don't see any huge issue with Jackson: it works fine and
> > > we keep the versions up to date to fix CVE.
> > >
> > > The only interesting move would be to use SAX parsing directly instead
> > > of a mapper.
> > >
> > > Regards
> > > JB
> > >
> > > On Tue, May 16, 2023 at 12:17 PM Jean-Louis Monteiro
> > >  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Jackson seems to be frequently affected by CVEs and it's really a pain
> > > for
> > > > users.
> > > >
> > > > Looks like Jackson is only used in the WebConsole to read/write a few
> > > > attributes. I'm sure we can get rid of it and either use a standard API
> > > so
> > > > one can plugin any implementation, or just write down a utility class
> > to
> > > > parse the small attribute we have to.
> > > >
> > > > thoughts?
> > > >
> > > > I'm happy to do a PR to remove it if that's the consensus.
> > > >
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > >
> >

Re: [VOTE] Release activemq-nms-amqp 2.2.0-rc1

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Sat, May 6, 2023 at 8:58 PM Havret  wrote:
>
> Hi all,
>
> I have put together another release of activemq-nms-amqp. Please review it
> and vote accordingly.
>
> This update enhances the message acknowledgement functionality by
> supporting multiple AckType's, This improvement enables clients to utilize
> broker redelivery configurations automatically and aligns the client
> library more closely with the qpid-jms counterpart.
>
> This release contains the following change:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201=12353210
>
> The files can be grabbed from:
> *https://dist.apache.org/repos/dist/dev/activemq/activemq-nms-amqp/2.2.0-rc1/
> *
>
> Regards,
> Krzysztof
>
> Here's mine +1 (binding)

Re: activemq.xsd

[Jean-Baptiste Onofré]

Hi,

I will check the xsd uploaded. 5.19.x is not yet there anyway.

For Jakarta, do you want the client side or broker side or both ?

Regards
JB

On Wed, May 10, 2023 at 4:23 PM  wrote:
>
> Hi,
> I checked out the latest classic ActiveMQ 
> (https://github.com/apache/activemq.git)
> Due to my project at my employer I wanted to try to build 5.19 as pure 
> Jakarta.
> I am almost complete I think, updating spring to 6.0.8 as well.
>
> I am facing a problem with the activemq.xsd.
> It doesn't seem to be available in the project.  I did find 
> https://activemq.apache.org/schema/core/, but 5.18.x or 5.19.x isn't there 
> either.
> Can anyone provide some help on how to deal with this schema and build the 
> project?
>
> I am happy to contribute my updates when I have built the whole thing.
>
> Regards,
> Rune Gellein
> BT Plc

Re: NMS micro-site

[Jean-Baptiste Onofré]

Hi Mike,

It makes sense to have a component/sub-site dedicated to NMS.

Regards
JB

On Thu, May 11, 2023 at 12:05 PM Michael André Pearce
 wrote:
>
> Hi All,
>
> Krzysztof and I have been offline chatting and starting to feel the need to 
> revamp the NMS docs, one thing we're finding is that the docs area is a 
> little thin.
>
> We are thinking if it would make sense for us to make a micro-site docs akin 
> to how Artemis docs are done, where they are published separately and simply 
> iframed within the apache activemq main site.
>
> Does anyone have any big objections here if we were to venture/explore this 
> route?
> Also we were thinking of running it just as github pages, to really simplify 
> things.
>
> I want to put this out here, before we expend effort, to just make sure.
>
> Best
> Mike
>
>

Re: [roadmap] ActiveMQ LTS

[Jean-Baptiste Onofré]

Hi Matt,

I think it's what I proposed: 5.18.x should be our LTS branch currently.

Regards
JB

On Thu, Dec 21, 2023 at 3:19 PM Matt Pavlovich  wrote:
>
> Hey JB-
>
> +1 I agree, formalizing and communicating LTS is important to users.
>
> However, I think we should have a *released* branch that we feel is solid to 
> base LTS off of vs declaring a future unreleased branch as a LTS release.
>
> -Matt
>
> > On Dec 21, 2023, at 3:29 AM, Jean-Baptiste Onofré  wrote:
> >
> > Hi François,
> >
> > We discussed LTS/EOA but without commitment yet.
> >
> > The thing we agreed on is to maintain 3 branches active (so 6.0.x,
> > 5.18.x, 5.17.x right now). The same as we do in Apache Karaf
> > basically. I would consider it a kind of informal LTS :)
> > If we need to have a concrete LTS plan, then 5.18.x would be LTS but not 
> > 6.0.x.
> >
> > In terms of roadmap, we have basically:
> > - 6.1.x plan to include new JMS features support
> > - 6.x (6.2.x, 6.3.x, etc) will follow the same path with new JMS
> > features support
> > - 7.x will be a big milestone because we plan to remove Spring
> > (supporting new configuration format like activemq,xml, activemq,yaml,
> > activemq.json, etc), add new tools, etc
> >
> > If there are no objections, I can start a formal vote for LTS policy
> > and if the vote passes I can update the website.
> >
> > Regards
> > JB
> >
> > On Wed, Dec 20, 2023 at 8:04 AM Francois Papon
> >  wrote:
> >>
> >> Hi all,
> >>
> >> Now that the current release is on 6.x, I am searching for LTS
> >> informations about the 5.x version but I cannot find it on the website.
> >>
> >> Is there some info about this topic?
> >>
> >> regards,
> >>
> >> François
> >>
>

Re: [roadmap] ActiveMQ LTS

[Jean-Baptiste Onofré]

Hi François,

We discussed LTS/EOA but without commitment yet.

The thing we agreed on is to maintain 3 branches active (so 6.0.x,
5.18.x, 5.17.x right now). The same as we do in Apache Karaf
basically. I would consider it a kind of informal LTS :)
If we need to have a concrete LTS plan, then 5.18.x would be LTS but not 6.0.x.

In terms of roadmap, we have basically:
- 6.1.x plan to include new JMS features support
- 6.x (6.2.x, 6.3.x, etc) will follow the same path with new JMS
features support
- 7.x will be a big milestone because we plan to remove Spring
(supporting new configuration format like activemq,xml, activemq,yaml,
activemq.json, etc), add new tools, etc

If there are no objections, I can start a formal vote for LTS policy
and if the vote passes I can update the website.

Regards
JB

On Wed, Dec 20, 2023 at 8:04 AM Francois Papon
 wrote:
>
> Hi all,
>
> Now that the current release is on 6.x, I am searching for LTS
> informations about the 5.x version but I cannot find it on the website.
>
> Is there some info about this topic?
>
> regards,
>
> François
>

[ANN] Apache ActiveMQ 6.0.1 has been released!

[Jean-Baptiste Onofré]

The ActiveMQ team is pleased to announce Apache ActiveMQ 6.0.1 release.

It's maintenance release on the ActiveMQ 6.0.x series, bringing:
- Fix Jakarta support in ActiveMQ RA
- Fix OSGi headers in activemq-jms-pool and activemq-cf
- Fix provided jetty.xml example on the SSL connector
- Fix jolokia conf loading when using Windows service wrapper
- Several dependency updates

You can find details on the Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12353594

You can download ActiveMQ 6.0.1 here:
https://activemq.apache.org/components/classic/download/

Emjoy !

Regards
--
The Apache ActiveMQ team

Re: Update on ActiveMQ 6.x Release

[Jean-Baptiste Onofré]

Hi

ActiveMQ 6.0.1 has been released
(https://repo1.maven.org/maven2/org/apache/activemq/apache-activemq/6.0.1/).
I'm working on website update and announcement right now.

However, 6.0.1 has the same JMS 3.x support as 6.0.0.
We plan to have new features implemented in 6.1.0.

Regards
JB

On Mon, Dec 11, 2023 at 4:47 AM Abhisek Swain
 wrote:
>
> Hi Team,
>
> Any update on the timelines for ActiveMQ 6.0.1 release.
> As per the latest ActiveMQ 6.0.0 version, it's not fully compatible with JMS 
> 3.x (jakarta.jms namespace).
> We are using ActiveMQ in our product and facing issues related to JMS.
> Can we have a patch release with JMS3.x support.
>
> With Regards,
> Abhisek Swain

Re: Question about the ActiveMQ Statistics Plugin

[Jean-Baptiste Onofré]

Hi Sophie

Which version are you using?
The situation is the same: no special properties on the message
(redelivery, ...) ?

Regards
JB

PS: this kind of message should be sent to the user mailing list

On Tue, Jan 2, 2024 at 10:30 PM Sophie Borchart
 wrote:
>
> Hello,
> I’m running into a situation where I am using the ActiveMQ Statistics Plugin 
> to retrieve data for queues. I know my queues have data in them:
>
> "statistics": {
> "dequeue_count": 0,
> "average_message_size": 1152,
> "memory_usage": 3456,
> "consumer_count": 0,
> "min_enqueue_time": 0,
> "memory_percent_usage": 0,
> "average_enqueue_time": 0,
> "messages_cached": 0,
> "expired_count": 0,
> "inflight_count": 0,
> "max_enqueue_time": 0,
> "dispatch_count": 0,
> "queue_size": 0,
> "destination_name": "queue://inbound_destinations.201.id1",
> "producer_count": 0,
> "memory_limit": 536870912,
> "broker_name": "detachedBroker",
> "enqueue_count": 0
>   },
>
> As you can see the average message size > 0 and some statistics are being 
> retrieved, so I know the plug in is working.
>
> I can confirm in my database tht the messages are there, the queue size is 3:
>
>   container   | count | bytes | max_bytes
>
> --+---+---+---
>
>  queue://inbound_destinations.201.id1 | 3 |  1344 |   481
>
>
> However, the queue size is showing up as 0. This is when I am using a Linux 
> machine – when I use the same code on my mac it works just fine. Is there a 
> reason why this would occur, ActiveMQ is reporting the size as 0 when that is 
> not the case, but the rest of the data is correct.
>
> Please let me know, thank you!
> Best,
> Sophie

Re: Need your help to assemble the ActiveMQ board report quickly!

[Jean-Baptiste Onofré]

Hi Bruce

I committed the Classic part and updated some sections.
By the way, we can use reporter
(https://reporter.apache.org/wizard/?activemq) for the board report
(we can create and save draft and contribute on it, then you can just
push the submit button).

Regards
JB

On Thu, Jan 4, 2024 at 11:53 PM Bruce Snyder  wrote:
>
> Hi folks,
>
> Happy new year! Best wishes in 2024!!
>
> Moments ago, we were reminded that the next ActiveMQ board report is due no
> later than Tuesday, Jan 9. This leaves less than one week, so please do
> move quickly with your contributions.
>
> Per the past several reports, please add your contributions to the
> following file in git:
>
> https://github.com/apache/activemq-website/blob/main/src/team/reports/DRAFT-ActiveMQ-board-report.txt
>
> Simply replace the existing reports in the Project Activity with the latest.
>
> Thank you!
>
> Bruce
>
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E http://bsnyder.org/ 

Re: Need your help to assemble the ActiveMQ board report quickly!

[Jean-Baptiste Onofré]

I'm doing the "Classic" part.

On Thu, Jan 4, 2024 at 11:53 PM Bruce Snyder  wrote:
>
> Hi folks,
>
> Happy new year! Best wishes in 2024!!
>
> Moments ago, we were reminded that the next ActiveMQ board report is due no
> later than Tuesday, Jan 9. This leaves less than one week, so please do
> move quickly with your contributions.
>
> Per the past several reports, please add your contributions to the
> following file in git:
>
> https://github.com/apache/activemq-website/blob/main/src/team/reports/DRAFT-ActiveMQ-board-report.txt
>
> Simply replace the existing reports in the Project Activity with the latest.
>
> Thank you!
>
> Bruce
>
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E http://bsnyder.org/ 

Re: Need your help to assemble the ActiveMQ board report quickly!

[Jean-Baptiste Onofré]

Hi Bruce,

I mean we can use draft on reporter to populate the report content
(instead of website).
Just a proposal: it would avoid you to copy/paste from website :)

Regards
JB

On Fri, Jan 5, 2024 at 8:04 PM Bruce Snyder  wrote:
>
> HI JB,
>
> I always use Reporter to submit the report.
>
> Bruce
>
> On Thu, Jan 4, 2024 at 11:04 PM Jean-Baptiste Onofré 
> wrote:
>
> > Hi Bruce
> >
> > I committed the Classic part and updated some sections.
> > By the way, we can use reporter
> > (https://reporter.apache.org/wizard/?activemq) for the board report
> > (we can create and save draft and contribute on it, then you can just
> > push the submit button).
> >
> > Regards
> > JB
> >
> > On Thu, Jan 4, 2024 at 11:53 PM Bruce Snyder 
> > wrote:
> > >
> > > Hi folks,
> > >
> > > Happy new year! Best wishes in 2024!!
> > >
> > > Moments ago, we were reminded that the next ActiveMQ board report is due
> > no
> > > later than Tuesday, Jan 9. This leaves less than one week, so please do
> > > move quickly with your contributions.
> > >
> > > Per the past several reports, please add your contributions to the
> > > following file in git:
> > >
> > >
> > https://github.com/apache/activemq-website/blob/main/src/team/reports/DRAFT-ActiveMQ-board-report.txt
> > >
> > > Simply replace the existing reports in the Project Activity with the
> > latest.
> > >
> > > Thank you!
> > >
> > > Bruce
> > >
> > >
> > > --
> > > perl -e 'print
> > > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E > > http://bsnyder.org/ <http://bruceblog.org/>
> >
>
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E http://bsnyder.org/ <http://bruceblog.org/>

Re: [PROPOSAL] OpenWire exception handling mismatch between Javax and Jakarta APIs

[Jean-Baptiste Onofré]

It looks good to me.

Thanks,
Regards
JB

On Tue, Jan 16, 2024 at 3:38 PM Christopher Shannon
 wrote:
>
> As background, last week it was discovered (thanks Justin) that there was
> an oversight with the Exception handling over OpenWire with the upgrade to
> Jakarta apis in the 6.0.x broker.
> https://issues.apache.org/jira/browse/AMQ-9418
>
> The problem is that OpenWire has a response type to return an exception to
> the client and this response type includes the actual throwable type
> written as a string with the fully qualified package. This means that if an
> older 5.x client that is using the javax JMS apis receives back something
> like InvalidClientIDException from a 6.x broker the exception type received
> is actually going to be "jakarta.jms.InvalidIDException" and then the
> client can't unmarshall that since it's likely not on the classpath. The
> result is that if it converts it will get a ClassNotFoundException and just
> convert to a generic exception type so this could be a breaking change for
> clients that are trying to handle specific exceptions. Note that the
> reverse is actually also true, if a new 6.x client connected to a 5.x
> broker the same problem happens.
>
> I've been looking at ways to fix this broker side and it's not great. We
> would need to detect if the client wants jakarta or javax types (we can
> kind of do this for newer clients because
> https://issues.apache.org/jira/browse/AMQ-6379 has new clients set their
> actual client version from the manifest file in the jar) and then we have
> to pass that to the marshallers and signal in some way to convert.  The
> main problem is having to pass it to the marshaller means probably having
> to update the Openwire format to include the version discovered and having
> complicated detection logic depending on if it is set or not as not
> everything sets it. If we didn't want to do it at the marshaller level,
> we'd have to include or repackage both versions of the Exceptions which is
> also not ideal as having to include both javax and jakarta exception types
> could cause mistakes elsewhere and maintaining isn't fun.
>
> I think a much simpler approach is to just let the receiver (usually
> client) handle it. I think instead of trying to have the broker detect what
> to send, it should be handled on the unmarshal side of things by the
> receiver of the error command. The receiver (client or broker) knows if it
> will need to convert so it makes things much simpler. Obviously this would
> only work if we update the marshaller in the client code jar so my proposal
> would be to just release a small update in the next version of 5.18.x
> client and also 6.0.x clients to handle this. We can just document saying
> that if you need to have specific exception type translation and are using
> a broker and client that are not both javax or jakarta then you need to
> upgrade to a new client version for the translation. Otherwise they can
> just get the generic Throwable back and will work. The main use case I
> think is if clients are stuck on older versions of Java and can't upgrade
> yet when talking to a new broker or an older broker can't be upgraded yet
> but the clients can.
>
> Here is an example of fixing the 5.18.x client:
> https://github.com/cshannon/activemq/commit/b52bdd3f1cdac31e9aa6fed86e6737d376b8b5a4
> It's pretty simple, if we get back jakarta then convert to javax and done.
> We would do the reverse in 6.x branch.
>
> Going forward as a permanent fix, we should just fix this entirely in
> OpenWire v13. Including the Java exception types already caused a major CVE
> issue and now it's causing issues here. I think for the next OpenWire
> version we should create a new Exception type that uses an Error code just
> like Artemis and other projects do and then the client can just take the
> code and convert it to whatever exception it wants. We could either include
> the error handling change by itself in OpenWire v13 so we could even
> upgrade older 5.x brokers with it or just include the new openwire
> exception handling only for 6.x along with shared sub OpenWire changes.
>
> Thoughts?

Re: [PROPOSAL] ActiveMQ 6.0.x/6.1.x/... roadmap

[Jean-Baptiste Onofré]

Hi,

That's OK for me. My point is really to incrementally provide new
JMS/Jakarta messaging features on 6.x releases. That's our top
priority.

FYI, I already created a builder to provide a BrokerService on the
branch. I also reduce the dependencies by a "real" plugins system
(more modulith).

Regards
JB

On Wed, Jan 17, 2024 at 1:15 PM Christopher Shannon
 wrote:
>
> I think for each 6.x branch we should just keep implementing more JMS 2 and
> Jakara messaging updates (6.1, 6.2, 6.3) etc and keep working towards being
> fully compatible.
>
> It would make sense to me to release 7.0 when everything is fully
> implemented for Jakarta messaging. I think improving configuration and
> making Spring optional makes sense so it doesn't have to be a dependency.
> Having dependencies is fine and some are necessary and useful (Jetty,
> Guava, etc) but I think in general we have too many dependencies and could
> reduce some which would help with maintenance and CVEs. I think supporting
> JSON or YAML makes sense but I think we should also create a nice Builder
> for creating a broker. Many things have gone to Java configuration and the
> builder pattern is quite common now for configuration so it would be nice
> to have a Builder for creating a broker easily that is embedded as well.
>
> On Tue, Jan 16, 2024 at 9:21 AM Francois Papon 
> wrote:
>
> > Hi JB,
> >
> > Thanks for the roadmap!
> >
> > Just for the note, the 5.x branch will be update only for CVEs purpose?
> > (dependencies or source code)
> >
> > If so, which minor version of 5.x are in the maintenance mode? I guess
> > only the latest 5.18.x right?
> >
> > regards,
> >
> > François
> >
> > On 12/01/2024 19:22, Jean-Baptiste Onofré wrote:
> > > Hi guys,
> > >
> > > Happy new year to all !
> > >
> > > After the festive break, I'm back on ActiveMQ :)
> > > I would like to discuss about the roadmap for ActiveMQ
> > > 6.0.x/6.1.x/6.2.x/7.x(future):
> > >
> > > - For 6.0.x branch, I propose to include fixes and minor dependencies
> > > updates (I have some PRs on the way, Matt also worked on different
> > > topics)
> > > - For 6.1.x branch, I propose to add a new round of JMS 2.x/3.x
> > > features support and include major dependencies updates (if there are
> > > :)). It can also include non breaking change refactoring.
> > > - For 6.2.x branch, I propose to add another round of JMS 2.x/3.x
> > > features support and new major updates compared to 6.1.x
> > > It would be great to target 6.5.x for instance for full JMS 2.x/3.x
> > support.
> > >
> > > - For 7.x, I started a prototype to set Spring as optional, having a
> > > core loader and new configuration format (in addition to activemq.xml,
> > > I have activemq.json and activemq.yml for instance). As this is a
> > > major milestone, we could have some breaking changes. Even if 7.x is
> > > not the top priority for now (I think we have to focus on full JMS 2/3
> > > support right now), it gives perspective to the community.
> > >
> > > Thoughts ?
> > >
> > > Regards
> > > JB
> >

Re: Need your help to assemble the ActiveMQ board report quickly!

[Jean-Baptiste Onofré]

+1

Thanks !

Regards
JB

On Mon, Jan 8, 2024 at 5:38 PM Bruce Snyder  wrote:

> I have now copied the existing report from the file in git (
> https://github.com/apache/activemq-website/blob/main/src/team/reports/DRAFT-ActiveMQ-board-report.txt)
> to the report wizard in Reporter and saved a draft copy but I have not
> published the report yet. I will wait until tomorrow to publish the report
> in order to give others one more day to offer contributions.
>
> Bruce
>
> On Mon, Jan 8, 2024 at 9:31 AM Bruce Snyder 
> wrote:
>
>> I restarted my browser to log in again and now Reporter appears to be
>> working correctly.
>>
>> In the future, we should pursue your idea of asking everyone to add their
>> contributions to Reporter but not publish it.
>>
>> Bruce
>>
>> On Mon, Jan 8, 2024 at 9:23 AM Bruce Snyder 
>> wrote:
>>
>>> Hi JB,
>>>
>>> Ah, that's a great idea and would simplify the collection/submission
>>> process. Unfortunately, it looks like there's something wrong with
>>> Reporter, see the screenshot below:
>>>
>>> [image: image.png]
>>>
>>> Bruce
>>>
>>> On Sat, Jan 6, 2024 at 7:27 AM Jean-Baptiste Onofré 
>>> wrote:
>>>
>>>> Hi Bruce,
>>>>
>>>> I mean we can use draft on reporter to populate the report content
>>>> (instead of website).
>>>> Just a proposal: it would avoid you to copy/paste from website :)
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On Fri, Jan 5, 2024 at 8:04 PM Bruce Snyder 
>>>> wrote:
>>>> >
>>>> > HI JB,
>>>> >
>>>> > I always use Reporter to submit the report.
>>>> >
>>>> > Bruce
>>>> >
>>>> > On Thu, Jan 4, 2024 at 11:04 PM Jean-Baptiste Onofré >>> >
>>>> > wrote:
>>>> >
>>>> > > Hi Bruce
>>>> > >
>>>> > > I committed the Classic part and updated some sections.
>>>> > > By the way, we can use reporter
>>>> > > (https://reporter.apache.org/wizard/?activemq) for the board report
>>>> > > (we can create and save draft and contribute on it, then you can
>>>> just
>>>> > > push the submit button).
>>>> > >
>>>> > > Regards
>>>> > > JB
>>>> > >
>>>> > > On Thu, Jan 4, 2024 at 11:53 PM Bruce Snyder <
>>>> bruce.sny...@gmail.com>
>>>> > > wrote:
>>>> > > >
>>>> > > > Hi folks,
>>>> > > >
>>>> > > > Happy new year! Best wishes in 2024!!
>>>> > > >
>>>> > > > Moments ago, we were reminded that the next ActiveMQ board report
>>>> is due
>>>> > > no
>>>> > > > later than Tuesday, Jan 9. This leaves less than one week, so
>>>> please do
>>>> > > > move quickly with your contributions.
>>>> > > >
>>>> > > > Per the past several reports, please add your contributions to the
>>>> > > > following file in git:
>>>> > > >
>>>> > > >
>>>> > >
>>>> https://github.com/apache/activemq-website/blob/main/src/team/reports/DRAFT-ActiveMQ-board-report.txt
>>>> > > >
>>>> > > > Simply replace the existing reports in the Project Activity with
>>>> the
>>>> > > latest.
>>>> > > >
>>>> > > > Thank you!
>>>> > > >
>>>> > > > Bruce
>>>> > > >
>>>> > > >
>>>> > > > --
>>>> > > > perl -e 'print
>>>> > > >
>>>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E>>> > > > http://bsnyder.org/ <http://bruceblog.org/>
>>>> > >
>>>> >
>>>> >
>>>> > --
>>>> > perl -e 'print
>>>> > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E>>> );'
>>>> > http://bsnyder.org/ <http://bruceblog.org/>
>>>>
>>>
>>>
>>> --
>>> perl -e 'print
>>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E>> http://bsnyder.org/ <http://bruceblog.org/>
>>>
>>
>>
>> --
>> perl -e 'print
>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E> http://bsnyder.org/ <http://bruceblog.org/>
>>
>
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E http://bsnyder.org/ <http://bruceblog.org/>
>

[PROPOSAL] ActiveMQ 6.0.x/6.1.x/... roadmap

[Jean-Baptiste Onofré]

Hi guys,

Happy new year to all !

After the festive break, I'm back on ActiveMQ :)
I would like to discuss about the roadmap for ActiveMQ
6.0.x/6.1.x/6.2.x/7.x(future):

- For 6.0.x branch, I propose to include fixes and minor dependencies
updates (I have some PRs on the way, Matt also worked on different
topics)
- For 6.1.x branch, I propose to add a new round of JMS 2.x/3.x
features support and include major dependencies updates (if there are
:)). It can also include non breaking change refactoring.
- For 6.2.x branch, I propose to add another round of JMS 2.x/3.x
features support and new major updates compared to 6.1.x
It would be great to target 6.5.x for instance for full JMS 2.x/3.x support.

- For 7.x, I started a prototype to set Spring as optional, having a
core loader and new configuration format (in addition to activemq.xml,
I have activemq.json and activemq.yml for instance). As this is a
major milestone, we could have some breaking changes. Even if 7.x is
not the top priority for now (I think we have to focus on full JMS 2/3
support right now), it gives perspective to the community.

Thoughts ?

Regards
JB

CVE-2022-41678: Apache ActiveMQ: Deserialization vulnerability on Jolokia that allows authenticated users to perform RCE

[Jean-Baptiste Onofré]

Severity: Medium

Affected versions:

- Apache ActiveMQ before 5.16.6
- Apache ActiveMQ 5.17.0 before 5.17.4
- Apache ActiveMQ 5.18.0 unaffected
- Apache ActiveMQ 6.0.0 unaffected

Description:

Once an user is authenticated on Jolokia, he can potentially trigger arbitrary 
code execution. 

In details, in ActiveMQ configurations, jetty allows
org.jolokia.http.AgentServlet to handler request to /api/jolokia

org.jolokia.http.HttpRequestHandler#handlePostRequest is able to
create JmxRequest through JSONObject. And calls to
org.jolokia.http.HttpRequestHandler#executeRequest.

Into deeper calling stacks,
org.jolokia.handler.ExecHandler#doHandleRequest is able to invoke
through refection.

And then, RCE is able to be achieved via
jdk.management.jfr.FlightRecorderMXBeanImpl which exists on Java version above 
11.

1 Call newRecording.

2 Call setConfiguration. And a webshell data hides in it.

3 Call startRecording.

4 Call copyTo method. The webshell will be written to a .jsp file.

The mitigation is to restrict (by default) the actions authorized on Jolokia, 
or disable Jolokia.
A more restrictive Jolokia configuration has been defined in default ActiveMQ 
distribution. We encourage users to upgrade to ActiveMQ distributions version 
including updated Jolokia configuration: 5.16.6, 5.17.4, 5.18.0, 6.0.0.

This issue is being tracked as AMQ-9201 

Credit:

wang...@threatbook.cn (finder)
wangzhend...@threatbook.cn (finder)
honglongl...@threatbook.cn (finder)

References:

https://activemq.apache.org/
https://www.cve.org/CVERecord?id=CVE-2022-41678
https://issues.apache.org/jira/browse/AMQ-9201

Re: Regarding ActiveMQ 6.0.1 release

[Jean-Baptiste Onofré]

Hi Abhisek

ActiveMQ 6.0.1 release is currently in voting.

It fixes the issue on ActiveMQ RAR.

It should be officially released during the weekend.

Regards
JB

On Fri, Dec 1, 2023 at 5:18 AM Abhisek Swain
 wrote:
>
> Hi Team,
>
> Can you please update on the ETA or timelines for ActiveMQ 6.0.1 release.
> Please confirm if below fixes are done as part of the release.
>
> 1. Added below dependency in 
> activemq-rar-6.0.0/META-INF/maven/org.apache.activemq/activemq-rar/pom.xml to 
> support jakarta standards.
>
> 
> jakarta.platform
> jakarta.jakartaee-api
> 9.0.0
> provided
> 
> 2. Modified javax.jms to jakarta.jms in activemq-rar-6.0.0/META-INF/ra.xml 
> file.
>
> With Regards,
>
> Abhisek

[RESULT][VOTE] Apache ActiveMQ 6.0.1 release

[Jean-Baptiste Onofré]

Hi guys,

this vote passed with the following result:

+1 (binding): Chris Shannon, JB Onofré, Clebert Suconic
+1 (non binding): Matt Pavlovich, JL Monteiro, Jonathan Gallimore,
François Papon, Gamie Goodyear

I'm promoting the artifacts on Maven Central and dist.apache.org, I
will update Jira and announce the release.

Thanks all for your vote!

Regards
JB

On Thu, Nov 30, 2023 at 2:17 PM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> Following the 6.0.0 release, I submit 6.0.1 to your vote.
>
> This release includes fixes on top of 6.0.0, especially:
> - fix Jakarta namespace in ActiveMQ RA
> - fix OSGi headers in activemq-cf and activemq-jms-pool
> - fix jolokia conf on Windows wrapper
> - fix Jetty secure connector example
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12353594
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1383/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/6.0.1/
>
> Git tag: activemq-6.0.1
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: [HEADS UP] 6.1.0 plans

[Jean-Baptiste Onofré]

Hi

I think it's really important to focus on JMS 2 complete impl for 6.1.0.
That's the most important.

I started to work on some impl, a couple are a little longer to impl,
require tests etc.
I don't think early January is reasonable. I would rather try at the
end of January.

I would rather:
1. Focus on 6.0.2 for fixes (I'm preparing 5.18.x/5.17.x too as they
include fixes as well)
2. Focus on 6.1.0 to complete JMS 2.x support. That's probably the
most important (honestly, I'm not a big fan of JMS 2.x support in
ActiveMQ 6.0.x, it could be confusing for users).

Regards
JB

On Sat, Dec 2, 2023 at 4:10 PM Matt Pavlovich  wrote:
>
> All-
>
> I’ve started organizing some JIRAs for v6.1.0. I’m thinking early-January for 
> release target timeframe.
>
> - Additional JMS 2.0 impls
> - New features for observability
> - Code base modernization
>
> Thanks!
> Matt Pavlovich
>
>

[VOTE] Apache ActiveMQ 6.0.1 release

[Jean-Baptiste Onofré]

Hi guys,

Following the 6.0.0 release, I submit 6.0.1 to your vote.

This release includes fixes on top of 6.0.0, especially:
- fix Jakarta namespace in ActiveMQ RA
- fix OSGi headers in activemq-cf and activemq-jms-pool
- fix jolokia conf on Windows wrapper
- fix Jetty secure connector example

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12353594

Maven Staging Repository:
https://repository.apache.org/content/repositories/orgapacheactivemq-1383/

Dist Staging Repository:
https://dist.apache.org/repos/dist/dev/activemq/activemq/6.0.1/

Git tag: activemq-6.0.1

Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks !
Regards
JB

Re: [VOTE] Apache ActiveMQ 6.0.1 release

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Thu, Nov 30, 2023 at 2:17 PM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> Following the 6.0.0 release, I submit 6.0.1 to your vote.
>
> This release includes fixes on top of 6.0.0, especially:
> - fix Jakarta namespace in ActiveMQ RA
> - fix OSGi headers in activemq-cf and activemq-jms-pool
> - fix jolokia conf on Windows wrapper
> - fix Jetty secure connector example
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12353594
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1383/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/6.0.1/
>
> Git tag: activemq-6.0.1
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: [HEADS UP] 6.1.0 plans

[Jean-Baptiste Onofré]

Ok. But in that case, can we target SMX 7 with full JMS 2 support ?

I think it’s important to have a kind of roadmap.

So let’s use 6.x for incremental work and 7 when complete (without strong
commitment on date).

Regards
JB

Le lun. 4 déc. 2023 à 13:18, Christopher Shannon <
christopher.l.shan...@gmail.com> a écrit :

> I don't see how we can release shared subscription support for 6.1.0 at
> this point. We haven't even come up with a plan of how we are going to
> implement it. There's multiple ways it could be done and probably requires
> protocol changes. We have to decide how much work is done by the broker and
> where.
>
> On Mon, Dec 4, 2023 at 2:18 AM Jean-Baptiste Onofré 
> wrote:
>
> > I think it would better to complete JMS 2 in 6.1.0 including shared topic
> > subscriptions.
> > We already did 6.0.x with partial JMS 2 support, which is so so from user
> > perspective.
> >
> > I would prefer to wait few weeks for 6.1.0 to give us time to complete
> JMS
> > 2.
> >
> > Regards
> > JB
> >
> > Le lun. 4 déc. 2023 à 07:52, Matt Pavlovich  a
> écrit :
> >
> > > Hey JB --
> > >
> > > These JMS 2.0 features are planned for v6.1.0:
> > >
> > > AMQ-8464 PR #1046 6.1.0, 5.18.x  JMSConsumer .receiveBody(Class)
> methods
> > > AMQ-8320 PR #982   6.1.0, 5.18.x  Delivery Delay Support for Message
> > > DeliveryDelay feature
> > > AMQ-8324 PR #1045 6.1.0, 5.18.x  JMSProducer features Completion
> Listener
> > > async send support
> > >
> > > This would just leave Shared Topic Subscriptions, which is currently
> > > planned for v6.2.0.
> > >
> > > AMQ-8323  6.2.0, 5.18.x  Shared Topic Consumer Multi-consumer
> > (queue-like)
> > > consuming from topic subscriptions
> > >
> > > Reference:
> > > https://activemq.apache.org/jms2
> > >
> > > I think this would work well, since we have Virtual Topic support
> (which
> > > is better anyway).
> > >
> > > Thanks,
> > > Matt
> > >
> > >
> > > > On Dec 2, 2023, at 11:00 PM, Jean-Baptiste Onofré 
> > > wrote:
> > > >
> > > > Hi
> > > >
> > > > I think it's really important to focus on JMS 2 complete impl for
> > 6.1.0.
> > > > That's the most important.
> > > >
> > > > I started to work on some impl, a couple are a little longer to impl,
> > > > require tests etc.
> > > > I don't think early January is reasonable. I would rather try at the
> > > > end of January.
> > > >
> > > > I would rather:
> > > > 1. Focus on 6.0.2 for fixes (I'm preparing 5.18.x/5.17.x too as they
> > > > include fixes as well)
> > > > 2. Focus on 6.1.0 to complete JMS 2.x support. That's probably the
> > > > most important (honestly, I'm not a big fan of JMS 2.x support in
> > > > ActiveMQ 6.0.x, it could be confusing for users).
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On Sat, Dec 2, 2023 at 4:10 PM Matt Pavlovich 
> > > wrote:
> > > >>
> > > >> All-
> > > >>
> > > >> I’ve started organizing some JIRAs for v6.1.0. I’m thinking
> > > early-January for release target timeframe.
> > > >>
> > > >> - Additional JMS 2.0 impls
> > > >> - New features for observability
> > > >> - Code base modernization
> > > >>
> > > >> Thanks!
> > > >> Matt Pavlovich
> > > >>
> > > >>
> > >
> > >
> >
>

Re: [HEADS UP] 6.1.0 plans

[Jean-Baptiste Onofré]

Yup agree and it means a new major version imho.



Le lun. 4 déc. 2023 à 13:19, Christopher Shannon <
christopher.l.shan...@gmail.com> a écrit :

> Speaking of protocol changes, if we do generate a new openwire version to
> add shared sub commands we have to actually fix the Openwire generator
> including the CVE issue.
>
> On Mon, Dec 4, 2023 at 7:18 AM Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
> > I don't see how we can release shared subscription support for 6.1.0 at
> > this point. We haven't even come up with a plan of how we are going to
> > implement it. There's multiple ways it could be done and probably
> requires
> > protocol changes. We have to decide how much work is done by the broker
> and
> > where.
> >
> > On Mon, Dec 4, 2023 at 2:18 AM Jean-Baptiste Onofré 
> > wrote:
> >
> >> I think it would better to complete JMS 2 in 6.1.0 including shared
> topic
> >> subscriptions.
> >> We already did 6.0.x with partial JMS 2 support, which is so so from
> user
> >> perspective.
> >>
> >> I would prefer to wait few weeks for 6.1.0 to give us time to complete
> JMS
> >> 2.
> >>
> >> Regards
> >> JB
> >>
> >> Le lun. 4 déc. 2023 à 07:52, Matt Pavlovich  a
> écrit
> >> :
> >>
> >> > Hey JB --
> >> >
> >> > These JMS 2.0 features are planned for v6.1.0:
> >> >
> >> > AMQ-8464 PR #1046 6.1.0, 5.18.x  JMSConsumer .receiveBody(Class)
> methods
> >> > AMQ-8320 PR #982   6.1.0, 5.18.x  Delivery Delay Support for Message
> >> > DeliveryDelay feature
> >> > AMQ-8324 PR #1045 6.1.0, 5.18.x  JMSProducer features Completion
> >> Listener
> >> > async send support
> >> >
> >> > This would just leave Shared Topic Subscriptions, which is currently
> >> > planned for v6.2.0.
> >> >
> >> > AMQ-8323  6.2.0, 5.18.x  Shared Topic Consumer Multi-consumer
> >> (queue-like)
> >> > consuming from topic subscriptions
> >> >
> >> > Reference:
> >> > https://activemq.apache.org/jms2
> >> >
> >> > I think this would work well, since we have Virtual Topic support
> (which
> >> > is better anyway).
> >> >
> >> > Thanks,
> >> > Matt
> >> >
> >> >
> >> > > On Dec 2, 2023, at 11:00 PM, Jean-Baptiste Onofré 
> >> > wrote:
> >> > >
> >> > > Hi
> >> > >
> >> > > I think it's really important to focus on JMS 2 complete impl for
> >> 6.1.0.
> >> > > That's the most important.
> >> > >
> >> > > I started to work on some impl, a couple are a little longer to
> impl,
> >> > > require tests etc.
> >> > > I don't think early January is reasonable. I would rather try at the
> >> > > end of January.
> >> > >
> >> > > I would rather:
> >> > > 1. Focus on 6.0.2 for fixes (I'm preparing 5.18.x/5.17.x too as they
> >> > > include fixes as well)
> >> > > 2. Focus on 6.1.0 to complete JMS 2.x support. That's probably the
> >> > > most important (honestly, I'm not a big fan of JMS 2.x support in
> >> > > ActiveMQ 6.0.x, it could be confusing for users).
> >> > >
> >> > > Regards
> >> > > JB
> >> > >
> >> > > On Sat, Dec 2, 2023 at 4:10 PM Matt Pavlovich 
> >> > wrote:
> >> > >>
> >> > >> All-
> >> > >>
> >> > >> I’ve started organizing some JIRAs for v6.1.0. I’m thinking
> >> > early-January for release target timeframe.
> >> > >>
> >> > >> - Additional JMS 2.0 impls
> >> > >> - New features for observability
> >> > >> - Code base modernization
> >> > >>
> >> > >> Thanks!
> >> > >> Matt Pavlovich
> >> > >>
> >> > >>
> >> >
> >> >
> >>
> >
>

Re: [HEADS UP] 6.1.0 plans

[Jean-Baptiste Onofré]

I think it would better to complete JMS 2 in 6.1.0 including shared topic
subscriptions.
We already did 6.0.x with partial JMS 2 support, which is so so from user
perspective.

I would prefer to wait few weeks for 6.1.0 to give us time to complete JMS
2.

Regards
JB

Le lun. 4 déc. 2023 à 07:52, Matt Pavlovich  a écrit :

> Hey JB --
>
> These JMS 2.0 features are planned for v6.1.0:
>
> AMQ-8464 PR #1046 6.1.0, 5.18.x  JMSConsumer .receiveBody(Class) methods
> AMQ-8320 PR #982   6.1.0, 5.18.x  Delivery Delay Support for Message
> DeliveryDelay feature
> AMQ-8324 PR #1045 6.1.0, 5.18.x  JMSProducer features Completion Listener
> async send support
>
> This would just leave Shared Topic Subscriptions, which is currently
> planned for v6.2.0.
>
> AMQ-8323  6.2.0, 5.18.x  Shared Topic Consumer Multi-consumer (queue-like)
> consuming from topic subscriptions
>
> Reference:
> https://activemq.apache.org/jms2
>
> I think this would work well, since we have Virtual Topic support (which
> is better anyway).
>
> Thanks,
> Matt
>
>
> > On Dec 2, 2023, at 11:00 PM, Jean-Baptiste Onofré 
> wrote:
> >
> > Hi
> >
> > I think it's really important to focus on JMS 2 complete impl for 6.1.0.
> > That's the most important.
> >
> > I started to work on some impl, a couple are a little longer to impl,
> > require tests etc.
> > I don't think early January is reasonable. I would rather try at the
> > end of January.
> >
> > I would rather:
> > 1. Focus on 6.0.2 for fixes (I'm preparing 5.18.x/5.17.x too as they
> > include fixes as well)
> > 2. Focus on 6.1.0 to complete JMS 2.x support. That's probably the
> > most important (honestly, I'm not a big fan of JMS 2.x support in
> > ActiveMQ 6.0.x, it could be confusing for users).
> >
> > Regards
> > JB
> >
> > On Sat, Dec 2, 2023 at 4:10 PM Matt Pavlovich 
> wrote:
> >>
> >> All-
> >>
> >> I’ve started organizing some JIRAs for v6.1.0. I’m thinking
> early-January for release target timeframe.
> >>
> >> - Additional JMS 2.0 impls
> >> - New features for observability
> >> - Code base modernization
> >>
> >> Thanks!
> >> Matt Pavlovich
> >>
> >>
>
>

Re: [VOTE] Apache ActiveMQ Artemis 2.32.0

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Jan 24, 2024 at 10:29 PM Clebert Suconic
 wrote:
>
> I would like to propose an Apache ActiveMQ Artemis 2.32.0 release.
>
>
> I would like to highlight the following for this release:
>
>
> * Mirrored Core Messages can now be sent in their native format
> without conversions
> * Mirror has been extensively tested and improved in stability
> * ActiveMQ Artemis has now adopted more inclusive language definitions.
> * The examples are now part of its own repository:
> https://github.com/apache/activemq-artemis-examples/
>
>
> And bug fixes and other improvements as usually. for the full JIRA
> report refer to:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920=12353769
>
>
>
> Ths git commit report is here:
> https://activemq.apache.org/components/artemis/download/commit-report-2.32.0
>
>
> Source and binary distributions can be found here:
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.32.0
>
> The Maven staging repository is here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1384
>
>
>
> If you would like to validate the release:
> https://activemq.apache.org/components/artemis/documentation/hacking-guide/#validating-releases
>
>
>
>
> It is tagged in the git repo as 2.32.0
>
>
> [ ] +1 approve this release
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)

Re: [HEADS-UP] ActiveMQ Artemis release in Wed...

[Jean-Baptiste Onofré]

It sounds good to me.

Thanks
Regards
JB

On Mon, Jan 22, 2024 at 8:48 PM Clebert Suconic
 wrote:
>
> I'm aiming to release on Wed Morning... willing to delay a day if
> anyone needs it... (please ping me on this thread if a delay is
> needed).
>
>
> Otherwise if you get your PRs merged tomorrow and before then they
> will be part of the release :)
>
> --
> Clebert Suconic

Re: [VOTE] Apache ActiveMQ 6.0.0 release (take #2)

[Jean-Baptiste Onofré]

+1 (binding)

I did the same tests I did during release preparation :)
Some fixes/polish to do for 6.0.1 but nothing blocker :)

Regards
JB

On Tue, Nov 14, 2023 at 11:05 AM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> After several weeks of work, I'm glad to submit Apache ActiveMQ 6.0.0
> release to your vote.
>
> This release is a big milestone for ActiveMQ, starting the new 6.x series.
>
> It's the second RC where we fixed AMQ-9388 detected during the first vote.
>
> This release includes a bunch of changes, especially:
> - Jakarta Messaging 3.1, JMS 2.0, JMS 1.1 (still work to do to be
> fully complete)
> - Jakarta EE namespace support
> - JDK17/21 support
> - Spring 6.x
> - Jetty 11.x
> - Apache Camel 4.x
> - Jolokia 2.x
> - and much much more!
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352570
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1381/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/6.0.0/
>
> Git tag: activemq-6.0.0
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

Re: JMS 2 and JMS 3.1 status

[Jean-Baptiste Onofré]

Hi,

The first support has started in ActiveMQ 6.0.0 currently in vote.
However, some features are not fully implemented, it's planned for
6.1/6.2 releases.

For instance, regarding Shared Durable Topic, you can see some method
throwing IllegalStateException("Operation not supported by a
TopicSession").
That's the case for the methods from JMS 2.0/3.1 and not yet
implemented (like createSharedDurableConsumer for example).

To be honest, I'm not a super fan of what we did here, I think it
would have been better to have a full running implementation. As we
wanted to have JMS 2.0/3.1 (and so Jakarta namespace support), we did
this approach in 5.18 (in the activemq-client-jakarta module) and now
in 6.0.0 (directly in activemq-client).
Now, we will implement method by method.

To be concrete on your question, Shared Durable Topic feature will be
fully implemented in 6.1.0.

Regards
JB

On Thu, Nov 16, 2023 at 12:21 PM Jean-Louis Monteiro
 wrote:
>
> Hi all,
>
> Any information or plans for the JMS 2.0 / JMS 3.1 implementation in
> ActiveMQ Classic?
> I'm more interested in the Shared Durable Topic feature.
>
> With some guidance or help, I can probably help on this.
>
> Thanks
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com

Re: JMS 2 and JMS 3.1 status

[Jean-Baptiste Onofré]

We plan 6.0.1 pretty quickly but no plan yet about 6.1.0.

I plan to work on an implementation plan with detailed
approaches/proposals (of course when 6.0.0 will be out ;) ). I will
share on the mailing list for discussion.

Then, we can define a roadmap and "attach" to releases.

Regards
JB

On Thu, Nov 16, 2023 at 3:05 PM Christopher Shannon
 wrote:
>
> I don't think it is very likely shared durable topics are going to be
> available in 6.1.0, unless we don't plan to release 6.1.0 for a long time.
>
> Shared subscriptions are going to be a decent amount of work to get correct
> as I don't think we should just hack the client to created a virtual topic
> as then it's entirely up to the client to manage things and there's no
> state tracking on the broker side. To do it properly the broker needs to
> handle mapping the subscriptions to queues transparently. We can  leverage
> composite destinations and virtual subs but we still need to figure out how
> this is going to be mapped and tracked by the broker when a client makes a
> shared subscription request. There's issues to work out as well based on
> the spec and what is and isn't allowed. The cleanest solution would be a
> new OpenWire version with a new shared sub name.
>
> So my point is, I don't think this feature is particularly close to being
> done considering no one is actually working on it and there are likely
> probably going to be other issues that come up that require us to release
> 6.1.0 much faster than shared durables or shared subs will be ready so the
> only thing we can really say is it will be available at some point in a 6.x
> release
>
> On Thu, Nov 16, 2023 at 8:41 AM Jean-Baptiste Onofré 
> wrote:
>
> > Hi,
> >
> > The first support has started in ActiveMQ 6.0.0 currently in vote.
> > However, some features are not fully implemented, it's planned for
> > 6.1/6.2 releases.
> >
> > For instance, regarding Shared Durable Topic, you can see some method
> > throwing IllegalStateException("Operation not supported by a
> > TopicSession").
> > That's the case for the methods from JMS 2.0/3.1 and not yet
> > implemented (like createSharedDurableConsumer for example).
> >
> > To be honest, I'm not a super fan of what we did here, I think it
> > would have been better to have a full running implementation. As we
> > wanted to have JMS 2.0/3.1 (and so Jakarta namespace support), we did
> > this approach in 5.18 (in the activemq-client-jakarta module) and now
> > in 6.0.0 (directly in activemq-client).
> > Now, we will implement method by method.
> >
> > To be concrete on your question, Shared Durable Topic feature will be
> > fully implemented in 6.1.0.
> >
> > Regards
> > JB
> >
> > On Thu, Nov 16, 2023 at 12:21 PM Jean-Louis Monteiro
> >  wrote:
> > >
> > > Hi all,
> > >
> > > Any information or plans for the JMS 2.0 / JMS 3.1 implementation in
> > > ActiveMQ Classic?
> > > I'm more interested in the Shared Durable Topic feature.
> > >
> > > With some guidance or help, I can probably help on this.
> > >
> > > Thanks
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> >

Re: [ANN] Apache ActiveMQ 6.0.0 has been released!

[Jean-Baptiste Onofré]

Hi

No ActiveMQ 6.0.0 is not Artemis. It’s ActiveMQ « classic » updated.

For me, Artemis and ActiveMQ are two projects in the ActiveMQ umbrella,
each with its own roadmap and release cycle.

Regards
JB

Le lun. 20 nov. 2023 à 08:52, Modanese, Riccardo
 a écrit :

> Hello,
> good news!
>
> So Apache Artemis is definitively mature and become ActiveMQ 6 (instead of
> ActiveMQ Artemis 2.x)?
> Isn’t it published yet to Maven repo (
> https://mvnrepository.com/artifact/org.apache.activemq/apache-activemq)?
> Latest 6.0 is several years old.
>
> Regards,
>
> Riccardo Modanese
> From: Jean-Baptiste Onofré 
> Date: Sunday, 19 November 2023 at 17:40
> To: dev@activemq.apache.org ,
> us...@activemq.apache.org 
> Subject: [ANN] Apache ActiveMQ 6.0.0 has been released!
> After several weeks (months ?) of work, the ActiveMQ team is pleased
> to announce Apache ActiveMQ 6.0.0 release.
>
> It's a major milestone for the project, starting the 6.x series, and
> bringing:
> - Jakarta Messaging 3.1, JMS 2.0 support (new features will come in
> the 6.x series)
> - Jakarta EE namespace support
> - JDK17/20/21 support
> - Spring 6.x support
> - Jetty 11.x support
> - Apache Camel 4.x support
> - Jolokia 2.x support
> - and much more !
>
> You can find details on the Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352570
>
> You can download ActiveMQ 6.0.0 here:
> https://activemq.apache.org/components/classic/download/
>
> Enjoy !
>
> Regards
> --
> The Apache ActiveMQ team
>

[ANN] Apache ActiveMQ 6.0.0 has been released!

[Jean-Baptiste Onofré]

After several weeks (months ?) of work, the ActiveMQ team is pleased
to announce Apache ActiveMQ 6.0.0 release.

It's a major milestone for the project, starting the 6.x series, and bringing:
- Jakarta Messaging 3.1, JMS 2.0 support (new features will come in
the 6.x series)
- Jakarta EE namespace support
- JDK17/20/21 support
- Spring 6.x support
- Jetty 11.x support
- Apache Camel 4.x support
- Jolokia 2.x support
- and much more !

You can find details on the Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352570

You can download ActiveMQ 6.0.0 here:
https://activemq.apache.org/components/classic/download/

Enjoy !

Regards
--
The Apache ActiveMQ team

Re: [HEADS UP] Branching 6.0.x and renumbering main 6.1.0-SNAPSHOT

[Jean-Baptiste Onofré]

Done !

Thanks
Regards
JB

On Mon, Nov 20, 2023 at 4:09 PM Matt Pavlovich  wrote:
>
> Hey JB-
>
> Sounds good! Go for it.
>
> Thanks,
> Matt Pavlovich
>
> > On Nov 20, 2023, at 8:58 AM, Jean-Baptiste Onofré  wrote:
> >
> > Hi
> >
> > Actually, I'm on it as I'm starting to prepare 6.0.1-SNAPSHOT.
> >
> > Give me 10mn and I will push it.
> >
> > Regards
> > JB
> >
> > On Mon, Nov 20, 2023 at 3:52 PM Matt Pavlovich  wrote:
> >>
> >> Heads up—
> >>
> >> I’m planning to branch main as activemq-6.0.x and then renumber main to 
> >> 6.1.0-SNAPSHOT to support new features in development.
> >>
> >> Thanks,
> >> Matt Pavlovich
> >>
>

Re: [ANN] Apache ActiveMQ 6.0.0 has been released!

[Jean-Baptiste Onofré]

You are right, that was the initial plan. But, as both Artemis and
ActiveMQ are active, with active communities, we decided to be back on
our "regular" versioning at ActiveMQ. So ActiveMQ "Classic" will use
6,7,8,9,10, ... versioning, Artemis can do the same, so we have two
different subprojects.

Regards
JB

On Mon, Nov 20, 2023 at 11:11 AM Modanese, Riccardo
 wrote:
>
> Thanks for the clarification.
> From my knowledge there was a plan to “rename” Artemis as Classic.
>
> From [1]
> “Once Artemis reaches a sufficient level of feature parity with the "Classic" 
> code-base it will become the next major version of ActiveMQ.”
>
> It means will be ActiveMQ 7?
>
> [1] https://activemq.apache.org/
>
> Regards,
>
> Riccardo
>
> From: Jean-Baptiste Onofré 
> Date: Monday, 20 November 2023 at 09:17
> To: us...@activemq.apache.org 
> Cc: dev@activemq.apache.org 
> Subject: Re: [ANN] Apache ActiveMQ 6.0.0 has been released!
> Hi
>
> No ActiveMQ 6.0.0 is not Artemis. It’s ActiveMQ « classic » updated.
>
> For me, Artemis and ActiveMQ are two projects in the ActiveMQ umbrella,
> each with its own roadmap and release cycle.
>
> Regards
> JB
>
> Le lun. 20 nov. 2023 à 08:52, Modanese, Riccardo
>  a écrit :
>
> > Hello,
> > good news!
> >
> > So Apache Artemis is definitively mature and become ActiveMQ 6 (instead of
> > ActiveMQ Artemis 2.x)?
> > Isn’t it published yet to Maven repo (
> > https://mvnrepository.com/artifact/org.apache.activemq/apache-activemq)?
> > Latest 6.0 is several years old.
> >
> > Regards,
> >
> > Riccardo Modanese
> > From: Jean-Baptiste Onofré 
> > Date: Sunday, 19 November 2023 at 17:40
> > To: dev@activemq.apache.org ,
> > us...@activemq.apache.org 
> > Subject: [ANN] Apache ActiveMQ 6.0.0 has been released!
> > After several weeks (months ?) of work, the ActiveMQ team is pleased
> > to announce Apache ActiveMQ 6.0.0 release.
> >
> > It's a major milestone for the project, starting the 6.x series, and
> > bringing:
> > - Jakarta Messaging 3.1, JMS 2.0 support (new features will come in
> > the 6.x series)
> > - Jakarta EE namespace support
> > - JDK17/20/21 support
> > - Spring 6.x support
> > - Jetty 11.x support
> > - Apache Camel 4.x support
> > - Jolokia 2.x support
> > - and much more !
> >
> > You can find details on the Release Notes:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352570
> >
> > You can download ActiveMQ 6.0.0 here:
> > https://activemq.apache.org/components/classic/download/
> >
> > Enjoy !
> >
> > Regards
> > --
> > The Apache ActiveMQ team
> >

Re: [HEADS UP] Branching 6.0.x and renumbering main 6.1.0-SNAPSHOT

[Jean-Baptiste Onofré]

Hi

Actually, I'm on it as I'm starting to prepare 6.0.1-SNAPSHOT.

Give me 10mn and I will push it.

Regards
JB

On Mon, Nov 20, 2023 at 3:52 PM Matt Pavlovich  wrote:
>
> Heads up—
>
> I’m planning to branch main as activemq-6.0.x and then renumber main to 
> 6.1.0-SNAPSHOT to support new features in development.
>
> Thanks,
> Matt Pavlovich
>

[RESULT][VOTE] Apache ActiveMQ 6.0.0 release (take #2)

[Jean-Baptiste Onofré]

Hi all,

this vote passed with the following result:

+1 (binding): Chris Shannon, JB Onofré, Art Naseef
+1 (non binding): François Papon, Aleksei Eraskin, JL Monteiro, Jamie
Goodyear, Matt Pavlovich

I'm promoting the artifacts on Maven Central and dist.apache.org.
I will merge the website related PR and I will update the website with
javadoc, announcement, etc.
Then, I will do the announcement.

Thanks all for your vote !

Regards
JB

On Tue, Nov 14, 2023 at 11:05 AM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> After several weeks of work, I'm glad to submit Apache ActiveMQ 6.0.0
> release to your vote.
>
> This release is a big milestone for ActiveMQ, starting the new 6.x series.
>
> It's the second RC where we fixed AMQ-9388 detected during the first vote.
>
> This release includes a bunch of changes, especially:
> - Jakarta Messaging 3.1, JMS 2.0, JMS 1.1 (still work to do to be
> fully complete)
> - Jakarta EE namespace support
> - JDK17/21 support
> - Spring 6.x
> - Jetty 11.x
> - Apache Camel 4.x
> - Jolokia 2.x
> - and much much more!
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352570
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1381/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/6.0.0/
>
> Git tag: activemq-6.0.0
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

[CANCEL][VOTE] Apache ActiveMQ 6.0.0 release

[Jean-Baptiste Onofré]

Hi guys,

We found a blocker in this release:
https://issues.apache.org/jira/browse/AMQ-9388

I cancel this vote to fix and prepare a new one.

Regards
JB

On Sun, Nov 12, 2023 at 8:41 AM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> After several weeks of work, I'm glad to submit Apache ActiveMQ 6.0.0
> release to your vote.
>
> This release is a big milestone for ActiveMQ, starting the new 6.x series.
> This release includes a bunch of changes, especially:
> - Jakarta Messaging 3.1, JMS 2.0, JMS 1.1 (still work to do to be
> fully complete)
> - Jakarta EE namespace support
> - JDK17/21 support
> - Spring 6.x
> - Jetty 11.x
> - Apache Camel 4.x
> - Jolokia 2.x
> - and much much more!
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352570
>
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1380/
>
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/6.0.0/
>
> Git tag: activemq-6.0.0
>
> Please vote to approve this release:
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks !
> Regards
> JB

[VOTE] Apache ActiveMQ 6.0.0 release (take #2)

[Jean-Baptiste Onofré]

Hi guys,

After several weeks of work, I'm glad to submit Apache ActiveMQ 6.0.0
release to your vote.

This release is a big milestone for ActiveMQ, starting the new 6.x series.

It's the second RC where we fixed AMQ-9388 detected during the first vote.

This release includes a bunch of changes, especially:
- Jakarta Messaging 3.1, JMS 2.0, JMS 1.1 (still work to do to be
fully complete)
- Jakarta EE namespace support
- JDK17/21 support
- Spring 6.x
- Jetty 11.x
- Apache Camel 4.x
- Jolokia 2.x
- and much much more!

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12352570

Maven Staging Repository:
https://repository.apache.org/content/repositories/orgapacheactivemq-1381/

Dist Staging Repository:
https://dist.apache.org/repos/dist/dev/activemq/activemq/6.0.0/

Git tag: activemq-6.0.0

Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks !
Regards
JB