Async Scope in Mule 4 | Async in Mule 4

Async Scope in Mule 4

The Async scope is a branch processing block that executes simultaneously with the main flow. The main flow continues to execute while it initiates and processes the Async scope. The flow does not have to pause until the last message processor embedded in the asynchronous flow has completed its task.

Async can be useful for executing time-consuming operations that do not require you to send a response back to the initiating flow (such as printing a file or connecting to a mail server).

Async scope processes the nested list of message processors asynchronously using a thread pool.

flow of async scope:

Here in above flow, since we applied async scope in subflow it processes asynchronously in a separate thread while parent flow execute in separate thread.
So parent flow will not wait for child flow to execute and continue its processing irrespective of child flow.

URL : http://localhost:8085/async

Method : GET


XML Project Code:

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:http="" xmlns=""
       xmlns:xsi="" xsi:schemaLocation="">
       <http:listener-config name="HTTP_Listener_config" doc:name="HTTP Listener config" doc:id="32e8c48a-de6a-4a27-870f-dc9e2240af52" >
              <http:listener-connection host="" port="8085" />
       <flow name="test_asyncFlow" doc:id="761c4811-ddf5-4c4a-a75c-07b288cff799" >
              <http:listener doc:name="Listener" doc:id="9930e598-8827-487c-b402-85bd05f50282" config-ref="HTTP_Listener_config" path="/async"/>
              <async doc:name="Async" doc:id="918beb26-ca8b-4221-8693-11f511dc0891" >
                     <flow-ref doc:name="Flow Reference" doc:id="46f07222-8fcc-462d-9d87-acdeb5e78cbf" name="test_asyncFlow1"/>
                     <logger level="INFO" doc:name="Logger" doc:id="d0e30ad6-399f-48cb-9857-843381d6c664" message="First Logger"/>
              <logger level="INFO" doc:name="Logger" doc:id="6c2f2bfc-ae5f-431e-9443-31b2ef489feb" message="Second Logger"/>
       <flow name="test_asyncFlow1" doc:id="4c146020-1bc6-40b8-9e72-5be70add5fcc" >
              <logger level="INFO" doc:name="Logger" doc:id="5235ee3d-24df-41f8-af18-176034eb6c3c" message="In subflow........."/>

© 2020

Share on :

Mule 4:

XML to JSON in mule 4 Web service consumer VM Validation in Mule 4 Until Successful
Sub flow Set Variable & Remove Variable Set Transaction ID Scatter Gather Round Robin
Consume Restful Service CRUD in Mule 4 Parse Template Object to JSON Load Static Resource
JSON to XML Invoke Idempotent Filter ForEach Flat file to JSON
Fixwidth to JSON First Successful File Execute Error Handling
Email Dynamic Evaluate Custom Business Event CSV to JSON Copybook to JSON
Choice Router Async RabbitMQ

Mule 3:

Database Connector Async CXF Attachement XSLT
Mongo DB Cache scope Custom Business Event Gzip Compress Expression
SMTP For Each Expression Javascript Filter Reference
Salesforce Message Enricher Groovy Parse Template Idempotent
VM Poll Invoke Ruby Message
Webservice consumer Python Transformer reference Message Property Not
Collection Aggregator First Sucessful Catch Exception Strategy Reference Exception Strategy Or
Choice Message Chunk Aggregator Choice Exception Strategy Global Exception Strategy Schema Validation
Custom Aggregator Scatter Gather Custom Exception Strategy Batch Processing MEL
M Unit RAML Map Operator API Mocking Dataweave