If you're talking about queues, that's expected behavior. A queue message
exists on only one broker in an NoB, so the two on-prem brokers will
complete for queue messages from your us-east master.
If you're talking about topics, then that's very unexpected behavior and we
should dig deeper.
And t
Hi everyone!
I am having an issue where a subscriber is not running and messages get sent
to the DLQ. The messages are marked 'Persistent'. Is there a way I can make
the DLQ 'persistent' messages to get deleted after a 24h period?
I don't care about redelivery or any kind of checking at this poin
My Setup:
Systems:
>OS: Windows Servers 2016
>ActiveMQ Version: 5.14.5
>Java: 1.8.141
I have setup 2 - 3 node Master/Slave/Slave clusters on AWS
2 on-prem ActiveMQ servers
>1 running 5.14.5
>1 running 5.10.0
Current network configuration
Germany (AWS) <-> USEast (AWS) <-> Cambridge (on-prem)
Sometimes my consumer clients encourages with 204 content not fount http
header although the broker has . It happes more than nearly 2 hours and
works normally after this time. I see this header status every day at night.
There is no error, no warning just have all consumers get 204 no content at
t
