Thank you for the response Justin. I get out of memory crashes when using
artemis-jakarta-client on the consumer side when the message is of type
Text.
The artemis-jakarta-client buffers the whole large message into memory if
the message is of type Text and that crashes the consumer if the message
> This is what I had in mind.
I'm not in favor of changing the branding at this point. In order to be
consistent between both Artemis and Classic lots of stuff would need to be
updated including potentially the website.
> are there any official logos...
There are logos here [1].
Justin
[1] ht
I haven't had a chance yet. I hope to have a chance relatively soon.
Justin
On Tue, Apr 22, 2025 at 4:42 AM Luchi Mirko wrote:
> Hi Justin,
>
> have you had a chance to take a look at why message redistribution seems
> not to work when clustered message grouping is used?
>
> Thanks,
> Mirko
>
If the message was sent as a "large" message or converted into a large
message by the broker (e.g. if it exceeded the journal-buffer-size) then it
can be streamed from the broker in chunks via JMS as noted in the
documentation [1]. However, if the message is not "large" then the entire
message will
Matt
What you provided is what I was finding as well but I wanted to see if I missed
something.
Thanks for the information
Jason Jackson
From: Matt Pavlovich
Sent: Tuesday, April 29, 2025 1:16 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ Classic 6.1
