Hi Justin,
We are using Artemis 2.31.2. Can you please help in understanding how
min-large-message-size will help in this case?
* 100 KB (102400) is the default min-large-message-size and any message bigger
than this size (message = header + body) will be split and sent over network
into multip
It was this issue / commit:
https://github.com/apache/activemq-artemis/commit/04f6424928a3d9cbc26f6b26f7c2e9b7f7bf7869
And BTW: Headers are not supposed to be large. Move the data to the
body of the message.
Headers are meant to be really small and only provide enough
information for filtering.
I had a fix for an almost large message becoming large and it should been
fixed on this latest release.
I don’t remember the JIRA now and I’m on the phone. But I may find it
tomorrow if you want it.
Clebert Suconic
On Mon, Jun 3, 2024 at 5:53 PM Justin Bertram wrote:
> What version of ActiveM
I'm pleased to announce the release of Apache ActiveMQ Artemis 2.34.0 release.
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.34.0
Also the dock
What version of ActiveMQ Artemis are you using? Do you have a way to
reproduce what you're seeing? If so, could you provide it?
A while back there was an issue with flow control and large messages [1].
More recently I've seen some issues with messages which are _almost_ large
with really big heade
There are lots of ways to monitor the heap usage of a JVM, but my
recommendation would be to use the metrics subsystem [1] and export JVM
memory and GC metrics [2] via something like Prometheus [3] using this
plugin [4]. Your configuration in broker.xml would look something like this:
true
IMO you should probably try/upgrade to artemis 2.34 being released now.
On Mon, Jun 3, 2024 at 1:40 AM wrote:
>
> Thank you for your thoughts.
> So I will consider the behavior of ActiveMQ Artemis the desired one and be
> more specific in the future with the client settings.
>
> Sebastian
>
> -
Since your address-setting match is using "/" characters (i.e. in "/tmp/#")
you should ostensibly define the wildcard syntax [1] to use them as well,
e.g.:
true
/
#
*
The default wildcard syntax uses "." characters so if you wanted to use the
default syntax your match wo
Stefan,
That is correct. You are in a tricky spot with Sparc, JDK 11, and Spring 5.x
all approaching EOL for support. Unfortunately, one of those will be the first
to be a problem.
Spring is the one that I suspect could see a community supported fork — similar
to reload4j did for log4j v1. Spr
Hi Matt,
Thanks - but it would seem that Spring really EOLs Spring 5 in 08/2024 and will
provide updates only for paying customers...
So I'm assuming to see "Not Active" on
https://activemq.apache.org/components/classic/download/ with the first issue
in used Spring components that will get no
That seems reasonable.
Let us know if you run into any issues during your migration.
Justin
On Mon, Jun 3, 2024 at 9:31 AM Boeltl, Stefan
wrote:
> Hi Justin,
>
> Looks like maybe the next 2 years - my hope is with Red Hat since we're
> using JBoss EAP which has the Artemis "on board", so they
Hi Stefan-
There are plans to keep a LTS ActiveMQ 5.x going for a while— that would keep
you updated with the Spring 5.x dependencies (as long as Spring is releasing
them).
Thanks,
Matt
> On Jun 3, 2024, at 9:30 AM, Boeltl, Stefan
> wrote:
>
> Hi Justin,
>
> Looks like maybe the next 2 ye
Hi Justin,
Looks like maybe the next 2 years - my hope is with Red Hat since we're using
JBoss EAP which has the Artemis "on board", so they might support any OSS
version for Java 11 until JBoss 7.4 is not supported anymore (which would work
for us).
Regards
Stefan
-Original Message-
Migrating to Artemis is a viable option. It currently only requires Java
11, but eventually that target will move. Do you have any idea how long
you'll be in this position?
Justin
On Mon, Jun 3, 2024 at 9:19 AM Boeltl, Stefan
wrote:
> Hi Matt,
>
> Thanks for the answer (wasn't sure whether the
Hi Matt,
Thanks for the answer (wasn't sure whether there is some "automatism")!
And just between the two of us: I was the one asking for this EOL topic some
time ago because we're stuck with Solaris on Sparc where Java 17 is not
supported... currently it looks like our way forward will be to m
Hi Stefan-
Currently, the work is on a 6.2.0 release and a 5.18.x will usually come around
the same time. Dependencies (including Spring) are updated ahead of each
release.
Keep in mind Spring is planning to EOL OSS support in August of 2024. I
recommend starting to make plans for ActiveMQ 6.
Hi team,
Is there any update/input on this topic? Seems we are being hit by this issue
more frequently.
Best Regards
Shiv
-Original Message-
From: Shiv Kumar Dixit
Sent: Thursday, May 30, 2024 12:35 PM
To: users@activemq.apache.org
Subject: Issue in clustering due to Large JMS Header
Dear ActiveMQ committers,
One question regarding upcoming 5.18.5: will there be an update for the Spring
components included (can't see a ticket for this yet)?
(Background: we have another finding in our SCA tool and it would be great to
be up to date again with the next patch)
Thanks!
Kind re
18 matches
Mail list logo
