请求-答复路由器不起作用

Question

我遇到了ule子中的请求-应答路由器的问题。 我正在使用3.子版本3.4.0。 request-reply用于fork-join模式，我在博客站点http://blogs.mulesoft.org/aggregation-with-mule-fork-and-join-pattern/上关注了本文。

    <request-reply>
      <all enableCorrelation="ALWAYS">
        <vm:outbound-endpoint path="PathA"/>
        <vm:outbound-endpoint path="PathB"/>
      </all>
      <vm:inbound-endpoint path="FinalResponse">
         <message-properties-transformer>
              <add-message-property key="MULE_CORRELATION_GROUP_SIZE" value="2" />
         </message-properties-transformer>
         <collection-aggregator />
      </vm:inbound-endpoint>
    </request-reply>

我面临的问题是未达到请求-答复后放置的处理器。在m子中，我看到2个响应已发送到FinalResponse vm端点。 我尝试将自己的自定义聚合器放置在collection-aggregator的位置。 但这没有达到。 我不确定如何调试此问题。 请注意，我在两个流中有2个这样的请求-答复路由器。 有人可以帮忙吗？

添加m子配置。 为了简洁起见，仅附加父流程和子流程之一

父流

    <flow name="ParentFlow" doc:name="ParentFlow" tracking:enable-default-events="true">
    <file:inbound-endpoint path="${SourceFilePath}"
        connector-ref="ParentFlowInboundConnector" 
        responseTimeout="10000" tracking:enable-default-events="true">
        <file:filename-regex-filter pattern="${REGEX}" caseSensitive="false"/>

    </file:inbound-endpoint>

    <object-to-string-transformer doc:name="Object to String"/>
    <message-properties-transformer
        doc:name="Message Properties">
        <add-message-property key="Source_System" value="XXX" />
        <add-message-property key="publisherName" value="YYY" />
        <add-message-property key="FlowName" value="ZZZ"/>
    </message-properties-transformer>
    <!-- This would store the message in the db -->
    <wire-tap>
        <vm:outbound-endpoint path="PERSITENCE.OUT"/>
    </wire-tap>

    <request-reply>
            <all doc:name="Move the message to all endpoints" enableCorrelation="ALWAYS">
                <vm:outbound-endpoint path="PathA"/>
                <vm:outbound-endpoint path="PathB"/>
                <vm:outbound-endpoint path="PathC"/>
                <vm:outbound-endpoint path="PathD"/>
            </all>
        <vm:inbound-endpoint path="Response">               
            <message-properties-transformer>                    
                <add-message-property key="MULE_CORRELATION_GROUP_SIZE" value="4" />                
            </message-properties-transformer>               
            <collection-aggregator failOnTimeout="false" doc:name="Collection Aggregator" />
        </vm:inbound-endpoint>

    </request-reply>
    <component class="ProcessorA"  />
    <component class="ProcessorB" />
    <exception-strategy ref="Exception Strategy" doc:name="Reference Exception Strategy"/>
</flow>

子流

<flow name="PathA" doc:name="PathA">
    <vm:inbound-endpoint path="PathA" >
        <vm:transaction action="ALWAYS_BEGIN"/>
    </vm:inbound-endpoint>
    <message-properties-transformer doc:name="Message Properties">                  
        <add-message-property key="originalFilename_processing" value="#[message.inboundProperties.originalFilename]" />                
    </message-properties-transformer>
    <message-properties-transformer doc:name="Message Properties">                  
        <add-message-property key="directory" value="#[message.inboundProperties.directory]" />             
    </message-properties-transformer>

    <message-properties-transformer doc:name="Message Properties">
        <add-message-property key="Destination_System" value="XXX" />
    </message-properties-transformer>

    <file:outbound-endpoint path="${OutPathA}" connector-ref="FileConnector_1" 
        tracking:enable-default-events="true"/>

    <!--Send email alerts -->
     <all doc:name="All" >
        <processor-chain>
            <message-property-filter pattern="turnOffEmail=false" caseSensitive="true" doc:name="Message Property"/>
            <custom-transformer class="com.XXX.YYY.ZZZ.VelocityTemplateResolver" doc:name="Java">
                <spring:property name="flowName" value="PPPP"/>
            </custom-transformer>
            <smtp:outbound-endpoint host="${SMTP_HOSTNAME}" port="${SMTP_PORT}" user="${SMTP_USERNAME}" password="${SMTP_PASSWORD}" to="${TO_ADDRESS}" from="${FROM_ADDRESS}" subject="${MAIL_SUBJECT}" cc="${MAIL_CC_ADDRESS}" bcc="${MAIL_BCC_ADDRESS}" responseTimeout="10000" transformer-refs="emailVelocityMessageTransformer"  tracking:enable-default-events="true"/>
        </processor-chain>
        <processor-chain>
            <message-property-filter pattern="turnOffEmail=false" caseSensitive="true" doc:name="Message Property"/>
            <custom-transformer class="com.XXX.YYY.ZZZ.VelocityTemplateResolver" doc:name="Java">
                <spring:property name="flowName" value="FlowName"/>
            </custom-transformer>
            <smtp:outbound-endpoint host="${SMTP_HOSTNAME}" port="${SMTP_PORT}" user="${SMTP_USERNAME}" password="${SMTP_PASSWORD}" to="${MAIL_TO_ADDRESS}" from="${MAIL_FROM_ADDRESS}" subject="${MAIL_SUBJECT}" cc="${MAIL_CC_ADDRESS}" bcc="${BCC_ADDRESS}" responseTimeout="10000" transformer-refs="emailVelocityMessageTransformer" tracking:enable-default-events="true"/>
        </processor-chain>
        <processor-chain>
            <message-property-filter pattern="turnOffEmail=false" caseSensitive="true" doc:name="Message Property"/>
            <custom-transformer class="com.XXX.YYY.ZZZ.VelocityTemplateResolver" doc:name="Java">
                <spring:property name="flowName" value="AAAA"/>
            </custom-transformer>
            <smtp:outbound-endpoint host="${SMTP_HOSTNAME}" port="${SMTP_PORT}" user="${SMTP_USERNAME}" password="${SMTP_PASSWORD}" to="${MAIL_TO_ADDRESS}" from="${MAIL_FROM_ADDRESS}" subject="${MAIL_SUBJECT}" cc="${MAIL_CC_ADDRESS}" bcc="${MAIL_BCC_ADDRESS}" responseTimeout="10000" transformer-refs="emailVelocityMessageTransformer" tracking:enable-default-events="true"/>
        </processor-chain>
    </all>
    <rollback-exception-strategy doc:name="Rollback Exception Strategy" maxRedeliveryAttempts="${MAX_REDELIVERY_ATTEMPTS}" enableNotifications="false">
        <logger message="==Rollback log ===" level="INFO" doc:name="Logger"/>
    </rollback-exception-strategy>
</flow>

Answer 1

该问题最可能的原因是相关性ID 。

您可能要检查发送到路径A和路径B的消息的相关性ID。在FinalResponse VM入站端点上收到的消息必须具有相同的相关性ID，否则它将不被接受为先前对消息的响应已发送。 换句话说，请求-应答将不会只接受入站端点中的任何内容，而只会接受与请求-应答路由器上发布的出站端点上的相关ID匹配的消息。

您可以使用此设置自定义相关性ID-

<set-property propertyName="MULE_CORRELATION_ID" value="some-correlation-id" />