Hi Herbert,
I think that makes sense and maybe the official transformer could support
also the other virtualDestinationInterceptor options.
Regards,
Domenico
Il ven 8 set 2023, 10:58 ha scritto:
> Hi Domenico,
>
> thank you for the helpful reply. I never extended the Broker, but it seems
> as
Hi JB,
Yes these messages has been redelivered befor moving to the DLQ.
regards,
François
On 08/09/2023 16:46, Jean-Baptiste Onofré wrote:
Hi,
The messages have been redelivered before moving to the DLQ ?
Regards
JB
On Wed, Sep 6, 2023 at 9:08 AM fpapon wrote:
Hi,
I have an ActiveMQ (5.
Hi,
The messages have been redelivered before moving to the DLQ ?
Regards
JB
On Wed, Sep 6, 2023 at 9:08 AM fpapon wrote:
>
> Hi,
>
> I have an ActiveMQ (5.16.2/JDK11) broker with persistence message (kahadb).
>
> We are using a deadletter strategy to clean messages older than 7 days
> but we c
Thanks for your reply.
The metrics used for this investigation is collected by datadog against the
broker JMX endpoint, and the kubernetes metrics-server.
"container" bytes are what I call the metrics collected by the metrics-server,
so what kubernetes refer to as used container memory. It is l
> ...each "address size" byte takes 40- 160 "container" bytes.
Can you elaborate on how this was calculated?
Also, what exactly do you mean by "'container' bytes"? Are you talking
about JVM heap? Keep in mind that as far as the broker is concerned memory
usage won't change when running in a conta
Hi Domenico,
thank you for the helpful reply. I never extended the Broker, but it seems
as if time finally has come now.
After googling around I noticed I'm not alone. Other people seem to hit
this issue, too when migrating to Artemis.
Don't you think it would be a good idea to officially deplo
Hi Herbert,
to implement the wild-card expansion you could use a custom transformer
[1], i.e.
public class PrefixAddressTransformer implements Transformer {
@Override
public Message transform(Message message) {
SimpleString originalAddress =
(SimpleString)message.getBrokerProperty(Mes
We have a Artemis 2.30.0 2 node cluster setup running in amazoncorretto:17
container image (Java 17 JRE), with persistance disabled.
We've had issues with high memory usage for our Artemis broker for a long time,
but recently several events raised a possible candidate to the cause. There
were
