To implement predictive maintenance on its machinery equipment, ACME Tractors has installed thousands of IoT sensors that will send data for each…

To maximize performance and concurrency in a multi-node cluster, the JMS Listener should be active on all nodes and use multiple consumers on each node. Setting primaryNodeOnly = false enables the listener on every node in the cluster. Setting numberOfConsumers to a value greater than one creates multiple concurrent message-consuming threads on each of those active nodes. Since JMS queues guarantee that a message is delivered to only one consumer, this setup achieves maximum parallel processing while maintaining the "exactly-once" processing requirement.

A: This configuration underutilizes each node by only allowing one consumer, limiting concurrency and performance.

B: This is the least performant option, restricting processing to a single thread on a single node in the entire cluster.

C: This configuration fails to utilize the other nodes in the cluster for message processing, limiting overall throughput.

1. MuleSoft Documentation, "JMS Connector - Listener". Under the "Clustering" section for the JMS Listener, it states: "If you set primaryNodeOnly to false (the default), every node in the cluster has an active message source."

2. MuleSoft Documentation, "JMS Connector - Listener". The documentation for the numberOfConsumers parameter explains it controls "The number of concurrent consumers for this listener." To maximize concurrency, this should be greater than one.