A Mule 4 application has several VM queues and schedulers. Scheduler flows publish messages to VM queues. A set of other flows listens to those VM queues and have Redelivery Policy set:
<vm:listener queueName="producer.queue" doc:name="Listener" doc:id="c1e6ecd3-e67b-44e4-8946-d997e54bbb67" config-ref="VM_Config">
<redelivery-policy maxRedeliveryCount="0" idExpression="correlationId" useSecureHash="false"/>
</vm:listener>
If schedulers are triggered at the same time, the application gets stuck. In the thread dump threads similar to the below maybe observed:
"[MuleRuntime].io.22: [app-name-dev].invoke-system-data-produce-some-data-record.BLOCKING @36e90291" #356 prio=5 os_prio=0 tid=0x00007f25542c0800 nid=0xe09 waiting on condition [0x00007f250597d000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00000000e197a760> (a java.util.concurrent.SynchronousQueue$TransferStack) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362) at java.util.concurrent.SynchronousQueue.offer(SynchronousQueue.java:895) at org.mule.service.scheduler.internal.executor.WaitPolicy.rejectedExecution(WaitPolicy.java:67) at org.mule.service.scheduler.internal.executor.ByCallerThreadGroupPolicy.rejectedExecution(ByCallerThreadGroupPolicy.java:125) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) at org.mule.service.scheduler.internal.DefaultScheduler.execute(DefaultScheduler.java:419) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) at org.mule.runtime.core.internal.util.rx.ConditionalExecutorServiceDecorator.submit(ConditionalExecutorServiceDecorator.java:84) at reactor.core.scheduler.Schedulers.workerSchedule(Schedulers.java:700) at reactor.core.scheduler.ExecutorServiceWorker.schedule(ExecutorServiceWorker.java:41) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.trySchedule(FluxPublishOn.java:282) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.onNext(FluxPublishOn.java:225) at org.mule.runtime.core.privileged.processor.chain.AbstractMessageProcessorChain$1.onNext(AbstractMessageProcessorChain.java:260) at org.mule.runtime.core.privileged.processor.chain.AbstractMessageProcessorChain$1.onNext(AbstractMessageProcessorChain.java:253) at reactor.core.publisher.FluxFlatMap$FlatMapMain.drainLoop(FluxFlatMap.java:659) at reactor.core.publisher.FluxFlatMap$FlatMapMain.drain(FluxFlatMap.java:536) at reactor.core.publisher.FluxFlatMap$FlatMapInner.onNext(FluxFlatMap.java:932) at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1193) at reactor.core.publisher.MonoFlatMap$FlatMapInner.onNext(MonoFlatMap.java:241) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:73) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:73) at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onNext(FluxSwitchIfEmpty.java:67) at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1208) at reactor.core.publisher.MonoCallable.subscribe(MonoCallable.java:62) at reactor.core.publisher.Mono.subscribe(Mono.java:3006)
The above behavior is caused by a VM listener redelivery policy similar to the above-mentioned. Under certain conditions, for example, when several VM queues are populated at the same time, and the runtime thread pool scheduler tries to dispatch tasks to a limited number of CPU_LIGHT threads, the application gets blocked. As a result, the CPU_LIGHT thread pool exhausts and the application stops processing payloads.
More information on Mule 4 threading can be found here: https://docs.mulesoft.com/mule-runtime/latest/execution-engine
Mule Runtime 4.1.4
Mule Runtime 4.1.5
The issue MULE-16205 will be fixed in Mule Runtimes 4.1.6 and 4.2.0.
Mule Runtime 4.1.4
Mule Runtime 4.1.5
Refer to the following link which explains How to apply patches in Mule runtimes (standalone and in Studio).
Patched CloudHub 4.1.4 and 4.1.5 Runtimes has already been released on 12-17-2018 PST. Refer to the following article which explains How to update CloudHub Runtime Release versions to the latest one.
For any other unanswered questions, please ask Agentforce or raise a Support Case on the Salesforce Help site.
001117783

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.