如何解决m子3中导致异常“ IllegalArgumentException：FlowConstruct不能为null”的根本原因是什么？
我正在尝试在mule 3.9中的事务中执行更新语句和插入语句。我将这2个DB资源包含在一个多事务组件中。当它尝试部署应用程序时，我得到以下异常。但是，当我删除事务性组件并且只有2个数据库资源组件时，我没有收到任何部署错误，并且应用程序运行良好。出现以下错误的原因是什么？
*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>
解决方法
我发现了问题。我没有对事务组件使用任何捕获策略。因此，它引用了我的应用程序中定义的默认异常处理策略。该策略没有任何关联的流程构造。为了解决这个问题，我为事务组件创建了捕获异常策略，并且效果很好。
版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 dio@foxmail.com 举报，一经查实，本站将立刻删除。