Java ExecutorService - Part 1

[@MoZaHo]

Best description and video of the ExecuterService on the internet. Helped a great load. Thank you

[@JakobJenkov]

Thank you very much for your kind words! :-) ... and for taking the time to tell me! :-)

[@karthikgsarode900]

Detailed, to the point explanation. Thanks a lot Jacob!

[@JakobJenkov]

You are welcome ! :-)

[@fatihmehmetkose]

Thanks Jacob! this is the best explanation of ExecuterService and Callable I have seen...

[@JakobJenkov]

Thank you! I am happy my video was helpful to you! Actually, the video is a re-recording of an old video about the Java ExectutorService which I felt could be improved. Seems like it was indeed an improvement from the old version :-)

[@BtXFWkyZBtXFWkyZ]

Reminder is set, thanks for the content sir

[@JakobJenkov]

Always welcome :-)

[@Jagan3559]

It was very nicely put and easy to understand

[@JakobJenkov]

Thank you ! I am happy you feel like that ! :-)

[@mouradlaraba]

Thnaks a lot sir your courses are very helpfull, you are very generous in sharing your knowledge with us thnaks a lot

[@JakobJenkov]

You are most welcome! :-) ... I hope my videos help you!

[@Dayakar-vi5dh]

Thank you sir, For clear cut explanation.

[@JakobJenkov]

You are welcome ! :-)

[@LuneAgent]

Great Scott! We can get a result back from the future!

[@JakobJenkov]

:-) ... well, not to ruin your pun - but it's probably more correct to say that we wait for the Future to become the present and then we obtain the result ;-)

[@LuneAgent]

@@JakobJenkov Yeah, I know how it works, but it sounds great when described that way :)

[@ahmetbcakici]

Thanks for the content! It ıs really so useful and easy to understand.

[@JakobJenkov]

Thanks! I am glad you feel that way ! :-)

[@mdshafi7043]

Sir , Can you please make a video or 2 on deadlock situation in multithreading and how to handle them in java ? Your videos are very helpful.I understand multithreading well by watching your videos

[@JakobJenkov]

Hmm... I probably could :-) ... I think I will get to that topic soon.

[@강승윤-n4w]

I love your tutorial web site and also like this video ! It's really helpful. Thanks a lot !

[@JakobJenkov]

You are welcome! Glad you like it all! :-)

[@tomasma4896]

Thanks a lot for these videos. I am programming few years in Java but there is always something new I learn from your videos or from your web site. You definitely deserve more subscribers. Just an advice, maybe instead of old way anonymous classes you could use lambdas. But anyway good job and keep doing!

[@JakobJenkov]

Hi Tomas, thank you for your kind words! :-) ... in this video I chose to use anonymous classes instead of lambdas to make it 100% clear that it is the Runnable / Callable interface that are being implemented! In my own code I would most likely use lambdas - but for instructional purposes I often simplify the code somewhat - to keep focus on the important parts. By the way, I also often learn something new when I write tutorials or make videos :-)

[@pv2930]

U deserve more subscribers 👍

[@JakobJenkov]

Thank you :-)

[@sam_paul]

Very well explained.. Thank you very much !

[@JakobJenkov]

You are welcome! :-)

[@sumanshekhar8110]

I think invokeAny() starts executing all the task in the Colection, and returns the o/p of the task which completed First. After this all the tasks are canceled. Btw thanks for the awesome explaination. We want more of your knowledge :p

[@JakobJenkov]

Thanks - and thanks for the input !! These constructs are sometimes a bit hard to get to know correctly 😊

[@smitmandavia5044]

Thanks a lot for the video and other videos in this playlist. They are really useful. I think one small suggestion is to clarify that how is this different than thread Pools (explained in previous video). I guess Thread pool was our own simple implementation whereas this is an inbuilt and more nuanced version of it. Please correct me if I am wrong or missed anything.

[@JakobJenkov]

The Java ExecutorService is very similar to a thread pool. Some of them are implemented as thread pools, but some of them are a bit more advanced, like the ForkAndJoinPool .

[@garimadhanania1853]

great content as always!

[@JakobJenkov]

Thank you !! 😊😊😊

[@roman_mf]

Hi Jakob, thanks for another excellent explanation. I have a question about invokeAny() - you say that it executes one task, but you also that the one that executes fastest gets to send its return value. How does "fastest" work in this case? Do all tasks in a collection run concurrently and they just race for who finishes execution first? invokeAny sounds almost like it just picks one task and has some logic of a failure in execution, like a timeout.

[@JakobJenkov]

The ExecutorService will attempt to start as many of the tasks as possible, and whatever task finishes first has its result returned. I don't know the exact logic used internally, unfortunately. I have never needed invokeAny() myself.

[@devalshah69]

Hey Jakob thanks you for such a detailed video explanation of the Java concurrency. I am not able to find this codes of Executor services in your github repo, is there anyway to get this implementations code?

[@JakobJenkov]

The ExecutorServive is part of standard Java... so if you have Java, you also have the ExecutorService implementation 😊

[@garimadhanania1853]

quick clarification: in the invokeany() call, it could happen that few of the tasks were executing and because of one of them completed and returned the result, the others were aborted? I mean there could be multiple tasks being executed on the different threads right? If only one task is run, it might take a long time to return and that defeats the purpose of using invokeAny() right?

[@JakobJenkov]

Yes, more than one task might get executed, but invokeAny() returns as soon as one task has finished executing. The motivation to use invokeAny() is to push N tasks out to N CPU cores, to get one of the tasks to finish as fast as possible.

[@yumyumtales]

Great Video❤❤❤

[@JakobJenkov]

Thanks !! 😊

[@csabadanyiko6096]

I really like your videos, great explanation for complex topics. I have one question. For invokeAll() you created a List then you cast it to Collection. Why didn't you just define it as Collection in the first place, is there a particular reason?

[@JakobJenkov]

You could probably have created it as a Collection immediately. Sometimes I do stuff in the videos you would not do normally, just to make it more clear what is going on :-)

[@affeine9267]

Why do we have multiple ThreadPools inside the ExecutorService ? We still can specify number of Threads that ThreadPool executes so why do we need more than one ThreadPool ?

[@JakobJenkov]

There can be different kinds of implementations of the ExecutorService interface, meaning different implementations of thread pools that behave differently.

[@RohanSharma-eh4kf]

well i came to this video to understand the inner workings of these interfaces, is there any resources i can follow to understand how things work exactly?

[@JakobJenkov]

I have another video about Thread Pools in Java which explains how to make your own thread pool like the ExecutorService, if you want that, or just want to learn how.

[@karthik8159]

Thank you.

[@JakobJenkov]

You're welcome! :-)

[@AmeySambhare-ki6do]

How did invokeAny return String? Should not it return future object of String?

[@JakobJenkov]

No. invokeAny will return the result of the first of your tasks that finishes. Since the ExecutorService doesn't know which task finishes first, it cannot know which Future object to return to you. Instead, it checks the Future objects internally for results, and as soon as one of the returns a result, that is what is returned.

[@minasalah8210]

thank you

[@JakobJenkov]

You are most welcome :-)

[@luuvanthao3679]

greate

[@JakobJenkov]

Thanks!

[@manojnavinjamuri5867]

please provide the code too