我有一个以调度器为源的流。这个调度程序有一个cron表达式，让它在每月15日凌晨4点执行
0 0 4 15 * ? *
但在某种程度上，这个流程被执行了两次。15日以及16日。以下是cloudHub日志条目。
没有多个调度程序，应用程序正在使用.2vCore.的1个Worker上工作
如果有人以前遇到过这个问题，请告诉我。
Mule运行时版本：4.4.0同样的问题也出现在发展环境中。
(我已经从日志信息中删除了机密信息(
[2022-08-15 04:00:07.898] INFO org.mule.extension.jsonlogger.JsonLogger [[MuleRuntime].uber.11911:fifteenthDayOfMonth-scheduler-flow.BLOCKING @72141012]: event:c0603230-1c4e-11ed-b2fc-1264ce2d1c7b {
"correlationId" : "c06031230-1c41e-11ed-b2fc-1264c1e2d1c7b231",
"message" : "Begin Schedular flow",
"tracePoint" : "START",
"priority" : "INFO",
"elapsed" : 0,
"locationInfo" : {
"lineInFile" : "51",
"component" : "json-logger:logger",
"fileName" : "schedulers.xml",
"rootContainer" : "fifteenthDayOfMonth-scheduler-flow"
},
"timestamp" : "2022-08-15T04:00:07.897Z",
"content" : { },
"applicationName" : "biz-prc-ent-finance-bulk-api-prod",
"applicationVersion" : "v1",
"environment" : "prod"
}
[2022-08-16 04:00:03.577] INFO org.mule.extension.jsonlogger.JsonLogger [[MuleRuntime].uber.12580:fifteenthDayOfMonth-scheduler-flow.BLOCKING @72141012]: event:e8364f00-1d17-11ed-b2fc-1264ce2d1c7b {
"correlationId" : "e8364f006-1d17-11ed-b2f6c-1264ce26d1c7b12334",
"message" : "Begin Schedular flow",
"tracePoint" : "START",
"priority" : "INFO",
"elapsed" : 0,
"locationInfo" : {
"lineInFile" : "51",
"component" : "json-logger:logger",
"fileName" : "schedulers.xml",
"rootContainer" : "fifteenthDayOfMonth-scheduler-flow"
},
"timestamp" : "2022-08-16T04:00:03.575Z",
"content" : { },
"applicationName" : "biz-prc-ent-finance-bulk-api-prod",
"applicationVersion" : "v1",
"environment" : "prod"
}
流xml
<flow name="workday-netsuite-journal-fifteenthDayOfMonth-scheduler-flow" doc:id="79a57c74-36ea-48db-ba49-3c54157fc6e0">
<scheduler doc:name="Schedule @ every fifteenthDayOfMonth" doc:id="666bf73a-82ad-42f8-8775-d84ce86b542e" >
<scheduling-strategy >
<cron expression="${cron.journal.fifteenthDayOfMonth}" />
</scheduling-strategy>
</scheduler>
<json-logger:logger doc:name="Begin Schedular flow - Workday Journal Sync to Netsuite " doc:id="eb92ea96-8285-4403-a9bd-c4425022d07e" config-ref="JSON_Logger_Config" message="Begin Schedular flow - Workday Journal Sync to Netsuite "/>
<flow-ref doc:name="getlookdatafromnetsuite" doc:id="b6917c50-ed4b-414d-aa50-cb7994203218" name="getlookdatafromnetsuite"/>
<set-payload value="#['regularrun-getworkdaydataflow']" doc:name="Set Payload" doc:id="3f9d33a5-6a56-427c-b58b-6efdc6d1dfdd" />
<flow-ref doc:name='workday-netsuite-impl-flow' doc:id="14f6171c-ce9d-4c68-8f28-e1437c652097" name="workday-netsuite-impl-flow"/>
<json-logger:logger doc:name="End Of Schedular flow - Workday Journal Sync to Netsuite " doc:id="852a1da4-0be4-4461-b60f-1a3fb7b23f52" config-ref="JSON_Logger_Config" message="End Of Schedular flow - Workday Journal Sync to Netsuite " tracePoint="END"/>
<error-handler ref="workday-netsuite-implError_Handler_Propagate" />
</flow>
如果完成流执行花费太多时间，CloudHub调度程序可以重新触发。查看执行的总时间。如果存在阻碍事件完成的瓶颈，则线程转储可能有助于分析。