Loading
Slack 관련 문의처가 Salesforce Help로 통합 및 변경됩니다.더 많이 읽기

Mule 4 VM Listener Redelivery Policy Blocks CPU_LITE Threads When Multiple Events Are Triggered Simultaneously

게시 일자: Mar 25, 2026
솔루션

SYMPTOMS

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)

CAUSE

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

PRODUCTS AFFECTED

Mule Runtime 4.1.4
Mule Runtime 4.1.5

SOLUTION

The issue MULE-16205 will be fixed in Mule Runtimes 4.1.6 and 4.2.0.

  • For Standalone Mule Runtimes 4.1.4 and 4.1.5 please download a respective patch: 

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).

  • For CloudHub Runtimes:

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.

Attachments

Mule Runtime 4.1.4
Mule Runtime 4.1.5

Knowledge 기사 번호

001117783

 
로드 중
Salesforce Help | Article