QuestionQ19

MuleSoft application network concepts

A cluster containing two customer-hosted Mule runtimes hosts an application with a flow that includes a JMS listener configured to subscribe to messages from a topic destination.

How should the JMS listener’s primaryNodeOnly parameter and subscription parameter be configured so the listener can receive messages on all nodes in the cluster while processing each message only once?

  • A Use the parameter primaryNodeOnly = “false” on the JMS listener with a shared subscription
  • B Use the parameter primaryNodeOnly = “false” on the JMS listener with a non-shared subscription
  • C Use the parameter primaryNodeOnly = “true” on the JMS listener with a non-shared subscription
  • D Use the parameter primaryNodeOnly = “true” on the JMS listener with a shared subscription
Explanation

Setting primaryNodeOnly to false runs the listener on every cluster node. For a topic, a JMS 2.0 shared subscription distributes each published message to only one of the subscription’s consumers, preventing duplicate processing across nodes. MuleSoft documents this clustered-topic configuration with primaryNodeOnly="false" and shared="true".

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!