Mule 异常的根本原因是什么;IllegalArgumentException:FlowConstruct不能为null;在骡子3?
我试图在mule 3.9中的事务中执行update语句和insert语句。我将这些2db资源包含在一个多事务组件中。当它尝试部署应用程序时,我遇到以下异常。但当我删除事务组件并且只有2db资源组件时,我并没有得到任何部署错误,应用程序运行正常。以下错误的原因是什么Mule 异常的根本原因是什么;IllegalArgumentException:FlowConstruct不能为null;在骡子3?,mule,mule-component,mulesoft,mule-esb,Mule,Mule Component,Mulesoft,Mule Esb,我试图在mule 3.9中的事务中执行update语句和insert语句。我将这些2db资源包含在一个多事务组件中。当它尝试部署应用程序时,我遇到以下异常。但当我删除事务组件并且只有2db资源组件时,我并没有得到任何部署错误,应用程序运行正常。以下错误的原因是什么 *Caused by: java.lang.IllegalArgumentException: FlowConstruct cannot be null at org.mule.processor.AsyncDelegateMessa
*Caused by: java.lang.IllegalArgumentException: FlowConstruct cannot be null
at org.mule.processor.AsyncDelegateMessageProcessor.validateFlowConstruct(AsyncDelegateMessageProcessor.java:117) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.processor.AsyncDelegateMessageProcessor.initialise(AsyncDelegateMessageProcessor.java:87) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.processor.AbstractMuleObjectOwner.initialise(AbstractMuleObjectOwner.java:72) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.exception.AbstractExceptionListener.initialise(AbstractExceptionListener.java:164) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.processor.AbstractMuleObjectOwner.initialise(AbstractMuleObjectOwner.java:72) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.exception.ChoiceMessagingExceptionStrategy.initialise(ChoiceMessagingExceptionStrategy.java:78) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.processor.TransactionalInterceptingMessageProcessor.initialise(TransactionalInterceptingMessageProcessor.java:93) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.processor.chain.AbstractMessageProcessorChain.initialise(AbstractMessageProcessorChain.java:87) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.processor.chain.AbstractMessageProcessorChain.initialise(AbstractMessageProcessorChain.java:87) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.routing.AbstractSelectiveRouter.initialise(AbstractSelectiveRouter.java:89) ~[mule-core-3.9.1.jar:3.9.1]
at org.mule.processor.chain.AbstractMessageProcessorChain.initialise(AbstractMessageProcessorChain.java:87) ~[mule-core-3.9.1.jar:3.9.1]*
错误代码:
工作代码:
我发现了问题。我没有对事务组件使用任何捕获策略。因此,它指的是应用程序中定义的默认异常处理策略。该策略没有任何关联的流构造。为了修复此问题,我为事务组件创建了捕获异常策略,它工作正常。请在错误消息中添加这些组件周围的流以及任何额外的行。当然,我现在就添加它。添加了完整的流和错误详细信息
<choice doc:name="Master Switch">
<when expression="#[(flowVars.MasterSwitch != null and flowVars.MasterSwitch.flag != null and flowVars.MasterSwitch.flag.DATA_VALUE.equalsIgnoreCase('Y'))]">
<set-variable variableName="payloadCopy" value="#[payload]" doc:name="Original payload" />
<flow-ref name="generate_unique_entity_id" doc:name="generate_unique_entity_id"/>
<message-properties-transformer scope="invocation" doc:name="Message Properties">
<add-message-property key="HistCreatedDate" value="#[server.dateTime.format('yyyy-MM-dd hh:mm:ss.SSSSSSSSS')]"/>
<add-message-property key="HistoryId" value="#[flowVars.uniqueEntityId]"/>
<add-message-property key="HistLastUpdatedDt" value="#[server.dateTime.format('yyyy-MM-dd hh:mm:ss.SSSSSSSSS')]"/>
<add-message-property key="HistChannelId" value="${hist_channel_id}"/>
<add-message-property key="HistAppId" value="${hist_app_id}"/>
</message-properties-transformer>
<set-variable variableName="lastIndicator" value="Y" doc:name="lastIndicator column value"/>
<ee:multi-transactional action="ALWAYS_BEGIN" doc:name="Transactional">
<db:update config-ref="Generic_Database_Configuration" doc:name="Database" transactionalAction="ALWAYS_JOIN">
<db:parameterized-query><![CDATA[${x_hist_update}]]></db:parameterized-query>
</db:update>
<db:insert config-ref="Generic_Database_Configuration" doc:name="x_hist" transactionalAction="ALWAYS_JOIN">
<db:parameterized-query><![CDATA[${x_hist_insert}]]></db:parameterized-query>
</db:insert>
</ee:multi-transactional>
<set-payload value="#[flowVars.payloadCopy]" doc:name="Payload before Flow" />
</when>
<otherwise>
<logger message="${logger.info} --- Skipping flow as the master switch is turned off." level="INFO" category="appinfologger" doc:name="Switch off logger"/>
</otherwise>
</choice>
<choice-exception-strategy doc:name="Choice Exception Strategy">
<catch-exception-strategy when="#[exception.causedBy(java.lang.Exception)]" doc:name="Catch Exception Strategy">
<logger level="INFO" doc:name="Logger" category="appinfologger" message="${logger.info} - x hist transaction failed"/>
</catch-exception-strategy>
</choice-exception-strategy>
</flow>
<choice doc:name="Master Switch">
<when expression="#[(flowVars.MasterSwitch != null and flowVars.MasterSwitch.flag != null and flowVars.MasterSwitch.flag.DATA_VALUE.equalsIgnoreCase('Y'))]">
<set-variable variableName="payloadCopy" value="#[payload]" doc:name="Original payload" />
<flow-ref name="generate_unique_entity_id" doc:name="generate_unique_entity_id"/>
<message-properties-transformer scope="invocation" doc:name="Message Properties">
<add-message-property key="HistCreatedDate" value="#[server.dateTime.format('yyyy-MM-dd hh:mm:ss.SSSSSSSSS')]"/>
<add-message-property key="HistoryId" value="#[flowVars.uniqueEntityId]"/>
<add-message-property key="HistLastUpdatedDt" value="#[server.dateTime.format('yyyy-MM-dd hh:mm:ss.SSSSSSSSS')]"/>
<add-message-property key="HistChannelId" value="${hist_channel_id}"/>
<add-message-property key="HistAppId" value="${hist_app_id}"/>
</message-properties-transformer>
<set-variable variableName="lastIndicator" value="Y" doc:name="lastIndicator column value"/>
<db:update config-ref="Generic_Database_Configuration" doc:name="Database" >
<db:parameterized-query><![CDATA[${x_hist_update}]]></db:parameterized-query>
</db:update>
<db:insert config-ref="Generic_Database_Configuration" doc:name="x_hist" >
<db:parameterized-query><![CDATA[${x_hist_insert}]]></db:parameterized-query>
</db:insert>
<set-payload value="#[flowVars.payloadCopy]" doc:name="Payload before Flow" />
</when>
<otherwise>
<logger message="${logger.info} --- Skipping flow as the master switch is turned off." level="INFO" category="appinfologger" doc:name="Switch off logger"/>
</otherwise>
</choice>
<choice-exception-strategy doc:name="Choice Exception Strategy">
<catch-exception-strategy when="#[exception.causedBy(java.lang.Exception)]" doc:name="Catch Exception Strategy">
<logger level="INFO" doc:name="Logger" category="appinfologger" message="${logger.info} - x hist transaction failed"/>
</catch-exception-strategy>
</choice-exception-strategy>
</flow>