threadpoolexecutor

This question already has an answer here: Executors.newCachedThreadPool() versus Executors.newFixedThreadPool() 8 answers In case newCachedThreadPool() as per creates a thread pool that creates new threads as needed, but will reuse previously constructed threads when they are available whereas in case of newFixedThreadPool(int size) specify size to create the thread pool with size specified. Why isn't newFixedThreadPool(int size) implemented in newCachedThreadPool() fashion where thread pool creates the new thread only when required and will limit the thread to size? Any clarrification on the

My application is reading messages through Jms MessageListener class and at some point of time it is throwing TaskRejectedException . I know most of you will say that the number of threads is exceeded by maxPoolSize and queue is also full. But I observed something. The number of messages sent to the queue from which the MessageListener class is fetching messages is 10353 and my spring property for threadPoolExecutor is below : <bean id="ticketReaderThreadPool" class="org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor" scope="singleton" destroy-method="destroy"> <property name=

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 have a linked blocking queue in which I am performing insertion and removal operations. I need to know which one is better put or offer in case of linked blocking queue. Performance parameters are CPU utilization, memory and overall throughput. Application usage is Real time system where there can be multiple incoming requests and less threads to handle where we will need to insert element in queue. I read Java docs of put and offer there was not much difference in internal application. Batty Actually, you can't compare performance between these two, the offer method is to just offer to the

I am working on a multithreaded application with tasks that have varying run times. When one thread finishes, is there a way for it to take over some tasks from a still running thread? Here is an example. I kick off my program with 5 threads, and each have 50 tasks. When the quickest running thread finishes, another thread still has 40 tasks to complete. How can I get the finished thread to take 20 tasks from the other thread, so each continue working on 20 a piece, rather than waiting for the running thread to complete the remaining 40? Use ForkJoinPool A ForkJoinPool differs from other kinds

Please, help to understand ExecutorService#awaitTermination(timeout) behaviour. I'm observing situation when I have in my code: private void shutdownAndAwaitTermination(ExecutorService threadPool){ threadPool.shutdown(); try { if (!threadPool.awaitTermination(threadPoolTimeout, TimeUnit.HOURS)){ threadPool.shutdownNow(); if (!threadPool.awaitTermination(60, TimeUnit.SECONDS)) { logger.warn("Pool did not terminate"); } } } catch (InterruptedException ie) { threadPool.shutdownNow(); Thread.currentThread().interrupt(); } } Does the tasks in pool complete in this case before any other calls after

I have List of N items and I want to divide this List in a sequential manner between a fixed number of threads . By sequential I mean, I want to pass 1 to N/4 to first thread , N/4 + 1 to N/2 to second thread and N/2+1 to N to third thread , Now once all the threads have finished their work, I want to notify to main thread to send some message that all the processing has been completed. What I have done so far now is that I have implemented ExecutorService I did something like this ExecutorService threadPool = Executors.newFixedThreadPool(Number_of_threads); //List of items List List <items