ExecutorService - thread pool

I am using a thread pool to handle requests. Is there a way to know who is doing what?
This is the code I used to assign new tasks to my pool:
for (;;) {
this.pool.execute(new Handler(this.sSocket.accept(),Identifier);
Is there a way to get the thread that will execute it?

You don't explain the context in which this application is launched - applications can be restricted by security policies too.
shutdown requires two permissions: one from the installed SecurityManager if any, and the other directly from the AccessController. Your installed SecurityManager may be saying "yes" while the AccessController says "no". There is a change in Java 6 such that only the security manager is queried.

Similar Messages

ExecutorService thread pool shutdown exception

Hello,
We are developing a desktop application (no applets etc) on the Netbeans plaform. I am trying to add a thread pool via the Java5 ExecutorService. I think we have a very standard implementation using static methods - we copied it from some basic examples in blogs. Please see the class below.
Everything seems OK until I try to run shutdown. During the application shutdown we catch an exception that says
access denied (java.lang.RuntimePermission modifyThread)The exception is raised when running the ExecutorService "shutdown()" method.
Please note that this is a desktop application, and we DO check the permission with the SecurityManager (see code) and we do seem to have the correct permission (no exception raised during check).
Firstly, this is the first time we've used ExecutorService, so maybe we just have just implemented it incorrectly. Secondly, all "googling" on the issue reveals very little. It only seems to happen to applets.
ANY SUGGESTIONS, ADVICE, GUIDANCE, HINTS would be MUCH appreciated.
public final class ThreadPool {
    private static ExecutorService threadPool = Executors.newFixedThreadPool(3);
    public static void execute(Runnable worker) {
        threadPool.submit(worker);
    public static void shutdown() {
        SecurityManager s = System.getSecurityManager ();
        if (s!=null) {
            try {
                s.checkPermission(new RuntimePermission("modifyThread"));
                // we apparently have permission, so proceed to shutdown ...
                threadPool.shutdown(); // EXCEPTION RAISED HERE !!!!!
                threadPool.awaitTermination(15L, TimeUnit.SECONDS);
                threadPool.shutdownNow(); // brutal mop up
            } catch (Exception e) {
                logger.warn("ThreadPool.shutdown(): ex=" + e.getMessage());
}

You don't explain the context in which this application is launched - applications can be restricted by security policies too.
shutdown requires two permissions: one from the installed SecurityManager if any, and the other directly from the AccessController. Your installed SecurityManager may be saying "yes" while the AccessController says "no". There is a change in Java 6 such that only the security manager is queried.

A good design for a single thread pool manager using java.util.concurrent

Hi,
I am developing a client side project which in distinct subparts will execute some tasks in parallel.
So, just to be logorroic, something like that:
program\
            \--flow A\
                       \task A1
                       \task A2
            \--flow B\
                        \task B1
                        \task B2
                        \...I would like both flow A and flow B (and all their launched sub tasks) to be executed by the same thread pool, because I want to set a fixed amount of threads that my program can globally run.
My idea would be something like:
public class ThreadPoolManager {
    private static ExecutorService executor;
    private static final Object classLock = ThreadPoolManager.class;
     * Returns the single instance of the ExecutorService by means of
     * lazy-initialization
     * @return the single instance of ThreadPoolManager
    public static ExecutorService getExecutorService() {
        synchronized (classLock) {
            if (executor != null) {
                return executor;
            } else {
                // TODO: put the dimension of the FixedThreadPool in a property
                executor = Executors.newFixedThreadPool(50);
            return executor;
     * Private constructor: deny creating a new object
    private ThreadPoolManager() {
}The tasks I have to execute will be of type Callable, since I expect some results, so you see an ExecutorService interface above.
The flaws with this design is that I don't prevent the use (for example) of executor.shutdownNow(), which would cause problems.
The alternative solution I have in mind would be something like having ThreadPoolManager to be a Singleton which implements ExecutorService, implementing all the methods with Delegation to an ExecutorService object created when the ThreadPoolManager object is instantiated for the first time and returned to client:
public class ThreadPoolManager implements ExecutorService {
    private static ThreadPoolManager pool;
    private static final Object classLock = ThreadPoolManager.class;
    private ExecutorService executor;
     * Returns the single instance of the ThreadPoolManager by means of
     * lazy-initialization
     * @return the single instance of ThreadPoolManager
    public static ExecutorService getThreadPoolManager() {
        synchronized (classLock) {
            if (pool !=null) {
                return pool;
            } else {
                // create the real thread pool
                // TODO: put the dimension of the FixedThreadPool in a property
                // file
                pool = new ThreadPoolManager();
                pool.executor = Executors.newFixedThreadPool(50);
                // executor = Executors.newCachedThreadPool();
                return pool;
     * Private constructor: deny creating a new object
    private ThreadPoolManager() {
    /* ======================================== */
    /* implement ExecutorService interface methods via delegation to executor
     * (forbidden method calls, like shutdownNow() , will be "ignored")
      // .....I hope to have expressed all the things, and hope to receive an answer that clarifies my doubts or gives me an hint for an alternative solution or an already made solution.
ciao
Alessio

Two things. Firstly, it's better to use     private static final Object classLock = new Object();because that saves you worrying about whether any other code synchronises on it. Secondly, if you do decide to go for the delegation route then java.lang.reflect.Proxy may be a good way forward.

Thread Pool , Executors ...

Sorry if i make a stupid post now, but i'm looking for a implementation of a Thread Pool using the latest 1.5 java.util.concurrent classes and i can't find anything serious. Any implementation or link to a tutorial should be vary helpful.
Thnx

but i'm looking
for a implementation of a Thread Pool using
the latest 1.5 java.util.concurrent classes and i
can't find anything serious. Any implementation or
link to a tutorial should be vary helpful.
Thnxhere is an Example :
import java.util.concurrent.*;
public class UtilConcurrentTest {
public static void main(String[] args) throws InterruptedException {
int numThreads = 4;
int numTasks = 20;
ExecutorService service = Executors.newFixedThreadPool(numThreads);
// do some tasks:
for (int i = 0; i < numTasks; i++) {
service.execute(new Task(i));
service.shutdown();
log("called shutdown()");
boolean isTerminated = service.awaitTermination(60, TimeUnit.SECONDS);
log("service terminated: " + isTerminated);
public static void log(String msg) {
System.out.println(System.currentTimeMillis() + "\t" + msg);
private static class Task implements Runnable {
private final int id;
public Task(int id) {
this.id = id;
public void run() {
log("begin:\t" + this);
try { Thread.sleep(1000); } catch (InterruptedException e) {}
log("end\t" + this);
public String toString() {
return "Task " + id + " in thread " + Thread.currentThread().getName();
}

Thread pool executor problem

When using a thread pool executor (java.util.concurrent.ThreadPoolExecutor) to limit the number of threads executing at a time, the number of threads running still exceeds the limit number.
This is the code:
private ThreadPoolExecutor threadPoolExecutor = new ThreadPoolExecutor(2, 3, 20, TimeUnit.SECONDS, new LinkedBlockingQueue());
The number of tasks in my program are 4, so i always have 4 threads running, although i limited it to 3.
Can anyone help me with this problem? Or can u propose another solution to limit the number of running threads? By the way, i also tried using a newFixedThreadPool() and got the same problem.
Thx.

The number of tasks in my program are 4, so i always
have 4 threads running, although i limited it to 3.How do you know that there are 4 threads running? If you're generating a JVM thread dump, you're going to see threads that are used internally by the JVM.
Here's a simple program that creates a fixed-size threadpool and runs jobs. It limits the number of concurrent threads to 3. Compare it to what you're doing, I'm sure that you'll find something different. Also, verify that you're not creating threads somewhere else in your program; all of the ThreadPoolExecutor threads will have names of the form "pool-X-thread-Y"
import java.util.concurrent.Executors;
import java.util.concurrent.ExecutorService;
public class ThreadPoolTest {
    public static void main(String[] args) {
        ExecutorService pool = Executors.newFixedThreadPool(3);
        for (int ii = 0 ; ii < 10 ; ii++) {
            pool.execute(new MyRunnable());
        pool.shutdown();
    private static class MyRunnable implements Runnable {
        public void run() {
            log("running");
            try {
                Thread.sleep(1000L);
            catch (InterruptedException e) {
                log("interrupted");
        private void log(String msg) {
            System.err.println(
                    msg + " on " + Thread.currentThread().getName()
                    + " at " + System.currentTimeMillis());
}

Thread Pool Callback Mechanism

I am using java.util.concurrent.ExecutorService to create a thread pool. I need a way to inform the user of the progress of the threads in the pool.
Does anyone have any ideas of how to do this?

I am using java.util.concurrent.ExecutorService to
create a thread pool. I need a way to inform the user
of the progress of the threads in the pool.
Does anyone have any ideas of how to do this?Hand the Executor instances of SwingWorker, which implements RunnableFuture. SwingWorker also has a progress() method which can provide progress information.

Fixed Size Thread Pool which infinitely serve task submitted to it

Hi,
I want to create a fixed size thread pool say of size 100 and i will submit around 200 task to it.
Now i want it to serve them infinitely i.e once all tasks are completed re-do them again and again.
public void start(Vector<String> addresses)
      //Create a Runnable object of each address in "addresses"
       Vector<FindAgentRunnable> runnables = new Vector<FindAgentRunnable>(1,1);
        for (String address : addresses)
            runnables.addElement(new FindAgentRunnable(address));
       //Create a thread pool of size 100
        ExecutorService pool = Executors.newFixedThreadPool(100);
        //Here i added all the runnables to the thread pool
         for(FindAgentRunnable runnable : runnables)
                pool.submit(runnable);
            pool.shutdown();
}Now i wants that this thread pool execute the task infinitely i.e once all the tasks are done then restart all the tasks again.
I have also tried to add then again and again but it throws a java.util.concurrent.RejectedExecutionException
public void start(Vector<String> addresses)
      //Create a Runnable object of each address in "addresses"
       Vector<FindAgentRunnable> runnables = new Vector<FindAgentRunnable>(1,1);
        for (String address : addresses)
            runnables.addElement(new FindAgentRunnable(address));
       //Create a thread pool of size 100
        ExecutorService pool = Executors.newFixedThreadPool(100);
        for(;;)
            for(FindAgentRunnable runnable : runnables)
                pool.submit(runnable);
            pool.shutdown();
            try
                pool.awaitTermination(Long.MAX_VALUE, TimeUnit.SECONDS);
            catch (InterruptedException ex)
                Logger.getLogger(AgentFinder.class.getName()).log(Level.SEVERE, null, ex);
}Can anybody help me to solve this problem?
Thnx in advance.

Ravi_Gupta wrote:
*@ kajbj*
so what should i do?
can you suggest me a solution?Consider this thread "closed". Continue to post in your other thread. I, and all others don't want to give answers that already have been given.

Thread pool with AT MOST one thread at a time

Hi,
I want to create a pool that creates at most one thread when it is needed. I want the pool to terminate the thread when it is idle for some time. Executors.newSingleThreadExecutor() creates a thread pool with one thread, but this thread doesn't die if idle...
The code below also doesn't work - no thread is ever created:
new ThreadPoolExecutor(0, 1, 30, TimeUnit.SECONDS,
                          new LinkedBlockingQueue<Runnable>());Thanks in advance

Use Future.get().
package net.jcip.examples;
import java.util.concurrent.*;
import static java.util.concurrent.TimeUnit.NANOSECONDS;
* RenderWithTimeBudget
* Fetching an advertisement with a time budget
* @author Brian Goetz and Tim Peierls
public class RenderWithTimeBudget {
    private static final Ad DEFAULT_AD = new Ad();
    private static final long TIME_BUDGET = 1000;
    private static final ExecutorService exec = Executors.newCachedThreadPool();
    Page renderPageWithAd() throws InterruptedException {
        long endNanos = System.nanoTime() + TIME_BUDGET;
        Future<Ad> f = exec.submit(new FetchAdTask());
        // Render the page while waiting for the ad
        Page page = renderPageBody();
        Ad ad;
        try {
            // Only wait for the remaining time budget
            long timeLeft = endNanos - System.nanoTime();
            ad = f.get(timeLeft, NANOSECONDS);
        } catch (ExecutionException e) {
            ad = DEFAULT_AD;
        } catch (TimeoutException e) {
            ad = DEFAULT_AD;
            f.cancel(true);
        page.setAd(ad);
        return page;
    Page renderPageBody() { return new Page(); }
    static class Ad {
    static class Page {
        public void setAd(Ad ad) { }
    static class FetchAdTask implements Callable<Ad> {
        public Ad call() {
            return new Ad();
}

Thread Pool "Null Pointer" exception

Hello,
I have an embarrassingly parallel algorithm. The parallel part is solved by 2 objects called shifters which implement the Runnable interface. However, for reasons I can't figure out, sometimes my code will randomly output this error.
Exception in thread "pool-1-thread-1" java.lang.NullPointerException
at cvtpmshiftlabnormalized.Shifter.run(Shifter.java:63)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Exception in thread "pool-1-thread-2" java.lang.NullPointerException
at cvtpmshiftlabnormalized.Shifter.run(Shifter.java:63)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
My code concerning the parallelization is as follows:
        shifter_1 = new Shifter(list_1 , clusterTree);
        shifter_2 = new Shifter(list_2 , clusterTree);
        ExecutorService executor = Executors.newFixedThreadPool(5);
        executor.execute(shifter_1);
        executor.execute(shifter_2);
        executor.shutdown();Any help would be greatly appreciated, seeing how my computer throws this error for the same data set whenever it feels like it.
Sincerely,
Chem E

Here is the run() method of the shifter. It's pretty big, but I don't know what you would want to look at , and what is garbage.. Thanks for helping me.
public void run()
        ArrayList<Cluster> neighbors = new ArrayList();
        ArrayList<Cluster> removeUs = new ArrayList();
        double resultantVector[] = new double[3];
        double dotProduct;
        double gaussian;
        double gaussianWeight;
        while(workingClusters.size() > 0)
            workingClusters.removeAll(removeUs);
            removeUs.clear();
            System.out.println("Working Clusters: " + workingClusters.size());
            for(Cluster cluster : workingClusters)
                neighbors.clear();
                neighbors = clusterTree.returnNeighbors(cluster.values, returnRange);
                clusterTree.remove(cluster);
                resultantVector[0] = 0;
                resultantVector[1] = 0;
                resultantVector[2] = 0;
                gaussianWeight = 0;
                for(Cluster nCluster : neighbors)
                     dotProduct = dotProduct( cluster.values, nCluster.values);
                     gaussian = Math.exp(-dotProduct / Math.pow(returnRange , 2));
                     resultantVector[0] += gaussian * nCluster.values[0] * nCluster.weight;
                     resultantVector[1] += gaussian * nCluster.values[1] * nCluster.weight;
                     resultantVector[2] += gaussian * nCluster.values[2] * nCluster.weight;
                     gaussianWeight += gaussian * nCluster.weight;
                if(neighbors.size() > 0)
                    resultantVector[0] /= gaussianWeight;
                    resultantVector[1] /= gaussianWeight;
                    resultantVector[2] /= gaussianWeight;
                    if(dotProduct(resultantVector , cluster.values) < 0.01)
                        removeUs.add(cluster);
                    cluster.values[0] = resultantVector[0];
                    cluster.values[1] = resultantVector[1];
                    cluster.values[2] = resultantVector[2];
                clusterTree.put(cluster);
    }

Submit submit a large number of task to a thread pool (more than 10,000)

i want to submit a large number of task to a thread pool (more than 10,000).
Since a thread pool take runnable as input i have to create as many objects of Runnable as the number of task, but since the number of task is very large it causes the memory overflow and my application crashes.
Can you suggest me some way to overcome this problem?

Ravi_Gupta wrote:
I have to serve them infinitely depending upon the choice of the user.
Take a look at my code (code of MyCustomRunnable is already posted)
public void start(Vector<String> addresses)
searching = true;What is this for? Is it a kind of comment?
>
Vector<MyCustomRunnable> runnables = new Vector<MyCustomRunnable>(1,1);
for (String address : addresses)
try
runnables.addElement(new MyCustomRunnable(address));
catch (IOException ex)
ex.printStackTrace();
}Why does MyCustomRunnable throw an IOException? Why is using up resources when it hasn't started. Why build this vector at all?
>
//ThreadPoolExecutor pool = new ThreadPoolExecutor(100,100,50000L,TimeUnit.MILLISECONDS,new LinkedBlockingQueue());
ExecutorService pool = Executors.newFixedThreadPool(100);You have 100 CPUs wow! I can only assume your operations are blocking on a Socket connection most of the time.
>
boolean interrupted = false;
Vector<Future<String>> futures = new Vector<Future<String>>(1,1);You don't save much by reusing your vector here.
for(int i=1; !interrupted; i++)You are looping here until the thread is interrupted, why are you doing this? Are you trying to generate loading on a remote server?
System.out.println("Cycle: " + i);
for(MyCustomRunnable runnable : runnables)Change the name of you Runnable as it clearly does much more than that. Typically a Runnable is executed once and does not create resources in its constructor nor have a cleanup method.
futures.addElement((Future<String>) pool.submit(runnable));Again, it unclear why you would use a vector rather than a list here.
>
for(Future<String> future : futures)
try
future.get();
catch (InterruptedException ex)
interrupted = true;If you want this to break the loop put the try/catch outside the loop.
ex.printStackTrace();
catch (ExecutionException ex)
ex.printStackTrace();If you are generating a load test you may want to record this kind of failure. e.g. count them.
futures.clear();
try
Thread.sleep(60000);Why do you sleep even if you have been interrupted? For better timing, you should sleep, before check if you futures have finished.
catch(InterruptedException e)
searching = false;again does nothing.
System.out.println("Thread pool terminated..................");
//return;remove this comment. its dangerous.
break;why do you have two way of breaking the loop. why not interrupted = true here.
searching = false;
System.out.println("Shut downing pool");
pool.shutdownNow();
try
for(MyCustomRunnable runnable : runnables)
runnable.close(); //release resources associated with it.
catch(IOException e)put the try/catch inside the loop. You may want to ignore the exception but if one fails, the rest of the resources won't get cleaned up.
The above code serve the task infinitely untill it is terminated by user.
i had created a large number of runnables and future objects and they remain in memory until
user terminates the operation might be the cause of the memory overflow.It could be the size of the resources each runnable holds. Have you tried increasing your maximum memory? e.g. -Xmx512m

Scheduled thread pools and blocking

Hello,
I am using a scheduled thread pool created in the following way:
ScheduledExecutorService scheduler = Executors.newScheduledThreadPool();I want to schedule a task on the scheduler, but this task uses a MulticastSocket and can block on:
byte[] b = new byte[BUFFER_LENGTH];
DatagramPacket dgram = new DatagramPacket(b, b.length);
socket.receive(dgram);Say I schedule this code to run at 500 ms. The first run blocks on the receive method. If the block lasts for more that 500ms, what happens when the scheduler allocates another thread at the next 500ms mark? Can I "lose" a thread from the pool permanently? Can I cause a backup of multiple threads blocking every time the scheduler runs the task?
Thanks!
-pm

Well it used to be a plain old Runnable with the receive() inside the run() method, and the runnable was launched inside a Thread. However, I have an infrastructure that adds tasks to a ScheduledExecutorService so that I can run tasks that require a timing mechanism. I also have an ExecutorService for executing tasks at one time. I want to use these concurrency facilities to get this task to always run, not just once, and I thought scheduling would allow that. Would the ExecutorService's submit() method do that? Would it make more sense to have the run() method loop:
run(){
byte[] b = new byte[BUFFER_LENGTH];
DatagramPacket dgram = new DatagramPacket(b, b.length);
while(true){
socket.receive(dgram);
// do something ...
}and then have ExecutorService simply run execute()?
Thanks!

Creating Thread Pool with Executors.newFixedThreadPool(poolSize)

I am creating a server socket and want a Thread pool to limit the number of threads created for serving each clients. I have written a code:
private ExecutorService threadPool;
//Creating a Thread Pool for handling new sessions
threadPool=ThreadPool.createSessionThreadPool(poolSize);
and in my main listen logic:
serverSocket = new ServerSocket(listenPort);
clientSocket = serverSocket.accept();
                    threadPool.execute(new Runnable(){
                         public void run(){
                              handleConnection();
and in handleConnection I am trying to read the inputstream in a while loop:
public void handleConnection(){
BufferedReader in=null;
in = new BufferedReader(new InputStreamReader(clientSocket.getInputStream()));
while (true) {
if((fullCommandString = in.readLine()) ==null){
wait(); // I assume that this wait will block the thread and keep the thread back in to the pool.
                    System.out.println(Thread.currentThread().getName() + " received the message");
                    System.out.println("echo: " + fullCommandString);
                    out.println("230 reply back \r\n");
why don't it keep the thread back in the pool when I call the wait() ? Is it since the thread is still active in reading the input stream? If so can any one hepl me with a snippet which will keep the thread back in the pool when there is noting on the input stream to read.

Hi,
The call to wait does not return the thread pool back to the pool. The thread will be associated with your runnable as long as your run method hasn't returned.
It looks like you instead want to use NIO if you want to use a few threads to handle many clients.
Kaj

How can I use the same thread pool implementation for different tasks?

Dear java programmers,
I have written a class which submits Callable tasks to a thread pool while illustrating the progress of the overall procedure in a JFrame with a progress bar and text area. I want to use this class for several applications in which the process and consequently the Callable object varies. I simplified my code and looks like this:
        threadPoolSize = 4;
        String[] chainArray = predock.PrepareDockEnvironment();
        int chainArrayLength = chainArray.length;
        String score = "null";
        ExecutorService executor = Executors.newFixedThreadPool(threadPoolSize);
        CompletionService<String> referee = new ExecutorCompletionService<String>(executor);
        for (int i = 0; i < threadPoolSize - 1; i++) {
            System.out.println("Submiting new thread for chain " + chainArray);
referee.submit(new Parser(chainArray[i]));
for (int chainIndex = threadPoolSize; chainIndex < chainArrayLength; chainIndex++) {
try {
System.out.println("Submiting new thread for chain " + chainArray[chainIndex]);
referee.submit(new Parser(chainArray[i]));
score = referee.poll(10, TimeUnit.MINUTES).get();
System.out.println("The next score is " + score);
executor.shutdown();
int index = chainArrayLength - threadPoolSize;
score = "null";
while (!executor.isTerminated()) {
score = referee.poll(10, TimeUnit.MINUTES).get();
System.out.println("The next score is " + score);
index++;
My question is how can I replace Parser object with something changeable, so that I can set it accordingly whenever I call this method to conduct a different task?
thanks,
Tom

OK lets's start from the beginning with more details. I have that class called ProgressGUI which opens a small window with 2 buttons ("start" and "stop"), a progress bar and a text area. It also implements a thread pool to conducts the analysis of multiple files.
My main GUI, which is much bigger that the latter, is in a class named GUI. There are 3 types of operations which implement the thread pool, each one encapsulated in a different class (SMAP, Dock, EP). The user can set the necessary parameters and when clicking on a button, opens the ProgressGUI window which depicts the progress of the respective operation at each time step.
The code I posted is taken from ProgressGui.class and at the moment, in order to conduct one of the supported operations, I replace "new Parser(chainArray)" with either "new SMAP(chainArray[i])", "new Dock(chainArray[i])", "new EP(chainArray[i])". It would be redundant to have exactly the same thread pool implementation (shown in my first post) written 3 different times, when the only thing that needs to be changed is "new Parser(chainArray[i])".
What I though at first was defining an abstract method named MainOperation and replace "new Parser(chainArray[i])" with:
new Callable() {
public void call() {
    MainOperation();
});For instance when one wants to use SMAP.class, he would initialize MainOperation as:
public abstract String MainOperation(){
    return new SMAP(chainArray));
That's the most reasonable explanation I can give, but apparently an abstract method cannot be called anywhere else in the abstract class (ProgressGUI.class in my case).
Firstly it should be Callable not Runnable.Can you explain why? You are just running a method and ignoring any result or exception. However, it makes little difference.ExecutorCompletionService takes Future objects as input, that's why it should be Callable and not Runnable. The returned value is a score (String).
Secondly how can I change that runMyNewMethod() on demand, can I do it by defining it as abstract?How do you want to determine which method to run?The user will click on the appropriate button and the GUI will initialize (perhaps implicitly) the body of the abstract method MainOperation accordingly. Don't worry about that, this is not the point.
Edited by: tevang2 on Dec 28, 2008 7:18 AM

JRun Thread Pool Issue

I'm running CF 9.0.1 on Ubuntu on an "Medium" Amazon EC2 instance. CF has been crashing intermittently (several times per day). At such times, running top gets me this (or something similar):
PID
USER
PR
NI
VIRT
RES
SHR
S
%CPU
%MEM
TIME+COMMAND
15855
wwwrun
20
0
1762m
730m
20m
S
99.3
19.4
13:22.96 coldfusion9
So, it's obviously consuming most of the server resources. The following error has been showing up in my cfserver.log in the leadup to each crash:
java.lang.RuntimeException: Request timed out waiting for an available thread to run. You may want to consider increasing the number of active threads in the thread pool.
If I run /opt/coldfusion9/bin/coldfusion status, I get:
Pg/Sec DB/Sec CP/Sec Reqs Reqs Reqs AvgQ   AvgReq AvgDB Bytes Bytes
Now Hi Now Hi Now Hi Q'ed Run'g TO'ed Time   Time   Time   In/Sec Out/Sec
0   0   0   0   -1 -1 150   25    0     0      -1352560      0      0
In the administrator, under Server Settings > Request Tuning, the setting for Maximum number of simultaneous Template requests is 25. So this makes sense so far. I could just increase the thread pool to cover these sort of load spikes. I could make it 200. (Which I did just now as a test.)
However, there's also this file /opt/coldfusion9/runtime/servers/coldfusion/SERVER-INF/jrun.xml. And some of the settings in there appear to conflict. For example, it reads:
<service class="jrunx.scheduler.SchedulerService" name="SchedulerService">
<attribute name="bindToJNDI">true</attribute>
<attribute name="activeHandlerThreads">25</attribute>
<attribute name="maxHandlerThreads">1000</attribute>
<attribute name="minHandlerThreads">20</attribute>
<attribute name="threadWaitTimeout">180</attribute>
<attribute name="timeout">600</attribute>
</service>
Which a) has fewer active threads (what does this mean?), and b) has a max threads that exceed the simultaneous request limit set in the admin. So, I'm not sure. Are these independent configs that need to be made to match manually? Or is the jrun.xml file supposed to be written by the CF Admin when changes are made there? Hmm. But maybe this is different because presumably the CF Scheduler should only use a subset of all available threads, right...so we'd always have some threads for real live users. We also have this in there:
<service class="jrun.servlet.http.WebService" name="WebService">
<attribute name="port">8500</attribute>
<attribute name="interface">*</attribute>
<attribute name="deactivated">true</attribute>
<attribute name="activeHandlerThreads">200</attribute>
<attribute name="minHandlerThreads">1</attribute>
<attribute name="maxHandlerThreads">1000</attribute>
<attribute name="mapCheck">0</attribute>
<attribute name="threadWaitTimeout">300</attribute>
<attribute name="backlog">500</attribute>
<attribute name="timeout">300</attribute>
</service>
This appears to have changed when I changed the CF Admin setting...maybe...but it's the activeHandlerThreads that matches my new maximum simulataneous requests setting...rather than the maxHandlerThreads, which again exceeds it. Finally, we have this:
<service class="jrun.servlet.jrpp.JRunProxyService" name="ProxyService">
<attribute name="activeHandlerThreads">200</attribute>
<attribute name="minHandlerThreads">1</attribute>
<attribute name="maxHandlerThreads">1000</attribute>
<attribute name="mapCheck">0</attribute>
<attribute name="threadWaitTimeout">300</attribute>
<attribute name="backlog">500</attribute>
<attribute name="deactivated">false</attribute>
<attribute name="interface">*</attribute>
<attribute name="port">51800</attribute>
<attribute name="timeout">300</attribute>
<attribute name="cacheRealPath">true</attribute>
</service>
So, I'm not certain which (if any) of these I should change and what exactly the relationship is between maximum requests and maximum threads. Also, since several of these list the maxHandlerThreads as 1000, I'm wondering if I should just set the maximum simultaneous requests to 1000. There must be some upper limit that depends on available server resources...but I'm not sure what it is and I don't really want to play around with it since it's a production environment.
I'm not sure if it pertains to this issue at all, but when I run a ps aux | grep coldfusion I get the following:
wwwrun   15853 0.0 0.0   8704   760 pts/1
S
20:22   0:00 /opt/coldfusion9/runtime/bin/coldfusion9 -jar jrun.jar -autorestart -start coldfusion
wwwrun   15855 5.4 18.2 1678552 701932 pts/1
Sl
20:22   1:38 /opt/coldfusion9/runtime/bin/coldfusion9 -jar jrun.jar -start coldfusion
There are always these two and never more than these two processes. So there does not appear to be a one-to-one relationship between processes and threads. I recall from an MX 6.1 install I maintained for many years that additional CF processes were visible in the process list. It seemed to me at the time like I had a process for each thread...so either I was wrong or something is quite different in version 9 since it's reporting 25 running requests and only showing these two processes. If a single process can have multiple threads in the background, then I'm given to wonder why I have two processes instead of one...just curious.
So, anyway, I've been experimenting while composing this post. As noted above I adjusted the maximum simulataneous requests up to 200. I was hoping this would solve my problem, but CF just crashed again (rather it slogged down and requests started timing out...so effectively "crashed"). This time, top looked similar (still consuming more than 99% of the CPU), but CF status looked different:
Pg/Sec DB/Sec CP/Sec Reqs Reqs Reqs AvgQ   AvgReq AvgDB Bytes Bytes
Now Hi Now Hi Now Hi Q'ed Run'g TO'ed Time   Time   Time   In/Sec Out/Sec
0   0   0   0   -1 -1 0     150   0     0      0      0      0      0
Obviously, since I'd increased the maximum simultaneous requests, it was allowing more requests to run simultaneously...but it was still maxing out the server resources.
Further experiments (after restarting CF) showed me that the server became unusably slogged after about 30-35 "Reqs Run'g", with all additional requests headed for an inevitible timeout:
Pg/Sec DB/Sec CP/Sec Reqs Reqs Reqs AvgQ   AvgReq AvgDB Bytes Bytes
Now Hi Now Hi Now Hi Q'ed Run'g TO'ed Time   Time   Time   In/Sec Out/Sec
0   0   0   0   -1 -1 0     33    0     0      -492   0      0      0
So, it's clear that increasing the maximum simultaneous requests has not helped. I guess what it comes down to is this: What is it having such a hard time with? Where are these spikes coming from? Bursts of traffic? On what pages? What requests are running at any given time? I guess I simply need more information to continue troubleshooting. If there are long-running requests, or other issues, I'm not seeing it in the logs (although I do have that option checked in the admin). I need to know which requests exactly are those responsible for these spikes. Any help would be much appreciated. Thanks.
~Day

I really appreciate your help. However, I haven't been able to find the JRun Thread settings you describe above.
Under Request Tuning, I see:
Server Settings > Request Tuning
Request Limits
Maximum number of simultaneous Template requests
Restricts the number of simultaneously processed requests. Use this setting to increase overall system performance for heavy load applications. Requests beyond the specified limit are queued. On Standard Edition, you must restart ColdFusion to enable this setting.
Maximum number of simultaneous Flash Remoting requests
The number of Flash Remoting requests that can be processed concurrently.
Maximum number of simultaneous Web Service requests
The number of Web Service requests that can be processed concurrently.
Maximum number of simultaneous CFC function requests
The number of ColdFusion Component methods that can be processed concurrently via HTTP. This does not affect invocation of CFC methods from within CFML, only methods requested via an HTTP request.
Tag Limit Settings
Maximum number of simultaneous Report threads
The maximum number of ColdFusion reports that can be processed concurrently.
Maximum number of threads available for CFTHREAD
The maximum number of threads created by CFTHREAD that will be run concurrently. Threads created by CFTHREAD in excess of this are queued. On Standard Edition, the maximum limit is 10.
And under Java and JVM, I see:
Server Settings > Java and JVM
    Java and JVM settings control the way ColdFusion starts the Java Virtual Machine when it starts. You can control settings like what classpaths are used and how memory is allocated as well as add custom command line arguments. Changing these settings requires restarting ColdFusion. If you enter an incorrect setting, ColdFusion may not restart properly.
   Backups of the jvm.config file are created when you hit the submit button. You can use this backup to restore from a critical change.
   Java Virtual Machine Path
Specifies the location of the Java Virtual Machine.
   Minimum JVM Heap Size (MB)         Maximum JVM Heap Size (MB)
   The Memory Size settings determine the amount of memory that the JVM can use for programs and data.
   ColdFusion Class Path
Specifies any additional class paths for the JVM, with multiple directories separated by commas.
   JVM Arguments
-server -Dsun.io.useCanonCaches=false -XX:MaxPermSize=192m -XX:+UseParallelGC -Xbatch -Dcoldfusion.rootDir={application.home}/../ -Dcoldfusion.libPath={application.home}/../lib
Specifies any specific JVM initialization options, separated by spaces.
I did go take a look at FusionReactor and found it's not free (which would be fine, of course, if it would actually help). It looks like there's a fully functional demo, which is cool...but I've haven't been able to get it to install yet, so we'll see.
Thanks again!
~Day
(By the way, I've cross-posted this inquiry on StackOverflow. So if you're able to help me arrive at a solution you might want to answer there as well.)

Custom thread pool for Java 8 parallel stream

It seems that it is not possible to specify thread pool for Java 8 parallel stream. If that's so, the whole functionality is useless in most of the situations. The only situation I can safely use it is a small single threaded application written by one person.
In all other cases, if I can not specify the thread pool, I have to share the default pool with other parts of the application. If someone submits a task that takes a lot of time, my tasks will get stuck. Is that correct or am I overlooking something?
Imagine that someone submits slow networking operation to the fork-join pool. It's not a good idea, but it's so tempting that it will be happening. In such case, all CPU intensive tasks executed on parallel streams will wait for the networking task to finish. There is nothing you can do to defend your part of the application against such situations. Is that so?

You are absolutely correct. That isn't the only problem with using the F/J framework as the parallel engine for bulk operations. Have a look http://coopsoft.com/ar/Calamity2Article.html

ExecutorService - thread pool

Similar Messages

Maybe you are looking for