Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

146
Views
How to stop a Callable thread process after a exception in one thread?

I'm using Callable and ExecutorService to use multi-threading in my application.

In case if any Exceptions are thrown from one thread need to stop all threads even though it's work completed and need to throw that exception to the calling class method. For this, I used a shutDownNow() method.

Is this the right way? or any other effective ways there?

        
ExecutorService exSvc = Executors.newFixedThreadPool(5);
exSvc.setKeepAliveTime(60, TimeUnit.SECONDS);

List<Future<Integer>> futureList = new LinkedList();
for(int i=0; i<50;i++){
    futureList.add(exSvc.submit(
        new Callable<Integer>() {
            public Integer call()  throws Exception{
                int num =  new Random().nextInt(1000);
                if(num==500){
                    throw new Exception("Error");
                }
            return num;
            }
        }));
}

for(int i=0; i<50; i++){
 
   try {
    int value =  futureList.get(i).get();
   } catch (Exception e) {
        exSvc.shutdownNow();
        throw new Exception("Error");
   } 
}


over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

This should work in your example. However, be sure to properly handle thread interruptions in your callables.

Note that the other tasks will be cancelled on a best effort basis and only after you have noticed that one of the tasks have thrown an exception. E.g., if task no. 5 have thrown an exception, you have to wait for the completion of tasks 0-4, and only then you notice that task 5 has failed.

Alternatively, you could subclass the ThreadPoolExecutor like here, to detect the exception as early as possible.

over 4 years ago · Santiago Trujillo Report

0

As ciamei said, if you want to detect the exception as early as possible, maybe you can use a CountDownLatch:

        CountDownLatch cdl = new CountDownLatch(1);
        AtomicInteger successCount = new AtomicInteger();
        AtomicBoolean fail = new AtomicBoolean();
        int taskSize = 50;
        for(int i=0; i<taskSize;i++){
            futureList.add(exSvc.submit(new Callable<Integer>() {
                @Override
                public Integer call() throws Exception {
                    int num =  new Random().nextInt(1000);
                    if(num == 500){
                        fail.set(true);
                        cdl.countDown();
                        throw new Exception("Error");
                    }
                    if (successCount.incrementAndGet() == taskSize) {
                        cdl.countDown();
                    }
                    return num;
                }
            }));
        }
        try {
            cdl.await();
        } catch (InterruptedException e) {
            Thread.currentThread().interrupt();
        }
        if (fail.get()) {
            exSvc.shutdownNow();
            throw new Exception("Error");
        }
        //...
over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!