executorservice

Sorry I have to open a new thread to describe this problem. This morning I asked this question , there're some replies but my problem is still not solved. This time I will attach some runnable code(simplified but with the same problem) for you to reproduce the problem: public class ThreadPoolTest { public static void main(String[] args) throws Exception { final ExecutorService taskExecutor = Executors.newFixedThreadPool(5); Future<Void> futures[] = new Future[5]; for (int i = 0; i < futures.length; ++i) futures[i] = startTask(taskExecutor); for (int i = 0; i < futures.length; ++i) System.out

I have a for loop which I am trying to parallelize using CompletableFuture. for (int i = 0; i < 10000; i++) { doSomething(); doSomethingElse(); } What I have till now is: for (int i = 0; i < 10000; i++) { CompletableFuture.runAsync(() -> doSomething()); CompletableFuture.runAsync(() -> doSomethingElse()); } I guess this serves the purpose but there is a requirement to print log just before the start and end of all the processing. If I do this: log("Started doing things"); for (int i = 0; i < 10000; i++) { CompletableFuture.runAsync(() -> doSomething()); CompletableFuture.runAsync(() ->

I have a long running task that is executing in the background on an ExecutorService thread pool. What are some best practices in terms of this task returning progress or intermediate results? Are there any libraries that provide this functionality? EDIT: To clarify, I'm talking about reporting progress to other code, not to the user. Normally I would use SwingWorker, but I'm working with a Java/Groovy backend for a Grails app, and I'm unsure how that would behave in a headless server environment since it has EDT ties. Another example is the Jobs framework in Eclipse RCP, but I would need

I have created threadpool using ExecutorService , in my application to call vendor websrvice, using below code. ExecutorService executor = Executors.newFixedThreadPool(getThreadPoolSize()); for (int i = 0; i < list.size(); i++) { Request ecpReq = list.get(i); thRespLst.add(executor.submit(new Task(ecpReq))); } Wanted to know do we need to take care of shutting down threadpool or something, basically I don't want hanging threads in production environment. Fabio Cardoso newFixedThreadPool public static ExecutorService newFixedThreadPool(int nThreads) Creates a thread pool that reuses a fixed

I'm slightly confused by the internal scheduling mechanism of the ExecutorService and the ForkJoinPool. I understood the ExecutorService scheduling is done this way . A bunch of tasks are queued. Once a thread is available it will handle the first available task and so forth. Meanwhile, a ForkJoinPool is presented as distinct because it uses a work-stealing algorithm. If I understand correctly it means a thread can steal some tasks from another thread. Yet, I don't really understand the difference with the mechanism implemented in the ExecutorService. From my understanding, both mechanisms

In a typical JAVA application, one configures a global ExecutorService for managing a global thread pool. Lets say I configure a fixed thread pool of 100 threads: ExecutorService threadPool = Executors.newFixedThreadPool(100); Now lets say that I have a list of 1000 files to upload to a server, and for each upload I create a callable that will handle the upload of this one file. List<Callable> uploadTasks = new ArrayList<Callable>(); // Fill the list with 1000 upload tasks How can I limit the max number of concurrent uploads to, lets say, 5? if I do threadPool.invokeAll(uploadTasks); I dont

I need to make a library in which I will have synchronous and asynchronous methods in it. executeSynchronous() - waits until I have a result, returns the result. executeAsynchronous() - returns a Future immediately which can be processed after other things are done, if needed. Core Logic of my Library The customer will use our library and they will call it by passing DataKey builder object. We will then construct a URL by using that DataKey object and make a HTTP client call to that URL by executing it and after we get the response back as a JSON String, we will send that JSON String back to

I want to use the same thread pool throughout my application. To this end, I can make ExecutorService static and global so that I can invoke ThreadUtil.executorService to get ExecutorService when I need it. public class ThreadUtil { public static final ExecutorService executorService = Executors.newCachedThreadPool(); } Is it OK to instance multiple thread pools like this? In addition, my application is a TCP server. If I don't know how big the pool should be, is it ok to simply use newCachedThreadPool ? When an instance with the same properties is to be used anywhere in your program, it is