How Threadpool re-use Threads and how it works

by

If there is no need to create new Thread in ThreadPool scenario, then how it works with same thread which just finished its run method, will that Thread can be used again?

Simple – the original thread never actually completes. It just waits for another task to execute. In pseudo-code:

// No, this isn't even slightly accurate! General impression only :)
while (!pool.isShutdown()) {
    Runnable task = pool.waitForTaskOnQueue();
    task.run();
}

(Obviously when a thread pool is shut down, it would need to stop waiting threads from waiting for another task, too – but hopefully you get the general idea.)

More Related Contents:

  1. How to wait for all threads to finish, using ExecutorService?
  2. Is there an advantage to use a Synchronized Method instead of a Synchronized Block?
  3. Why is creating a Thread said to be expensive?
  4. When and how should I use a ThreadLocal variable?
  5. What is the difference between Thread.start() and Thread.run()?
  6. Java Wait and Notify: IllegalMonitorStateException
  7. Are static variables shared between threads?
  8. How do synchronized static methods work in Java and can I use it for loading Hibernate entities?
  9. Is iterating ConcurrentHashMap values thread safe?
  10. Why use a ReentrantLock if one can use synchronized(this)?
  11. Is it safe to get values from a java.util.HashMap from multiple threads (no modification)?
  12. How do I implement task prioritization using an ExecutorService in Java 5?
  13. Threads configuration based on no. of CPU-cores
  14. Constructor synchronization in Java
  15. More efficient way for pausing loop wanted
  16. Javafx: Difference between javafx.concurent and Platform.runLater?
  17. How are Threads allocated to handle Servlet request?
  18. Instruction reordering & happens-before relationship [duplicate]
  19. When should we use Java’s Thread over Executor?
  20. Why should I use concurrent characteristic in parallel stream with collect?
  21. ThreadPoolExecutor Block When its Queue Is Full?
  22. Java: ExecutorService that blocks on submission after a certain queue size [duplicate]
  23. Why doesn’t volatile in java 5+ ensure visibility from another thread?
  24. Concurrent JUnit testing
  25. Handling Exceptions for ThreadPoolExecutor
  26. Dynamic Thread Pool
  27. JAVAFX : why wait cursor needs a new thread?
  28. notifyAll() throws IllegalMonitorStateException
  29. Will a chain of method calls (CompletableFuture API) execute asynchronously if the first method in a chain is asynchronous?
  30. ExecutorCompletionService? Why do need one if we have invokeAll?

Leave a Comment