Executor ExecutorService and Thread pools
suggest changeVersions
[{“Name”:“Java SE 5”,“GroupName”:null},{“Name”:“Java SE 6”,“GroupName”:null},{“Name”:“Java SE 7”,“GroupName”:null},{“Name”:“Java SE 8”,“GroupName”:null}]
Introduction
The Executor interface in Java provides a way of decoupling task submission from the mechanics of how each task will be run, including details of thread use, scheduling, etc. An Executor is normally used instead of explicitly creating threads. With Executors, developers won’t have to significantly rewrite their code to be able to easily tune their program’s task-execution policy.
Remarks
Pitfalls
- When you schedule a task for repeated execution, depending on the ScheduledExecutorService used, your task might be suspended from any further execution, if an execution of your task causes an exception which isn’t handled. See Mother F**k the ScheduledExecutorService!
Found a mistake? Have a question or improvement idea?
Let me know.
Table Of Contents