3. Introduction
• You can use the Java Virtual Machine (VM) transport for intra-JVM
communication between Mule flows. This transport by default uses
in-memory queues but can optionally be configured to use persistent
queues. Note: VM file persistency does not work on clusters
7. Features
• The in memory (VM) transport has two modes of operation: One for use
with request-response and another for use with one-way endpoints.
• request-response:
When using request-response endpoints, messages are delivered directly from an
outbound vm endpoint to the inbound vm endpoint that is listening on the same path.
This delivery is blocking and occurs in the same thread. If there is no inbound request-
response VM endpoint in the same Mule application that is listening on this path, then
dispatching a message from the outbound endpoint fails.
• one-way:
When using one-way endpoints, messages are delivered to the corresponding inbound
endpoint via a queue. This delivery is non-blocking. If there is no inbound one-
wayendpoint in the same Mule application listening on this path, then, although
dispatching of the message succeeds, the message remains in the queue. By default,
this queue is in memory, but it is also possible to configure a persistent queue that
uses the file system as its persistence mechanism.