From the course: Java EE: Concurrency and Multithreading

Unlock the full course today

Join today to access over 24,800 courses taught by industry experts.

ExecutorService shutdown

ExecutorService shutdown

From the course: Java EE: Concurrency and Multithreading

Start my 1-month free trial Buy for my team

ExecutorService shutdown

“

- [Instructor] Now let's take a look at the three remaining APIs, shutdown now, and await termination. Now let's first understand this. When you create the executor service, or check, in your application, it is not going to be destroyed automatically. You have to destroy it yourself. Now, if you do not destroy the object, it is good at times, because your application may have certain jobs coming on an irregular basis. So in that case you may want the service object to be alive so that tasks can be submitted. That's okay. However, if you know that all the tasks in your application are definitely reaching the completion point, then, it is wise, to of course, go ahead and destroy the service object. So, that you can reclaim the resources. So the shutdown mechanism for this service happens via these three APIs. That is shutdown, shutdown now, and await termination. No, let's say you talk about the shutdown method. When you invoke this method, what essentially happens is there is a…

Contents