wso2esb 死信通道在 4.9.0 版本中不起作用

Question

很简单的问题。我正在使用 vanilla wso2esb 4.9.0 并尝试死信通道设计。它失败！存储在队列中的消息是端点接收到的肥皂故障错误。我究竟做错了什么？这是工作吧？我下面的例子是：https://docs.wso2.com/display/IntegrationPatterns/Dead+Letter+Channel

<proxy xmlns="http://ws.apache.org/ns/synapse" name="Proxy1"
transports="https,http" statistics="disable" trace="disable"
startOnLoad="true">
<target>
    <inSequence>
        <log level="full" />
    </inSequence>
    <outSequence>
        <log level="full">
            <property name="MSG" value="Response...." />
        </log>
        <send />
    </outSequence>
    <faultSequence>
        <log level="full">
            <property name="MSG" value="++++++++++FAULT---------...." />
        </log>
        <property name="target.endpoint" value="ReportDataTransferServiceEp" />
        <store messageStore="ReportMessageStore" />
    </faultSequence>
    <endpoint>
        <address uri="http://localhost:8080/TestSoapESB/webservices/ReportDataTransferService" />
    </endpoint>
</target>
<publishWSDL
    uri="http://localhost:8080/TestSoapESB/webservices/ReportDataTransferService?wsdl" />
<description></description>

Answer 1

作为 outSequence 内部，您知道当前消息是响应而不是 inSequence 内部收到的初始消息，在 faultSequence 中，您不能依赖初始消息将保持不变的事实：您必须将其保存在inSequence 的顶部并在调用 store in faultSequence 之前恢复它：

保存：

<enrich>
    <source type="envelope" clone="true"/>
    <target type="property" property="INPUT_MESSAGE"/>
</enrich>

恢复：

<enrich>
    <source type="property" clone="false" property="INPUT_MESSAGE"/>
    <target type="envelope"/>
</enrich>