WSO2 ESB：如何在Iterate中介器中实现阻塞式调用？

Let's break down what's going wrong here and fix it step by step.

First, you're dealing with two core issues:

1. Even with sequential="true", requests are still sending in parallel and triggering "too many requests" errors
2. Neither Call nor Callout mediators are sending any requests to the target URL

Why sequential="true" didn't work as expected #

The sequential flag in the Iterate mediator only guarantees child sequences are started in order, but WSO2 ESB still uses a thread pool to process them by default. On top of that, your continueParent="true" setting lets the parent message flow continue while iterated requests run, which amplifies the parallel execution behavior.

Why Call(blocking=true) didn't send requests #

Looking at your config, your Endpoint uses uri-template="{uri.var.getrecordfile}", but you're setting a property named XXXX instead of uri.var.getrecordfile. The variable isn't being populated correctly, so the Call mediator has no valid target URL to hit—hence no requests going out.

The Fix: Proper Sequential Execution in Iterate #

Here's a corrected configuration that ensures sequential calls, fixes the missing requests, and addresses the rate limiting issue:

Step 1: Fix the Target URL Variable

First, correct the property name to match the uri-template variable:

<property name="uri.var.getrecordfile" scope="default" type="STRING" value="https://XXXX" />

Step 2: Adjust Iterate & Add Aggregate

Set continueParent="false" to pause the parent message until all iterations complete, and add an Aggregate mediator to wait for all child requests. This is critical for true sequential execution.

Full Working Configuration

<!-- Explicitly set an ID for Iterate to link with Aggregate -->
<iterate id="recordIteration" continueParent="false" expression="//Data" sequential="true">
 <target>
 <sequence>
 <log level="custom">
 <property name="Check>>>>>>>>>>>>" value="Inside Iterator - Processing RecordId: //Data/RecordId" />
 </log>
 <payloadFactory media-type="json">
 <format>{"RecordID":"$1" }</format>
 <args>
 <arg evaluator="xml" expression="//Data/RecordId" />
 </args>
 </payloadFactory>
 <!-- Corrected property name for target URL -->
 <property name="uri.var.getrecordfile" scope="default" type="STRING" value="https://XXXX" />
 <property expression="fn:concat('Basic ', base64Encode('XXXXX'))" name="Authorization" scope="transport" type="STRING" />
 <!-- Blocking=true ensures each request finishes before the next iteration starts -->
 <call blocking="true">
 <endpoint>
 <http method="post" uri-template="{uri.var.getrecordfile}">
 <timeout>
 <duration>30000</duration> <!-- 30-second timeout to avoid hanging requests -->
 <responseAction>fault</responseAction>
 </timeout>
 <suspendOnFailure>
 <initialDuration>-1</initialDuration>
 <progressionFactor>1</progressionFactor>
 </suspendOnFailure>
 <markForSuspension>
 <retriesBeforeSuspension>0</retriesBeforeSuspension>
 </markForSuspension>
 </http>
 </endpoint>
 </call>
 <log level="custom">
 <property expression="json-eval($)" name="RESPONSE >>>>" />
 <property expression="$trp:Status" name="Status" />
 </log>
 </sequence>
 </target>
</iterate>

<!-- Aggregate waits for all iterations to complete -->
<aggregate id="recordIteration">
 <completeCondition>
 <messageCount max="-1" min="-1"/>
 </completeCondition>
 <onComplete expression="//Data">
 <log level="custom">
 <property name="Iteration_Complete" value="All records processed sequentially" />
 </log>
 <!-- Add post-processing logic here if needed -->
 </onComplete>
</aggregate>

Extra Tips to Avoid Rate Limiting #

If the target endpoint's rate limits are strict, add a delay between requests to stay under the threshold:

<!-- Insert this right before the Call mediator -->
<delay>
 <duration>1000</duration> <!-- 1-second delay; adjust based on the endpoint's rate limit -->
</delay>

Why This Works #

• continueParent="false" stops the parent message flow until all iterations are done, preventing parallel execution between parent and child requests.
• sequential="true" + Call(blocking=true) ensures each child request completes fully before the next iteration starts—this is the key to true sequential processing.
• Fixing the property name gives the Call mediator a valid target URL, so requests are sent correctly.

内容的提问来源于stack exchange，提问作者SDS