An integration Mule application is deployed to a customer-hosted multi-node Mule 4 runtime duster. The Mule application uses a Listener operation of a JMS connector to receive incoming messages from a JMS queue.
How are the messages consumed by the Mule application?
Correct answer is Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node
For applications running in clusters, you have to keep in mind the concept of primary node and how the connector will behave. When running in a cluster, the JMS listener default behavior will be to receive messages only in the primary node, no matter what kind of destination you are consuming from. In case of consuming messages from a Queue, you'll want to change this configuration to receive messages in all the nodes of the cluster, not just the primary.
This can be done with the primaryNodeOnly parameter:
<jms:listener config-ref='config' destination='${inputQueue}' primaryNodeOnly='false'/>
Herminia
4 months agoShannon
4 months agoElbert
5 months agoTambra
5 months agoKanisha
5 months agoJuliann
5 months agoJannette
5 months agoLeslie
6 months agoRhea
6 months agoLeontine
6 months agoLuther
6 months agoMadalyn
6 months agoTyisha
7 months agoEsteban
12 months agoRutha
11 months agoStefan
11 months agoGeraldine
11 months agoNoel
12 months agoFidelia
12 months agoKeith
10 months agoKristeen
11 months agoAlethea
11 months agoLeatha
12 months agoRaina
1 year agoEdward
1 year agoCraig
1 year agoAlease
12 months agoRoxane
12 months agoRaina
1 year ago