An integration Mule application is deployed to a customer-hosted multi-node Mule 4 runtime cluster. 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?
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. This setup allows for flexible configuration to accommodate different load balancing and high availability requirements. The primary cluster node setting ensures that all messages are handled by a specific node, while other configurations allow for messages to be distributed among available nodes, optimizing resource usage and reliability.
D is correct - https://dzone.com/articles/deep-dive-into-jms-integration-patterns-with-mules
D. 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
D. I think.
D, because its queue not topic so all the nodes cant consume, only one listener can consume.
D is the answer
D The configurations primaryNodeOnly, shared-subscriptions, and topics may affect if only primary node or the other nodes will process receiving messages.
in connector configuration, we have the configuration name "make primary node" if we enable this then this worker is only responsible for processing all the messages to prevent duplicacy, if we didn't enable it then every worker is responsible to process the message Ans D
D. 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
D is the answer
it is D
should be D
With listener-based connector (JMS, VM) traffic is distributed automatically or load balanced both in CloudHub and cluster. This means, even if primarynode=false the load distribution will be taken care of.
This is the expected behaviour to achieve load balancing. Can be set to isPrimaryNode = true as well.
In a customer-hosted multi-node runtime cluster, a JMS listener can be configured to decide where the messages are consumed: primary node only or all nodes. D is the correct answer