Thanks for pointing out, it was missing
10
Thanks Again,
Prateek Jain
--
EXPECTATION : Causes all troubles..
--
On Mon, Mar 6, 2023 at 7:36 PM Justin Bertram wrote:
>
Thanks Justin.
Anyone has any thoughts on this. Any help or suggestions are greatly
appreciated.
Ekta Awasthi,
Engineer, EAI Operations & Support | Office Depot, Inc.
6600 North Military Trail | Boca Raton, FL 33496-2434
Office: 561-438-3552 | Mobile: 206-966-5577 |
The use-case you're describing is exactly the use-case that message
redistribution solves. This is different from what the documentation calls
"initial distribution" which is working properly according to your previous
explanation.
Can you confirm you read the documentation I linked previously?
Hi Justin,
Thanks for responding. Yes, message redistribution is configured and it is
working fine. The issue occurs when, producer is done with sending messages
but *no consumer is up till then*. Now, when a consumer comes up; it only
gets messages that are present on that particular node only
It sounds like you need to configure message redistribution [1]. Have you
done that?
Justin
[1]
https://activemq.apache.org/components/artemis/documentation/latest/clusters.html#message-redistribution
On Mon, Mar 6, 2023 at 12:17 PM prateekjai...@gmail.com <
prateekjai...@gmail.com> wrote:
>
Hi All,
I am facing an issue where, I have created a 3 node cluster of artemis and
created a distributed queue on it, for example exampleQueue.
When I send messages to this queue, messages are loadbalanced on each node.
If there is a consumer already listening/connected to any node in cluster
Hello users!
I'm using a (test) Artemis cluster with auto-discovery using jgroups+file_ping.
When master- or slave-nodes are added, Artemis shows them immediately after a
broker-diagram refresh.
When master-nodes are removed, and after the reconnect-attempts are exhausted,
the server forgets
