Re: Unofficial ActiveMQ Artemis .NET Client

[Michael André Pearce]

My points on this is two parts:


1) This only works for Artemis if this was the case, i would have expected an 
"Artemis" specific client to work on the CORE protocol level.
2) The point of NMS is its an API, and actually the NMS AMQP client has tested 
compatibility with ActiveMQ Classic, ActiveMQ Artemis, Solace, and because its 
agnostic should work with any other AMQP broker, thats working like with QPID 
clients. 


The main short coming of NMS atm is lack of task async api, and thats been 
acknowledged, but this is being added with the NMS 2.0 work, thats in progress 
as you know thats in PR.


Obviously there's nothing stopping you continuing to maintain the client 
externally as its own project.


For these reasons im personally not keen on supporting this/bringing this under 
the Apache ActiveMQ sub banner, i dont have the time, id rather if people feel 
something is missing in existing solutions, that they contribute there.



On 4 February 2021 at 20:38, Havret  wrote:


Hi Justin,

You made an excellent point. I will try to answer as thoroughly as I can.

AmqpNetLite is a .NET implementation of AMQP 1.0 protocol. It gives you
full control and all the building blocks you may need to communicate using
AMQP 1.0. Unfortunately, to use it properly, you need to write quite a lot
of tedious boilerplate code. For instance, in order to create a connection,
you would need to write sth along these lines:
https://github.com/Havret/dotnet-activemq-artemis-client/blob/0c7a165c77744ff1d0042511e6d5afc44a3e38e2/src/ActiveMQ.Artemis.Client/Builders/ConnectionBuilder.cs#L10-L53

The same rule applies to other resources like producers, consumers,
sessions, etc.

Having all this implemented one would only utilize the most basic features
of ActiveMQ Artemis. There is however a good chunk of functionalities that
require subtle knowledge specific to ActiveMQ Artemis implementation built
on top of this protocol. For example things like scheduled message
delivery, scheduled delivery delay, message selectors, attaching to
address/queue based on routing type, fully qualified queue names, just to
name a few. All these bits are not part of the original protocol and are
proprietary to this specific implementation.

My library packs all these scraps of knowledge into a simple strongly typed
SDK, that can be used by any developer without the knowledge that to define
a message selector on your consumer you need to add to FilterSet property
of Source frame described value apache.org:
selector-filter:string=0x468C0004L.

Besides that, it adds things that are not included in the raw AmqpNetLite
by design but are pretty useful in real-life situations, like automatic
recovery.

The thing that I personally (and my fellow .NET developers :)) missed the
most after switching from RabbitMQ to ActiveMQ Artemis is the topology
management functionality built right into the client. In RabbitMQ .NET
client, this is a first-class citizen, and there are extremely popular
frameworks like NServiceBus and MassTransit that make heavy use of it.
JMS/NMS 2.0 features like durable subscriptions try to compensate for the
lack of this functionality to some extent, but unfortunately are far too
limited. So this is the other thing that this library introduces, and that
was welcomed with great enthusiasm when I showed it to my colleagues.

As the lib doesn't implement nms/jms it is much simpler. You don't need a
spring container, caching connection factories, single connection
factories, etc, and the knowledge of how to configure and use them. You
just need to create your producers and consumers and you're ready to go.
Everything is thread-safe, so you don't need to worry about creating
explicit memory barriers, etc.

I started this library as a playground for experimentations while
implementing nms-amqp, but in time it evolved into sth else. My current
goal is to create a simple well-documented library that will make the
adaptation of ActiveMQ Artemis as simple and non-intrusive as possible.

I hope my reply is not too chaotic and answers your question at least to
some extent.

All the best,
Krzysztof

On Thu, Feb 4, 2021 at 3:14 AM Justin Bertram  wrote:


The docs [1] indicate that the client is "a very lightweight wrapper around
AmqpNetLite." If that is the case why is it advertised as the "ActiveMQ
Artemis Client for .NET"? Couldn't it be used for *any* AMQP 1.0 use-case?
How is it different from AmqpNetLite? What specifically does the wrapper
provide?


Generally speaking, one of the nice things about implementing standardized
protocols in the broker is that anybody can implement clients and those
clients exist completely independent of the broker. There are *lots* of
clients for STOMP, AMQP, and MQTT written in lots of different languages
for all kinds of different platforms. If we cited your client in the
documentation then someone could logically ask why we don't also cite
client X in the documentation as well. Clients come and go over 

Re: Unofficial ActiveMQ Artemis .NET Client

[Havret]

Hi Mike, thanks for the feedback,

I totally get it. My main inspiration in this regard was RabbitMQ .NET
Client, which of course works on AMQP 0.9.1 and (AMQP 1.0), but actually
uses a proprietary protocol build on top of the mentioned (the same as
ActiveMQ Artemis). Theoretically one could use NMS to talk to RabbitMQ but
nobody does that. At least in the .NET world. This library is not to
replace NMS.AMQP, it just to give the devs a simpler alternative. It is
something between AmqpNetLite which is too low level and NMS.AMQP which is
too overengineered (and constrained with many JMS-specific requirements),
has a really high learning curve and requires additional tooling (spring
container) just to start using it.

I asked my initial question because I was looking for ActiveMQ Artemis
counterpart of this page https://www.rabbitmq.com/devtools.html I didn't
find one, so I asked.

On Fri, Feb 5, 2021 at 10:37 AM Michael André Pearce
 wrote:

> My points on this is two parts:
>
> 1) This only works for Artemis if this was the case, i would have expected
> an "Artemis" specific client to work on the CORE protocol level.
> 2) The point of NMS is its an API, and actually the NMS AMQP client has
> tested compatibility with ActiveMQ Classic, ActiveMQ Artemis, Solace, and
> because its agnostic should work with any other AMQP broker, thats working
> like with QPID clients.
>
> The main short coming of NMS atm is lack of task async api, and thats been
> acknowledged, but this is being added with the NMS 2.0 work, thats in
> progress as you know thats in PR.
>
> Obviously there's nothing stopping you continuing to maintain the client
> externally as its own project.
>
> For these reasons im personally not keen on supporting this/bringing this
> under the Apache ActiveMQ sub banner, i dont have the time, id rather if
> people feel something is missing in existing solutions, that they
> contribute there.
>
>
> On 4 February 2021 at 20:38, Havret  wrote:
>
> Hi Justin,
>
> You made an excellent point. I will try to answer as thoroughly as I can.
>
> AmqpNetLite is a .NET implementation of AMQP 1.0 protocol. It gives you
> full control and all the building blocks you may need to communicate using
> AMQP 1.0. Unfortunately, to use it properly, you need to write quite a lot
> of tedious boilerplate code. For instance, in order to create a connection,
> you would need to write sth along these lines:
>
> https://github.com/Havret/dotnet-activemq-artemis-client/blob/0c7a165c77744ff1d0042511e6d5afc44a3e38e2/src/ActiveMQ.Artemis.Client/Builders/ConnectionBuilder.cs#L10-L53
>
> The same rule applies to other resources like producers, consumers,
> sessions, etc.
>
> Having all this implemented one would only utilize the most basic features
> of ActiveMQ Artemis. There is however a good chunk of functionalities that
> require subtle knowledge specific to ActiveMQ Artemis implementation built
> on top of this protocol. For example things like scheduled message
> delivery, scheduled delivery delay, message selectors, attaching to
> address/queue based on routing type, fully qualified queue names, just to
> name a few. All these bits are not part of the original protocol and are
> proprietary to this specific implementation.
>
> My library packs all these scraps of knowledge into a simple strongly typed
> SDK, that can be used by any developer without the knowledge that to define
> a message selector on your consumer you need to add to FilterSet property
> of Source frame described value apache.org:
> selector-filter:string=0x468C0004L.
>
> Besides that, it adds things that are not included in the raw AmqpNetLite
> by design but are pretty useful in real-life situations, like automatic
> recovery.
>
> The thing that I personally (and my fellow .NET developers :)) missed the
> most after switching from RabbitMQ to ActiveMQ Artemis is the topology
> management functionality built right into the client. In RabbitMQ .NET
> client, this is a first-class citizen, and there are extremely popular
> frameworks like NServiceBus and MassTransit that make heavy use of it.
> JMS/NMS 2.0 features like durable subscriptions try to compensate for the
> lack of this functionality to some extent, but unfortunately are far too
> limited. So this is the other thing that this library introduces, and that
> was welcomed with great enthusiasm when I showed it to my colleagues.
>
> As the lib doesn't implement nms/jms it is much simpler. You don't need a
> spring container, caching connection factories, single connection
> factories, etc, and the knowledge of how to configure and use them. You
> just need to create your producers and consumers and you're ready to go.
> Everything is thread-safe, so you don't need to worry about creating
> explicit memory barriers, etc.
>
> I started this library as a playground for experimentations while
> implementing nms-amqp, but in time it evolved into sth else. My current
> goal is to create a simple 

Re: Unofficial ActiveMQ Artemis .NET Client

[Michael André Pearce]

You can actually send management messages in via NMS/JMS, so again not so sure 
we need to be maintaining two clients here.


I would expect if something to do some extra bits, via management address, to 
make some kind of management client, that a wrapper over the NMS could be done 
there.


Again an i re-iterate, i would encourage contribution to extend the NMS client 
where needed here, not divergence.


On a separate note, re just adding docs pointing to your project, which is a 
not an ASF sister project, I think we want to be careful going down that route 
too much, as an Apache project it gets us into some murky waters, i don't think 
we need or want to go down.


e.g. we then open ourselves to having to accept every request to link to a 
client project, to keep things fair, and then further what about propriety 
clients, that would end up in a very odd position, im not sure where we even 
stand, with an Apache ASF project essentially promoting a NON open source tool, 
should someone then insist we promote theirs too. 


If you look at Kafka eco system, it provides very few clients, but in actual 
fact it is well known there are clients in nearly all languages, many/most 
actually developed outside the Apache Kafka project, and even in some cases for 
the same language there are a couple of clients on offer. But the Apache Kafka 
project does not list or promote those.


Best
M



















On 5 February 2021 at 10:44, Havret  wrote:


Hi Mike, thanks for the feedback,

I totally get it. My main inspiration in this regard was RabbitMQ .NET
Client, which of course works on AMQP 0.9.1 and (AMQP 1.0), but actually
uses a proprietary protocol build on top of the mentioned (the same as
ActiveMQ Artemis). Theoretically one could use NMS to talk to RabbitMQ but
nobody does that. At least in the .NET world. This library is not to
replace NMS.AMQP, it just to give the devs a simpler alternative. It is
something between AmqpNetLite which is too low level and NMS.AMQP which is
too overengineered (and constrained with many JMS-specific requirements),
has a really high learning curve and requires additional tooling (spring
container) just to start using it.

I asked my initial question because I was looking for ActiveMQ Artemis
counterpart of this page https://www.rabbitmq.com/devtools.html I didn't
find one, so I asked.

On Fri, Feb 5, 2021 at 10:37 AM Michael André Pearce
 wrote:


My points on this is two parts:


1) This only works for Artemis if this was the case, i would have expected
an "Artemis" specific client to work on the CORE protocol level.
2) The point of NMS is its an API, and actually the NMS AMQP client has
tested compatibility with ActiveMQ Classic, ActiveMQ Artemis, Solace, and
because its agnostic should work with any other AMQP broker, thats working
like with QPID clients.


The main short coming of NMS atm is lack of task async api, and thats been
acknowledged, but this is being added with the NMS 2.0 work, thats in
progress as you know thats in PR.


Obviously there's nothing stopping you continuing to maintain the client
externally as its own project.


For these reasons im personally not keen on supporting this/bringing this
under the Apache ActiveMQ sub banner, i dont have the time, id rather if
people feel something is missing in existing solutions, that they
contribute there.




On 4 February 2021 at 20:38, Havret  wrote:


Hi Justin,


You made an excellent point. I will try to answer as thoroughly as I can.


AmqpNetLite is a .NET implementation of AMQP 1.0 protocol. It gives you
full control and all the building blocks you may need to communicate using
AMQP 1.0. Unfortunately, to use it properly, you need to write quite a lot
of tedious boilerplate code. For instance, in order to create a connection,
you would need to write sth along these lines:


https://github.com/Havret/dotnet-activemq-artemis-client/blob/0c7a165c77744ff1d0042511e6d5afc44a3e38e2/src/ActiveMQ.Artemis.Client/Builders/ConnectionBuilder.cs#L10-L53


The same rule applies to other resources like producers, consumers,
sessions, etc.


Having all this implemented one would only utilize the most basic features
of ActiveMQ Artemis. There is however a good chunk of functionalities that
require subtle knowledge specific to ActiveMQ Artemis implementation built
on top of this protocol. For example things like scheduled message
delivery, scheduled delivery delay, message selectors, attaching to
address/queue based on routing type, fully qualified queue names, just to
name a few. All these bits are not part of the original protocol and are
proprietary to this specific implementation.


My library packs all these scraps of knowledge into a simple strongly typed
SDK, that can be used by any developer without the knowledge that to define
a message selector on your consumer you need to add to FilterSet property
of Source frame described value apache.org:
selector-filter:string=0x468C0004L.


Besides that, 

Re: Website update, announcement, CVE

[Timothy Bish]

Did I miss the announcement going out?  Seems like it should have been done
by now but I don't see it, although website appears to but updated now.

On Fri, Jan 29, 2021 at 8:44 AM Jean-Baptiste Onofre 
wrote:

> Thanks Robbie,
>
> I was about to update website. Thanks for catching this !
>
> I will move forward on announcement.
>
> Regards
> JB
>
> > Le 29 janv. 2021 à 14:38, Robbie Gemmell  a
> écrit :
> >
> > I have just updated the website to change the download page to 5.16.1,
> > add the 5.16.1 release page (which notes the announced CVE Gary
> > already updated the site with), and fix the broken links for the
> > 5.16.0 page. The site should be updated before the prior release is
> > removed from mirrors, or it breaks the links.
> >
> > I leave any further tweaks and announcements needed to you.
> >
> > On Thu, 28 Jan 2021 at 05:00, Jean-Baptiste Onofre 
> wrote:
> >>
> >> Hi guys,
> >>
> >> Sorry, I’m late about website update, announcement and CVE publication
> for ActiveMQ 5.16.1.
> >>
> >> I will fix that asap (at least during the week end).
> >>
> >> Sorry about that,
> >> Regards
> >> JB
>
>

-- 
--
Tim Bish

Re: Website update, announcement, CVE

[Jean-Baptiste Onofre]

Hi,

Let me check (I did it but maybe forgot to send ;)).

I will fix that if it didn’t go.

Regards
JB

> Le 5 févr. 2021 à 16:46, Timothy Bish  a écrit :
> 
> Did I miss the announcement going out?  Seems like it should have been done
> by now but I don't see it, although website appears to but updated now.
> 
> On Fri, Jan 29, 2021 at 8:44 AM Jean-Baptiste Onofre 
> wrote:
> 
>> Thanks Robbie,
>> 
>> I was about to update website. Thanks for catching this !
>> 
>> I will move forward on announcement.
>> 
>> Regards
>> JB
>> 
>>> Le 29 janv. 2021 à 14:38, Robbie Gemmell  a
>> écrit :
>>> 
>>> I have just updated the website to change the download page to 5.16.1,
>>> add the 5.16.1 release page (which notes the announced CVE Gary
>>> already updated the site with), and fix the broken links for the
>>> 5.16.0 page. The site should be updated before the prior release is
>>> removed from mirrors, or it breaks the links.
>>> 
>>> I leave any further tweaks and announcements needed to you.
>>> 
>>> On Thu, 28 Jan 2021 at 05:00, Jean-Baptiste Onofre 
>> wrote:
 
 Hi guys,
 
 Sorry, I’m late about website update, announcement and CVE publication
>> for ActiveMQ 5.16.1.
 
 I will fix that asap (at least during the week end).
 
 Sorry about that,
 Regards
 JB
>> 
>> 
> 
> -- 
> --
> Tim Bish

Re: Website update, announcement, CVE

[Christopher Shannon]

With the discussion of trying to do quarterly releases and keep to a
schedule I am going to chime in here and bring up the fact that I think
that going forward as a project we need to do a much better job at
completing the release process. Recently it seems that most releases are
vastly delayed in having emails sent and the website updated, etc. I've
done a ton of releases for 5.x and I know it's a bit of extra work to do
things like update the site, CVE announcements, release announcements, etc
but it's all part of doing a release. The process doesn't end when the vote
ends and the artifacts are uploaded.

Obviously doing a release is voluntary and no one is obligated to do one
(but it is appreciated of course). However, that being said, my opinion is
if someone chooses to take on the task of doing a release and be the
release manager for it they need to complete the entire process in a timely
manner and not let it drag on for days and weeks.

Chris

On Fri, Feb 5, 2021 at 10:54 AM Jean-Baptiste Onofre 
wrote:

> Hi,
>
> Let me check (I did it but maybe forgot to send ;)).
>
> I will fix that if it didn’t go.
>
> Regards
> JB
>
> > Le 5 févr. 2021 à 16:46, Timothy Bish  a écrit :
> >
> > Did I miss the announcement going out?  Seems like it should have been
> done
> > by now but I don't see it, although website appears to but updated now.
> >
> > On Fri, Jan 29, 2021 at 8:44 AM Jean-Baptiste Onofre 
> > wrote:
> >
> >> Thanks Robbie,
> >>
> >> I was about to update website. Thanks for catching this !
> >>
> >> I will move forward on announcement.
> >>
> >> Regards
> >> JB
> >>
> >>> Le 29 janv. 2021 à 14:38, Robbie Gemmell  a
> >> écrit :
> >>>
> >>> I have just updated the website to change the download page to 5.16.1,
> >>> add the 5.16.1 release page (which notes the announced CVE Gary
> >>> already updated the site with), and fix the broken links for the
> >>> 5.16.0 page. The site should be updated before the prior release is
> >>> removed from mirrors, or it breaks the links.
> >>>
> >>> I leave any further tweaks and announcements needed to you.
> >>>
> >>> On Thu, 28 Jan 2021 at 05:00, Jean-Baptiste Onofre 
> >> wrote:
> 
>  Hi guys,
> 
>  Sorry, I’m late about website update, announcement and CVE publication
> >> for ActiveMQ 5.16.1.
> 
>  I will fix that asap (at least during the week end).
> 
>  Sorry about that,
>  Regards
>  JB
> >>
> >>
> >
> > --
> > --
> > Tim Bish
>
>

Re: Website update, announcement, CVE

[Robbie Gemmell]

On Fri, 5 Feb 2021 at 16:21, Jean-Baptiste Onofre  wrote:
>
> Hi Chris,
>
> I take the fault, no worries. I did the release, but I was swamped with bunch 
> of things and not completed cleanly.
>

In general I have no issue with that, things clearly come up.

Some things can be prioritised though, e.g completing the
delayed/outstanding release process before starting and participating
in new discussion about doing more frequent releases as happened.

> I will fix that.
>
> I think I know well enough the Apache release process on different Apache 
> projects (I can’t count the number of releases I did and still doing) to know 
> that I did bad on the last ActiveMQ one.
> I would like to remind that it’s the first time I messed with the 
> announcement, and I will fix that.

I have actually raised this on multiple previous occasions, and there
have been further occasions inbetween where I haven't.

>
> So, sorry about that and, again I will fix that.
> If you wanna help, you are welcome.

I would agree with Chris that it is preferable or at least typical
that one person completes the process, it's generally far simpler.
That said folks can certainly agree with others to coordinate on
things if needed though. Typically thats done beforehand, or at least
in a timely fashion if unexpected things comes up.

If you dont arrange things with others and/or send mails indicating
you are going to do it, people are generally not going to expect they
are needed to assist with the relatively simple final tasks of the
release, or wont do it to avoid stepping on the original persons toes.
If you instead need help, ask for that rather than reassuing you are
doing it, which likely only delays things further.

I did update the website for 5.16.1 despite this thread last week
though, once I had realised it still wasnt on the site after a week
but a CVE announcement relating to it had already been made since.
With announcements especially though, its awkward to just step in and
do it, as you ought to coordinate first that the original person isnt
also doing it at the same time, and knows not to repeat it later etc,
plus again you had repeated you were doing it, and so I just noted I
was leaving that.

>
> On Apache projects, when I see people having issue (time, personal, …), I 
> propose my help. That’s the way it works IMHO.
>
> Regards
> JB
>
> > Le 5 févr. 2021 à 17:12, Christopher Shannon 
> >  a écrit :
> >
> > With the discussion of trying to do quarterly releases and keep to a
> > schedule I am going to chime in here and bring up the fact that I think
> > that going forward as a project we need to do a much better job at
> > completing the release process. Recently it seems that most releases are
> > vastly delayed in having emails sent and the website updated, etc. I've
> > done a ton of releases for 5.x and I know it's a bit of extra work to do
> > things like update the site, CVE announcements, release announcements, etc
> > but it's all part of doing a release. The process doesn't end when the vote
> > ends and the artifacts are uploaded.
> >
> > Obviously doing a release is voluntary and no one is obligated to do one
> > (but it is appreciated of course). However, that being said, my opinion is
> > if someone chooses to take on the task of doing a release and be the
> > release manager for it they need to complete the entire process in a timely
> > manner and not let it drag on for days and weeks.
> >
> > Chris
> >
> > On Fri, Feb 5, 2021 at 10:54 AM Jean-Baptiste Onofre 
> > wrote:
> >
> >> Hi,
> >>
> >> Let me check (I did it but maybe forgot to send ;)).
> >>
> >> I will fix that if it didn’t go.
> >>
> >> Regards
> >> JB
> >>
> >>> Le 5 févr. 2021 à 16:46, Timothy Bish  a écrit :
> >>>
> >>> Did I miss the announcement going out?  Seems like it should have been
> >> done
> >>> by now but I don't see it, although website appears to but updated now.
> >>>
> >>> On Fri, Jan 29, 2021 at 8:44 AM Jean-Baptiste Onofre 
> >>> wrote:
> >>>
>  Thanks Robbie,
> 
>  I was about to update website. Thanks for catching this !
> 
>  I will move forward on announcement.
> 
>  Regards
>  JB
> 
> > Le 29 janv. 2021 à 14:38, Robbie Gemmell  a
>  écrit :
> >
> > I have just updated the website to change the download page to 5.16.1,
> > add the 5.16.1 release page (which notes the announced CVE Gary
> > already updated the site with), and fix the broken links for the
> > 5.16.0 page. The site should be updated before the prior release is
> > removed from mirrors, or it breaks the links.
> >
> > I leave any further tweaks and announcements needed to you.
> >
> > On Thu, 28 Jan 2021 at 05:00, Jean-Baptiste Onofre 
>  wrote:
> >>
> >> Hi guys,
> >>
> >> Sorry, I’m late about website update, announcement and CVE publication
>  for ActiveMQ 5.16.1.
> >>
> >> I will fix that asap (at least during the week end).
> >>
> 

RE: [ANN] Apache ActiveMQ 5.16.1 has been released!

[Shank, Charles R]

Good morning, I appreciate the emails I have been receiving - I would like to 
know if there is a standard docker image of ActiveMQ that is used by the AMQ 
community that is used in a kubernetes container?

Thank you
Chuck Shank
Nationwide Insurance




-Original Message-
From: Jean-Baptiste Onofre  
Sent: Friday, February 05, 2021 11:38 AM
To: dev@activemq.apache.org; u...@activemq.apache.org
Cc: annou...@apache.org
Subject: [EXTERNAL] [ANN] Apache ActiveMQ 5.16.1 has been released!

Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION 
before clicking on links, opening attachments, or responding. (Sender: 
dev-return-72161-SHANKC1=nationwide@activemq.apache.org)

--


Hi everyone,

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

http://activemq.apache.org/activemq-5161-release 


This release includes updates, and improvements, especially:

- Fix on the runtime configuration plugin, allowing to work with both JDK8 and 
JDK9+
- Prefetch & invalid certificate warnings now include details about the client
- bunch of dependency updates, addressing third party fixes and CVE
- new simple logout link on admin console
- improved Apache Karaf features
- and much more !

Enjoy !

Regards
—
The ActiveMQ Team

RE: Re: [ANN] Apache ActiveMQ 5.16.1 has been released!

[Shank, Charles R]

Nationwide would like to be involved in creating a standard image that could be 
used by the open source community for ActiveMQ




-Original Message-
From: Jean-Baptiste Onofre  
Sent: Friday, February 05, 2021 11:49 AM
To: dev@activemq.apache.org
Subject: [EXTERNAL] Re: [ANN] Apache ActiveMQ 5.16.1 has been released!

Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION 
before clicking on links, opening attachments, or responding. (Sender: 
dev-return-72163-SHANKC1=nationwide@activemq.apache.org)

--


Hi,

We don’t have "official" Apache image (https://hub.docker.com/r/apache/activemq 
).

I create such image for Apache Karaf (https://hub.docker.com/r/apache/karaf 
).

Maybe we can create a Jira about that and start something about that.

Thoughts ?

Regards
JB

> Le 5 févr. 2021 à 17:45, Shank, Charles R  a écrit :
> 
> Good morning, I appreciate the emails I have been receiving - I would like to 
> know if there is a standard docker image of ActiveMQ that is used by the AMQ 
> community that is used in a kubernetes container?
> 
> Thank you
> Chuck Shank
> Nationwide Insurance
> 
> 
> 
> 
> -Original Message-
> From: Jean-Baptiste Onofre  
> Sent: Friday, February 05, 2021 11:38 AM
> To: dev@activemq.apache.org; u...@activemq.apache.org
> Cc: annou...@apache.org
> Subject: [EXTERNAL] [ANN] Apache ActiveMQ 5.16.1 has been released!
> 
> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
> CAUTION before clicking on links, opening attachments, or responding. 
> (Sender: dev-return-72161-SHANKC1=nationwide@activemq.apache.org)
> 
> --
> 
> 
> Hi everyone,
> 
> The ActiveMQ team is pleased to announce Apache ActiveMQ 5.16.1 release.
> 
> http://activemq.apache.org/activemq-5161-release 
> 
> 
> This release includes updates, and improvements, especially:
> 
> - Fix on the runtime configuration plugin, allowing to work with both JDK8 
> and JDK9+
> - Prefetch & invalid certificate warnings now include details about the client
> - bunch of dependency updates, addressing third party fixes and CVE
> - new simple logout link on admin console
> - improved Apache Karaf features
> - and much more !
> 
> Enjoy !
> 
> Regards
> —
> The ActiveMQ Team

Re: Website update, announcement, CVE

[Jean-Baptiste Onofre]

Hi Chris,

I take the fault, no worries. I did the release, but I was swamped with bunch 
of things and not completed cleanly.

I will fix that.

I think I know well enough the Apache release process on different Apache 
projects (I can’t count the number of releases I did and still doing) to know 
that I did bad on the last ActiveMQ one.
I would like to remind that it’s the first time I messed with the announcement, 
and I will fix that.

So, sorry about that and, again I will fix that.
If you wanna help, you are welcome.

On Apache projects, when I see people having issue (time, personal, …), I 
propose my help. That’s the way it works IMHO.

Regards
JB

> Le 5 févr. 2021 à 17:12, Christopher Shannon 
>  a écrit :
> 
> With the discussion of trying to do quarterly releases and keep to a
> schedule I am going to chime in here and bring up the fact that I think
> that going forward as a project we need to do a much better job at
> completing the release process. Recently it seems that most releases are
> vastly delayed in having emails sent and the website updated, etc. I've
> done a ton of releases for 5.x and I know it's a bit of extra work to do
> things like update the site, CVE announcements, release announcements, etc
> but it's all part of doing a release. The process doesn't end when the vote
> ends and the artifacts are uploaded.
> 
> Obviously doing a release is voluntary and no one is obligated to do one
> (but it is appreciated of course). However, that being said, my opinion is
> if someone chooses to take on the task of doing a release and be the
> release manager for it they need to complete the entire process in a timely
> manner and not let it drag on for days and weeks.
> 
> Chris
> 
> On Fri, Feb 5, 2021 at 10:54 AM Jean-Baptiste Onofre 
> wrote:
> 
>> Hi,
>> 
>> Let me check (I did it but maybe forgot to send ;)).
>> 
>> I will fix that if it didn’t go.
>> 
>> Regards
>> JB
>> 
>>> Le 5 févr. 2021 à 16:46, Timothy Bish  a écrit :
>>> 
>>> Did I miss the announcement going out?  Seems like it should have been
>> done
>>> by now but I don't see it, although website appears to but updated now.
>>> 
>>> On Fri, Jan 29, 2021 at 8:44 AM Jean-Baptiste Onofre 
>>> wrote:
>>> 
 Thanks Robbie,
 
 I was about to update website. Thanks for catching this !
 
 I will move forward on announcement.
 
 Regards
 JB
 
> Le 29 janv. 2021 à 14:38, Robbie Gemmell  a
 écrit :
> 
> I have just updated the website to change the download page to 5.16.1,
> add the 5.16.1 release page (which notes the announced CVE Gary
> already updated the site with), and fix the broken links for the
> 5.16.0 page. The site should be updated before the prior release is
> removed from mirrors, or it breaks the links.
> 
> I leave any further tweaks and announcements needed to you.
> 
> On Thu, 28 Jan 2021 at 05:00, Jean-Baptiste Onofre 
 wrote:
>> 
>> Hi guys,
>> 
>> Sorry, I’m late about website update, announcement and CVE publication
 for ActiveMQ 5.16.1.
>> 
>> I will fix that asap (at least during the week end).
>> 
>> Sorry about that,
>> Regards
>> JB
 
 
>>> 
>>> --
>>> --
>>> Tim Bish
>> 
>> 

[ANN] Apache ActiveMQ 5.16.1 has been released!

[Jean-Baptiste Onofre]

Hi everyone,

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

http://activemq.apache.org/activemq-5161-release 


This release includes updates, and improvements, especially:

- Fix on the runtime configuration plugin, allowing to work with both JDK8 and 
JDK9+
- Prefetch & invalid certificate warnings now include details about the client
- bunch of dependency updates, addressing third party fixes and CVE
- new simple logout link on admin console
- improved Apache Karaf features
- and much more !

Enjoy !

Regards
—
The ActiveMQ Team

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

[Jean-Baptiste Onofre]

Hi,

We don’t have "official" Apache image (https://hub.docker.com/r/apache/activemq 
).

I create such image for Apache Karaf (https://hub.docker.com/r/apache/karaf 
).

Maybe we can create a Jira about that and start something about that.

Thoughts ?

Regards
JB

> Le 5 févr. 2021 à 17:45, Shank, Charles R  a écrit :
> 
> Good morning, I appreciate the emails I have been receiving - I would like to 
> know if there is a standard docker image of ActiveMQ that is used by the AMQ 
> community that is used in a kubernetes container?
> 
> Thank you
> Chuck Shank
> Nationwide Insurance
> 
> 
> 
> 
> -Original Message-
> From: Jean-Baptiste Onofre  
> Sent: Friday, February 05, 2021 11:38 AM
> To: dev@activemq.apache.org; u...@activemq.apache.org
> Cc: annou...@apache.org
> Subject: [EXTERNAL] [ANN] Apache ActiveMQ 5.16.1 has been released!
> 
> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
> CAUTION before clicking on links, opening attachments, or responding. 
> (Sender: dev-return-72161-SHANKC1=nationwide@activemq.apache.org)
> 
> --
> 
> 
> Hi everyone,
> 
> The ActiveMQ team is pleased to announce Apache ActiveMQ 5.16.1 release.
> 
> http://activemq.apache.org/activemq-5161-release 
> 
> 
> This release includes updates, and improvements, especially:
> 
> - Fix on the runtime configuration plugin, allowing to work with both JDK8 
> and JDK9+
> - Prefetch & invalid certificate warnings now include details about the client
> - bunch of dependency updates, addressing third party fixes and CVE
> - new simple logout link on admin console
> - improved Apache Karaf features
> - and much more !
> 
> Enjoy !
> 
> Regards
> —
> The ActiveMQ Team

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

[Jean-Baptiste Onofre]

Awesome !

Do you already have a Dockerfile ready ?

Regards
JB

> Le 5 févr. 2021 à 17:52, Shank, Charles R  a écrit :
> 
> Nationwide would like to be involved in creating a standard image that could 
> be used by the open source community for ActiveMQ
> 
> 
> 
> 
> -Original Message-
> From: Jean-Baptiste Onofre  
> Sent: Friday, February 05, 2021 11:49 AM
> To: dev@activemq.apache.org
> Subject: [EXTERNAL] Re: [ANN] Apache ActiveMQ 5.16.1 has been released!
> 
> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
> CAUTION before clicking on links, opening attachments, or responding. 
> (Sender: dev-return-72163-SHANKC1=nationwide@activemq.apache.org)
> 
> --
> 
> 
> Hi,
> 
> We don’t have "official" Apache image 
> (https://hub.docker.com/r/apache/activemq 
> ).
> 
> I create such image for Apache Karaf (https://hub.docker.com/r/apache/karaf 
> ).
> 
> Maybe we can create a Jira about that and start something about that.
> 
> Thoughts ?
> 
> Regards
> JB
> 
>> Le 5 févr. 2021 à 17:45, Shank, Charles R  a écrit :
>> 
>> Good morning, I appreciate the emails I have been receiving - I would like 
>> to know if there is a standard docker image of ActiveMQ that is used by the 
>> AMQ community that is used in a kubernetes container?
>> 
>> Thank you
>> Chuck Shank
>> Nationwide Insurance
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: Jean-Baptiste Onofre  
>> Sent: Friday, February 05, 2021 11:38 AM
>> To: dev@activemq.apache.org; u...@activemq.apache.org
>> Cc: annou...@apache.org
>> Subject: [EXTERNAL] [ANN] Apache ActiveMQ 5.16.1 has been released!
>> 
>> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
>> CAUTION before clicking on links, opening attachments, or responding. 
>> (Sender: dev-return-72161-SHANKC1=nationwide@activemq.apache.org)
>> 
>> --
>> 
>> 
>> Hi everyone,
>> 
>> The ActiveMQ team is pleased to announce Apache ActiveMQ 5.16.1 release.
>> 
>> http://activemq.apache.org/activemq-5161-release 
>> 
>> 
>> This release includes updates, and improvements, especially:
>> 
>> - Fix on the runtime configuration plugin, allowing to work with both JDK8 
>> and JDK9+
>> - Prefetch & invalid certificate warnings now include details about the 
>> client
>> - bunch of dependency updates, addressing third party fixes and CVE
>> - new simple logout link on admin console
>> - improved Apache Karaf features
>> - and much more !
>> 
>> Enjoy !
>> 
>> Regards
>> —
>> The ActiveMQ Team
> 

Re: Website update, announcement, CVE

[Christopher Shannon]

JB,

Believe me I certainly appreciate the work you have done and all the
releases as of late. I know my email essentially singled you out (just
because you are the only one who has done 5.x releases recently) and was a
bit critical but my response was also just for anyone and includes all of
our projects like Artemis. I just think it's a good idea to have a plan to
make sure the process is finished in a timely manner before starting.

When I've done releases I have personally found that when starting the
release process it's just easiest if that same person completes everything
and just acts as the release manager for the whole process because others
don't know where things stand so it's a bit hard for them to help (unless
it's asked for). That's just my opinion of course and maybe other people
don't agree.  As you stated anyone can still help out and that is great if
they do of course.

Going forward we can always rotate who performs the releases so the work
isn't always put on one person (in this case you). Since we will have a
schedule it will probably be easier to get others to volunteer. I can
certainly help out and do some of them. Or we can coordinate and task
different people to do different parts of the process ahead of time if they
are willing to reduce the burden on one person.

Chris

On Fri, Feb 5, 2021 at 11:21 AM Jean-Baptiste Onofre 
wrote:

> Hi Chris,
>
> I take the fault, no worries. I did the release, but I was swamped with
> bunch of things and not completed cleanly.
>
> I will fix that.
>
> I think I know well enough the Apache release process on different Apache
> projects (I can’t count the number of releases I did and still doing) to
> know that I did bad on the last ActiveMQ one.
> I would like to remind that it’s the first time I messed with the
> announcement, and I will fix that.
>
> So, sorry about that and, again I will fix that.
> If you wanna help, you are welcome.
>
> On Apache projects, when I see people having issue (time, personal, …), I
> propose my help. That’s the way it works IMHO.
>
> Regards
> JB
>
> > Le 5 févr. 2021 à 17:12, Christopher Shannon <
> christopher.l.shan...@gmail.com> a écrit :
> >
> > With the discussion of trying to do quarterly releases and keep to a
> > schedule I am going to chime in here and bring up the fact that I think
> > that going forward as a project we need to do a much better job at
> > completing the release process. Recently it seems that most releases are
> > vastly delayed in having emails sent and the website updated, etc. I've
> > done a ton of releases for 5.x and I know it's a bit of extra work to do
> > things like update the site, CVE announcements, release announcements,
> etc
> > but it's all part of doing a release. The process doesn't end when the
> vote
> > ends and the artifacts are uploaded.
> >
> > Obviously doing a release is voluntary and no one is obligated to do one
> > (but it is appreciated of course). However, that being said, my opinion
> is
> > if someone chooses to take on the task of doing a release and be the
> > release manager for it they need to complete the entire process in a
> timely
> > manner and not let it drag on for days and weeks.
> >
> > Chris
> >
> > On Fri, Feb 5, 2021 at 10:54 AM Jean-Baptiste Onofre 
> > wrote:
> >
> >> Hi,
> >>
> >> Let me check (I did it but maybe forgot to send ;)).
> >>
> >> I will fix that if it didn’t go.
> >>
> >> Regards
> >> JB
> >>
> >>> Le 5 févr. 2021 à 16:46, Timothy Bish  a écrit :
> >>>
> >>> Did I miss the announcement going out?  Seems like it should have been
> >> done
> >>> by now but I don't see it, although website appears to but updated now.
> >>>
> >>> On Fri, Jan 29, 2021 at 8:44 AM Jean-Baptiste Onofre 
> >>> wrote:
> >>>
>  Thanks Robbie,
> 
>  I was about to update website. Thanks for catching this !
> 
>  I will move forward on announcement.
> 
>  Regards
>  JB
> 
> > Le 29 janv. 2021 à 14:38, Robbie Gemmell 
> a
>  écrit :
> >
> > I have just updated the website to change the download page to
> 5.16.1,
> > add the 5.16.1 release page (which notes the announced CVE Gary
> > already updated the site with), and fix the broken links for the
> > 5.16.0 page. The site should be updated before the prior release is
> > removed from mirrors, or it breaks the links.
> >
> > I leave any further tweaks and announcements needed to you.
> >
> > On Thu, 28 Jan 2021 at 05:00, Jean-Baptiste Onofre 
>  wrote:
> >>
> >> Hi guys,
> >>
> >> Sorry, I’m late about website update, announcement and CVE
> publication
>  for ActiveMQ 5.16.1.
> >>
> >> I will fix that asap (at least during the week end).
> >>
> >> Sorry about that,
> >> Regards
> >> JB
> 
> 
> >>>
> >>> --
> >>> --
> >>> Tim Bish
> >>
> >>
>
>

RE: Re: [ANN] Apache ActiveMQ 5.16.1 has been released!

[Shank, Charles R]

We have an initial dockerfile, we have used to put a instance of AMQ in the 
cloud.  We will need to work on fine tuning it to have it available to the 
community





-Original Message-
From: Jean-Baptiste Onofre  
Sent: Friday, February 05, 2021 11:55 AM
To: dev@activemq.apache.org
Subject: [EXTERNAL] Re: [ANN] Apache ActiveMQ 5.16.1 has been released!

Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION 
before clicking on links, opening attachments, or responding. (Sender: 
dev-return-72165-SHANKC1=nationwide@activemq.apache.org)

--


Awesome !

Do you already have a Dockerfile ready ?

Regards
JB

> Le 5 févr. 2021 à 17:52, Shank, Charles R  a écrit :
> 
> Nationwide would like to be involved in creating a standard image that could 
> be used by the open source community for ActiveMQ
> 
> 
> 
> 
> -Original Message-
> From: Jean-Baptiste Onofre  
> Sent: Friday, February 05, 2021 11:49 AM
> To: dev@activemq.apache.org
> Subject: [EXTERNAL] Re: [ANN] Apache ActiveMQ 5.16.1 has been released!
> 
> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
> CAUTION before clicking on links, opening attachments, or responding. 
> (Sender: dev-return-72163-SHANKC1=nationwide@activemq.apache.org)
> 
> --
> 
> 
> Hi,
> 
> We don’t have "official" Apache image 
> (https://hub.docker.com/r/apache/activemq 
> ).
> 
> I create such image for Apache Karaf (https://hub.docker.com/r/apache/karaf 
> ).
> 
> Maybe we can create a Jira about that and start something about that.
> 
> Thoughts ?
> 
> Regards
> JB
> 
>> Le 5 févr. 2021 à 17:45, Shank, Charles R  a écrit :
>> 
>> Good morning, I appreciate the emails I have been receiving - I would like 
>> to know if there is a standard docker image of ActiveMQ that is used by the 
>> AMQ community that is used in a kubernetes container?
>> 
>> Thank you
>> Chuck Shank
>> Nationwide Insurance
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: Jean-Baptiste Onofre  
>> Sent: Friday, February 05, 2021 11:38 AM
>> To: dev@activemq.apache.org; u...@activemq.apache.org
>> Cc: annou...@apache.org
>> Subject: [EXTERNAL] [ANN] Apache ActiveMQ 5.16.1 has been released!
>> 
>> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
>> CAUTION before clicking on links, opening attachments, or responding. 
>> (Sender: dev-return-72161-SHANKC1=nationwide@activemq.apache.org)
>> 
>> --
>> 
>> 
>> Hi everyone,
>> 
>> The ActiveMQ team is pleased to announce Apache ActiveMQ 5.16.1 release.
>> 
>> http://activemq.apache.org/activemq-5161-release 
>> 
>> 
>> This release includes updates, and improvements, especially:
>> 
>> - Fix on the runtime configuration plugin, allowing to work with both JDK8 
>> and JDK9+
>> - Prefetch & invalid certificate warnings now include details about the 
>> client
>> - bunch of dependency updates, addressing third party fixes and CVE
>> - new simple logout link on admin console
>> - improved Apache Karaf features
>> - and much more !
>> 
>> Enjoy !
>> 
>> Regards
>> —
>> The ActiveMQ Team
> 

Re: Website update, announcement, CVE

[Jean-Baptiste Onofre]

OK, ack.

No more comment about that from my side.

I will keep your comments in mind.

Anyway, I will move forward on my actions and release cycle for the good of the 
project ;)

> Le 5 févr. 2021 à 18:52, Robbie Gemmell  a écrit :
> 
> On Fri, 5 Feb 2021 at 16:21, Jean-Baptiste Onofre  wrote:
>> 
>> Hi Chris,
>> 
>> I take the fault, no worries. I did the release, but I was swamped with 
>> bunch of things and not completed cleanly.
>> 
> 
> In general I have no issue with that, things clearly come up.
> 
> Some things can be prioritised though, e.g completing the
> delayed/outstanding release process before starting and participating
> in new discussion about doing more frequent releases as happened.
> 
>> I will fix that.
>> 
>> I think I know well enough the Apache release process on different Apache 
>> projects (I can’t count the number of releases I did and still doing) to 
>> know that I did bad on the last ActiveMQ one.
>> I would like to remind that it’s the first time I messed with the 
>> announcement, and I will fix that.
> 
> I have actually raised this on multiple previous occasions, and there
> have been further occasions inbetween where I haven't.
> 
>> 
>> So, sorry about that and, again I will fix that.
>> If you wanna help, you are welcome.
> 
> I would agree with Chris that it is preferable or at least typical
> that one person completes the process, it's generally far simpler.
> That said folks can certainly agree with others to coordinate on
> things if needed though. Typically thats done beforehand, or at least
> in a timely fashion if unexpected things comes up.
> 
> If you dont arrange things with others and/or send mails indicating
> you are going to do it, people are generally not going to expect they
> are needed to assist with the relatively simple final tasks of the
> release, or wont do it to avoid stepping on the original persons toes.
> If you instead need help, ask for that rather than reassuing you are
> doing it, which likely only delays things further.
> 
> I did update the website for 5.16.1 despite this thread last week
> though, once I had realised it still wasnt on the site after a week
> but a CVE announcement relating to it had already been made since.
> With announcements especially though, its awkward to just step in and
> do it, as you ought to coordinate first that the original person isnt
> also doing it at the same time, and knows not to repeat it later etc,
> plus again you had repeated you were doing it, and so I just noted I
> was leaving that.
> 
>> 
>> On Apache projects, when I see people having issue (time, personal, …), I 
>> propose my help. That’s the way it works IMHO.
>> 
>> Regards
>> JB
>> 
>>> Le 5 févr. 2021 à 17:12, Christopher Shannon 
>>>  a écrit :
>>> 
>>> With the discussion of trying to do quarterly releases and keep to a
>>> schedule I am going to chime in here and bring up the fact that I think
>>> that going forward as a project we need to do a much better job at
>>> completing the release process. Recently it seems that most releases are
>>> vastly delayed in having emails sent and the website updated, etc. I've
>>> done a ton of releases for 5.x and I know it's a bit of extra work to do
>>> things like update the site, CVE announcements, release announcements, etc
>>> but it's all part of doing a release. The process doesn't end when the vote
>>> ends and the artifacts are uploaded.
>>> 
>>> Obviously doing a release is voluntary and no one is obligated to do one
>>> (but it is appreciated of course). However, that being said, my opinion is
>>> if someone chooses to take on the task of doing a release and be the
>>> release manager for it they need to complete the entire process in a timely
>>> manner and not let it drag on for days and weeks.
>>> 
>>> Chris
>>> 
>>> On Fri, Feb 5, 2021 at 10:54 AM Jean-Baptiste Onofre 
>>> wrote:
>>> 
 Hi,
 
 Let me check (I did it but maybe forgot to send ;)).
 
 I will fix that if it didn’t go.
 
 Regards
 JB
 
> Le 5 févr. 2021 à 16:46, Timothy Bish  a écrit :
> 
> Did I miss the announcement going out?  Seems like it should have been
 done
> by now but I don't see it, although website appears to but updated now.
> 
> On Fri, Jan 29, 2021 at 8:44 AM Jean-Baptiste Onofre 
> wrote:
> 
>> Thanks Robbie,
>> 
>> I was about to update website. Thanks for catching this !
>> 
>> I will move forward on announcement.
>> 
>> Regards
>> JB
>> 
>>> Le 29 janv. 2021 à 14:38, Robbie Gemmell  a
>> écrit :
>>> 
>>> I have just updated the website to change the download page to 5.16.1,
>>> add the 5.16.1 release page (which notes the announced CVE Gary
>>> already updated the site with), and fix the broken links for the
>>> 5.16.0 page. The site should be updated before the prior release is
>>> removed from mirrors, or it breaks the links.
>>> 
>>> I leave any 

RE: Re: [ANN] Apache ActiveMQ 5.16.1 has been released!

[Shank, Charles R]

JB,

The dockerfile and image that we currently have available is specific to 
Nationwide.  What I would like to propose is to have a community discussion on 
the requirements so a generic docker image could be created that would benefit 
the whole ActiveMQ community.

For example:
Do we build it using Debian or alpine?
Java version?
Items like this - also where does the jira board for ActiveMQ reside?

I look forward to working with you and the others in the ActiveMQ community

Thank you in advance
Chuck Shank



-Original Message-
From: Jean-Baptiste Onofre  
Sent: Friday, February 05, 2021 11:55 AM
To: dev@activemq.apache.org
Subject: [EXTERNAL] Re: [ANN] Apache ActiveMQ 5.16.1 has been released!

Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION 
before clicking on links, opening attachments, or responding. (Sender: 
dev-return-72165-SHANKC1=nationwide@activemq.apache.org)

--


Awesome !

Do you already have a Dockerfile ready ?

Regards
JB

> Le 5 févr. 2021 à 17:52, Shank, Charles R  a écrit :
> 
> Nationwide would like to be involved in creating a standard image that could 
> be used by the open source community for ActiveMQ
> 
> 
> 
> 
> -Original Message-
> From: Jean-Baptiste Onofre  
> Sent: Friday, February 05, 2021 11:49 AM
> To: dev@activemq.apache.org
> Subject: [EXTERNAL] Re: [ANN] Apache ActiveMQ 5.16.1 has been released!
> 
> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
> CAUTION before clicking on links, opening attachments, or responding. 
> (Sender: dev-return-72163-SHANKC1=nationwide@activemq.apache.org)
> 
> --
> 
> 
> Hi,
> 
> We don’t have "official" Apache image 
> (https://hub.docker.com/r/apache/activemq 
> ).
> 
> I create such image for Apache Karaf (https://hub.docker.com/r/apache/karaf 
> ).
> 
> Maybe we can create a Jira about that and start something about that.
> 
> Thoughts ?
> 
> Regards
> JB
> 
>> Le 5 févr. 2021 à 17:45, Shank, Charles R  a écrit :
>> 
>> Good morning, I appreciate the emails I have been receiving - I would like 
>> to know if there is a standard docker image of ActiveMQ that is used by the 
>> AMQ community that is used in a kubernetes container?
>> 
>> Thank you
>> Chuck Shank
>> Nationwide Insurance
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: Jean-Baptiste Onofre  
>> Sent: Friday, February 05, 2021 11:38 AM
>> To: dev@activemq.apache.org; u...@activemq.apache.org
>> Cc: annou...@apache.org
>> Subject: [EXTERNAL] [ANN] Apache ActiveMQ 5.16.1 has been released!
>> 
>> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
>> CAUTION before clicking on links, opening attachments, or responding. 
>> (Sender: dev-return-72161-SHANKC1=nationwide@activemq.apache.org)
>> 
>> --
>> 
>> 
>> Hi everyone,
>> 
>> The ActiveMQ team is pleased to announce Apache ActiveMQ 5.16.1 release.
>> 
>> http://activemq.apache.org/activemq-5161-release 
>> 
>> 
>> This release includes updates, and improvements, especially:
>> 
>> - Fix on the runtime configuration plugin, allowing to work with both JDK8 
>> and JDK9+
>> - Prefetch & invalid certificate warnings now include details about the 
>> client
>> - bunch of dependency updates, addressing third party fixes and CVE
>> - new simple logout link on admin console
>> - improved Apache Karaf features
>> - and much more !
>> 
>> Enjoy !
>> 
>> Regards
>> —
>> The ActiveMQ Team
> 

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

[Jean-Baptiste Onofre]

Hi,

Of course a discussion is always welcome.

To answer to your first question:

1. Alpine is fine IMHO for ActiveMQ (lighter).
2. Java 8 for ActiveMQ 5.15.x, Java 11 based image for ActiveMQ 5.16.x+
3. The ActiveMQ Jira is there: 
https://issues.apache.org/jira/projects/AMQ/issues/AMQ-7229?filter=allopenissues
 

I can create a component Docker on Jira.

IMHO, the docker image should use env variables to pass configuration (in 
activemq.xml), and we should provide README.md with some important information 
(I’m thinking the filesystem to use on some cloud provider, like EFS on AWS, 
etc).
By the way, I also have a Dockerfile for my production system (on Azure and 
AWS).

Regards
JB

> Le 5 févr. 2021 à 21:45, Shank, Charles R  a écrit :
> 
> 
> JB,
> 
> The dockerfile and image that we currently have available is specific to 
> Nationwide.  What I would like to propose is to have a community discussion 
> on the requirements so a generic docker image could be created that would 
> benefit the whole ActiveMQ community.
> 
> For example:
> Do we build it using Debian or alpine?
> Java version?
> Items like this - also where does the jira board for ActiveMQ reside?
> 
> I look forward to working with you and the others in the ActiveMQ community
> 
> Thank you in advance
> Chuck Shank
> 
> 
> 
> -Original Message-
> From: Jean-Baptiste Onofre  
> Sent: Friday, February 05, 2021 11:55 AM
> To: dev@activemq.apache.org
> Subject: [EXTERNAL] Re: [ANN] Apache ActiveMQ 5.16.1 has been released!
> 
> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
> CAUTION before clicking on links, opening attachments, or responding. 
> (Sender: dev-return-72165-SHANKC1=nationwide@activemq.apache.org)
> 
> --
> 
> 
> Awesome !
> 
> Do you already have a Dockerfile ready ?
> 
> Regards
> JB
> 
>> Le 5 févr. 2021 à 17:52, Shank, Charles R  a écrit :
>> 
>> Nationwide would like to be involved in creating a standard image that could 
>> be used by the open source community for ActiveMQ
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: Jean-Baptiste Onofre  
>> Sent: Friday, February 05, 2021 11:49 AM
>> To: dev@activemq.apache.org
>> Subject: [EXTERNAL] Re: [ANN] Apache ActiveMQ 5.16.1 has been released!
>> 
>> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
>> CAUTION before clicking on links, opening attachments, or responding. 
>> (Sender: dev-return-72163-SHANKC1=nationwide@activemq.apache.org)
>> 
>> --
>> 
>> 
>> Hi,
>> 
>> We don’t have "official" Apache image 
>> (https://hub.docker.com/r/apache/activemq 
>> ).
>> 
>> I create such image for Apache Karaf (https://hub.docker.com/r/apache/karaf 
>> ).
>> 
>> Maybe we can create a Jira about that and start something about that.
>> 
>> Thoughts ?
>> 
>> Regards
>> JB
>> 
>>> Le 5 févr. 2021 à 17:45, Shank, Charles R  a écrit :
>>> 
>>> Good morning, I appreciate the emails I have been receiving - I would like 
>>> to know if there is a standard docker image of ActiveMQ that is used by the 
>>> AMQ community that is used in a kubernetes container?
>>> 
>>> Thank you
>>> Chuck Shank
>>> Nationwide Insurance
>>> 
>>> 
>>> 
>>> 
>>> -Original Message-
>>> From: Jean-Baptiste Onofre  
>>> Sent: Friday, February 05, 2021 11:38 AM
>>> To: dev@activemq.apache.org; u...@activemq.apache.org
>>> Cc: annou...@apache.org
>>> Subject: [EXTERNAL] [ANN] Apache ActiveMQ 5.16.1 has been released!
>>> 
>>> Nationwide Information Security Warning: This is an EXTERNAL email. Use 
>>> CAUTION before clicking on links, opening attachments, or responding. 
>>> (Sender: dev-return-72161-SHANKC1=nationwide@activemq.apache.org)
>>> 
>>> --
>>> 
>>> 
>>> Hi everyone,
>>> 
>>> The ActiveMQ team is pleased to announce Apache ActiveMQ 5.16.1 release.
>>> 
>>> http://activemq.apache.org/activemq-5161-release 
>>> 
>>> 
>>> This release includes updates, and improvements, especially:
>>> 
>>> - Fix on the runtime configuration plugin, allowing to work with both JDK8 
>>> and JDK9+
>>> - Prefetch & invalid certificate warnings now include details about the 
>>> client
>>> - bunch of dependency updates, addressing third party fixes and CVE
>>> - new simple logout link on admin console
>>> - improved Apache Karaf features
>>> - and much more !
>>> 
>>> Enjoy !
>>> 
>>> Regards
>>> —
>>> The ActiveMQ Team
>> 
>