How to make ThreadPoolExecutor’s submit() method block if it is saturated?

by

One of the possible solutions I’ve just found:

public class BoundedExecutor {
    private final Executor exec;
    private final Semaphore semaphore;

    public BoundedExecutor(Executor exec, int bound) {
        this.exec = exec;
        this.semaphore = new Semaphore(bound);
    }

    public void submitTask(final Runnable command)
            throws InterruptedException, RejectedExecutionException {
        semaphore.acquire();
        try {
            exec.execute(new Runnable() {
                public void run() {
                    try {
                        command.run();
                    } finally {
                        semaphore.release();
                    }
                }
            });
        } catch (RejectedExecutionException e) {
            semaphore.release();
            throw e;
        }
    }
}

Are there any other solutions? I’d prefer something based on RejectedExecutionHandler since it seems like a standard way to handle such situations.

More Related Contents:

  1. Java Executors: how can I set task priority?
  2. ThreadPoolExecutor Block When Queue Is Full?
  3. When should we use Java’s Thread over Executor?
  4. ThreadPoolExecutor Block When its Queue Is Full?
  5. What is optimum thread pool size for simple program running cpu based tasks in Java
  6. Why must wait() always be in synchronized block
  7. How to share data with two(2) SwingWorker class in Java
  8. ConcurrentModificationException despite using synchronized
  9. Volatile vs Static in Java
  10. How do I simulate a buffered peripheral device with SwingWorker?
  11. Java swing GUI freezes
  12. How do I call some blocking method with a timeout in Java?
  13. Volatile variable in Java
  14. What is the JVM thread scheduling algorithm?
  15. What is the difference between synchronized on lockObject and using this as the lock?
  16. Why does Thread.isInterrupted () always return false?
  17. What is an “incompletely constructed object”?
  18. How does `this` reference to an outer class escape through publishing inner class instance?
  19. Java memory model – can someone explain it?
  20. Are non-synchronised static methods thread safe if they don’t modify static class variables?
  21. When do I need to use AtomicBoolean in Java?
  22. Java concurrency: Countdown latch vs Cyclic barrier
  23. How to interrupt a BlockingQueue which is blocking on take()?
  24. Any good Spring threading with a TaskExecutor examples? [closed]
  25. Hashmap concurrency issue
  26. Which concurrent Queue implementation should I use in Java?
  27. Why should I use concurrent characteristic in parallel stream with collect?
  28. Java concurrency: is final field (initialized in constructor) thread-safe?
  29. Jboss Java EE container and an ExecutorService
  30. Java: is there no AtomicFloat or AtomicDouble?

Leave a Comment