I'm pleased to announce the release of ActiveMQ Artemis 2.19.1
Downloads are now available at:
https://activemq.apache.org/components/artemis/download/
For a complete list of updates:
https://activemq.apache.org/components/artemis/download/release-notes-2.19.1
This is a maintenance release o
I'm just releasing artemis 2.19.1 which is a maintenance release on
top of 2.19.0
2.21.0 is due in a couple of weeks.
On Tue, Feb 1, 2022 at 12:37 AM Wilcox, Jim
wrote:
>
> Hello,
>
> Can you share any information on when this new major version of ActiveMQ for
> Artemis release date is planned
Hi Justin,
I think it’s not a huge effort compare to what we already do at each release
(updating the website).
For instance, for Karaf, it’s pretty quick to update website and release
schedule at each release cycle.
I already proposed regular release cycle in the past (as best effort).
I wou
Generally speaking, I'm against anything that will require more maintenance
of the website. History indicates that the community is somewhat weak in
this area.
Correct me if I'm wrong, but from what I can tell we've never consistently
scheduled releases. Also, given the Apache Way with the release
Hello Paul-
The transaction handles the nack details. The example is showing how you
identify a transaction “tx1”. A transaction may end via abort, commit or
abandoned. I believe the abort would send a nack that instructs the broker to
redeliver the message.
Thanks,
Matt Pavlovich
> On Feb 1,
Most folks want the opposite of what you're asking; they want to be able to
read the content of the message on the web console. Therefore, if you build
the message in such a way that the web console can deserialize it then the
web console _will_ deserialize it. It will detect the BytesMessage and
s
Hello,
According to the stomp specification, the handling of the NACK client
command is server specific. Does anyone know how activemq handles the
NACK command? The only relevant documentation seems to be :
https://activemq.apache.org/how-do-i-unack-the-message-with-stomp,
which is written as if
I understand. But I was wondering if web console can just show (or not show)
the raw binary content and serialization/deserialization happen only on the
client. That way the message content is not human readable in the web console.
I ran across IObjectMessage & CreateObjectMessage and tried it.
And by the way, this page should mention some important notes (like JDK
version supported, log4j versions, Spring version, ...).
Regards
JB
On 01/02/2022 13:47, Tim Bain wrote:
Would it be worth the effort to create and then maintain a page that lists
the planned timeline of upcoming releases
Hi Tim,
That's a good idea (and it's what we are doing on others projects like
Karaf and Camel).
If there's no objection, I will do the ActiveMQ one.
Regards
JB
On 01/02/2022 13:47, Tim Bain wrote:
Would it be worth the effort to create and then maintain a page that lists
the planned timeli
Would it be worth the effort to create and then maintain a page that lists
the planned timeline of upcoming releases for both 5.x and Artemis? There
have been a lot of questions about upcoming plans in the wake of the Log4J
CVE, but even during normal times we get occasional questions here about
up
If you want to prevent messages from being read by people other than the
intended recipient, whether on the web console or elsewhere, the standard
way to do that is to encrypt the message when sending and then have the
intended recipient decrypt it upon receipt.
Or you can limit access to the web
12 matches
Mail list logo
