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
2 months agoShannon
3 months agoElbert
3 months agoTambra
3 months agoKanisha
3 months agoJuliann
3 months agoJannette
4 months agoLeslie
4 months agoRhea
4 months agoLeontine
4 months agoLuther
4 months agoMadalyn
5 months agoTyisha
5 months agoEsteban
10 months agoRutha
9 months agoStefan
9 months agoGeraldine
9 months agoNoel
10 months agoFidelia
10 months agoKeith
8 months agoKristeen
9 months agoAlethea
9 months agoLeatha
10 months agoRaina
10 months agoEdward
11 months agoCraig
11 months agoAlease
10 months agoRoxane
10 months agoRaina
11 months ago