Mule vm:未触发入站端点

时间:2016-12-07 16:11:30

标签: java mule

我有一个列表,我想在paraller中处理,所以在调用collection-splitter之后,我将每条记录发布到出站端点,但是没有触发接收入站端点。 配置如下;

<flow name="ProcessPolledOrders" doc:name="ProcessPolledOrders">
        <set-session-variable variableName="fileName" value="#[message.payload.orderBatch.orderSourceName]" />
        <set-session-variable variableName="batchId" value="#[message.payload.orderBatch.id]" />
        <logger message="************* Item: #[sessionVars.fileName] processing resumed. ***********" level="INFO"/>
        <component>
            <spring-object bean="PolledOrderSplitter"/>
        </component>
        <set-session-variable variableName="size" value="#[message.payload.size()"/>
        <collection-splitter/>
        <set-property propertyName="MULE_CORRELATION_GROUP_SIZE" value="#[sessionVars.size]" />
        <set-property propertyName="MULE_CORRELATION_ID" value="#[sessionVars.fileName]" />
        <choice>
            <when>
                <payload-type-filter expectedType="model.Order"/>
                <vm:outbound-endpoint exchange-pattern="one-way" path="step2" doc:name="VM"/>
            </when>
            <otherwise>
                <echo-component/>
            </otherwise>
        </choice>
    </flow>

<flow name="PollerOrderProcessingFlow" doc:name="PollerOrderProcessingFlow">
        <vm:inbound-endpoint exchange-pattern="one-way" path="step2" doc:name="VM"/>
        <logger message="***************** Validating order with id #[message.payload.id] ********************"
                level="INFO"/>
        <component>
            <spring-object bean="PolledOrderValidationComponent"/>
        </component>
        <collection-aggregator timeout="600000" failOnTimeout="false"
                               doc:name="Validated Orders Aggregator"/>
        <component>
            <spring-object bean="BatchOrderUpdateComponent"/>
        </component>
        <default-exception-strategy>
            <flow-ref name="ValidationProcessingExceptionFlow" />
        </default-exception-strategy>
    </flow>

1 个答案:

答案 0 :(得分:0)

你有任何例外吗?尝试调试,看看消息丢失的位置?我试过类似的流程并且对我来说工作正常。