Multi Threading issues with Scheduled Jobs | Receiver Thread Pools in MuleSoft

[@mohanbapuji]

I can't ask for more on thread pooling concept with such a clear illustration.
Thanks Jason.

[@weswill192]

Great video! You explain compicated topics very well. Your mulesoft tutorials are terrific! Thanks much!

[@suryaveer1794]

Thanks Jason , you are really most hardworking mule developer/ Architect (ACC to LinkedIn).Will wait for other videos.

[@Senai88]

That is an awesome Mulesoft jacket!

[@shubhamrendalkar7569]

How can we do the same thing with 'Schedular' in Mule-4?

[@thedeveloper2513]

Good explanation Jason. Can you tell me how the Thread Pool is working on Mule 4. And please keep up the advanced topics.

[@amitmohan4011]

How it will work in Mule 4 scenario as we don't as processing strategies in mule 4 ?

[@bogdanpopey]

There is no more processing strategy in Mule 4 .Mule Runtime is designed on the concept/processing strategy called Non-Blocking processing Strategy.
Mule Runtime is smart enough to do anything based on current event processor related to processing strategy.
So no need to define anything for any connector.
Mule Runtime is Non-Blocking Engine now in Mule 4.

[@emuralimba]

there is lots of differences in mule3 and mule4. Is there a way to simulate similar scenario for mule4? Quartz connector no longer in mule4 and now we have only scheduler here.

[@sachindubey9411]

you can set max concurrency to 1 for the flow

[@AZeeee]

Any idea of how we can limit the number of threads spawned / processed by VM outbound / Inbout ? I tried steps similar to yours but was not successful.

[@sachindubey9411]

you can set max concurrency to 1 for the flow

[@MahisMemories]

Thank you for the video sir..

[@bobwoodard]

How about more videos with some being more technical? :-)

[@vijaydhanakodi5591]

Not worth for 17 min Jason. I thought you are going to explain a creative way to fix this.