VM queues and persistent queues by deployment
How VM Connector queues and operations behave, where a persistent VM queue actually keeps its messages on a standalone runtime, a cluster, CloudHub 1.0, CloudHub 2.0 and Runtime Fabric, and what to use when a VM queue cannot give the durability a design needs.
Design Mule applications using Virtual Machine (VM) queues and the Anypoint VM Connector in all deployment options.
~8 min read · 11 practice questions
What the exam expects
- Choose between transient and persistent VM queues, and design VM Connector configurations and queue names that an application or domain can use.
- Select the VM operation (Publish, Consume, Publish Consume, Listener) that matches a one-way handoff or a request that waits for a reply.
- State where a persistent VM queue keeps messages on a single runtime, in a customer-hosted cluster, on CloudHub 1.0, on CloudHub 2.0 and on Runtime Fabric.
- Recognize the CloudHub 1.0 Persistent queues behaviors that change a design: retention, delivery guarantees, latency, encryption and batch interaction.
- Pick a durable replacement (Anypoint MQ or an external JMS broker) where VM queues cannot meet the requirement.
VM Connector: intra-app and inter-app communication through asynchronous queues. Transient queue: faster, but not reliable if the system crashes. Persistent queue: slower but reliable (VM Connector). CloudHub persistent queues: a per-application CloudHub 1.0 setting that stores VM queue messages externally (Compare CloudHub and CloudHub 2.0). Memory grid: the shared memory a cluster uses for VM queue and Object Store data (HA cluster overview).
Key facts
- Detail
- TRANSIENT
- Detail
- 5 SECONDS
- Detail
- Memory grid; JMS where data must outlive the whole cluster
- Detail
- Local queues, no object store backups
- Detail
- All VM, Batch and SEDA queues
- Detail
- Up to 4 days
- Detail
- Duplicates possible, not one-time-only
- Detail
- Disabling makes earlier encrypted messages unreadable
- Detail
- 70 s default;
persistent.queue.min.timeoutmax 43000000 ms
- Detail
- Ephemeral; use Anypoint MQ
- Detail
- Persistent VM queues unavailable
- Detail
- Not supported on CloudHub
Sources for this section (8)
- Configure VM Connector in Studiodocs.mulesoft.com (opens in a new tab)
- VM Connector Referencedocs.mulesoft.com (opens in a new tab)
- HA cluster overviewdocs.mulesoft.com (opens in a new tab)
- Manage Queuesdocs.mulesoft.com (opens in a new tab)
- CloudHub HA featuresdocs.mulesoft.com (opens in a new tab)
- Compare CloudHub and CloudHub 2.0docs.mulesoft.com (opens in a new tab)
- VM Connectordocs.mulesoft.com (opens in a new tab)
- On-premises deployment modeldocs.mulesoft.com (opens in a new tab)
- Why can't two VM Connector configurations in one application each declare a queue with the same name?
- When Persistent queues is selected for a CloudHub 1.0 application that is already running, what must happen before the setting takes effect?
- In which region does a CloudHub 1.0 worker's persistent queue live?
- How often do the Queued and In-Flight columns on the Queues tab refresh?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Platform Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both