Swing Worker Threads Not Concurrent

Question

It seems that when I instantiate 12 Swing Worker threads, the first six starts to complete its task, it finishes AND then the last six starts and finishes. The behavior I'm looking for is all 12 threads start working at the same time & finish at the same time.

I have the following:

for (int i = 0; i < 12; i++ )
{
        myTask m = new Mytask(i, START);
        m.execute();
}

The myTask m will increment a progress bar from 0 - 100 in increments of 25. I'm getting outlandish behavior that the first six threads start incrementing, they finish at 100, then the last six threads start from 0 and increment, and finish.

Is there a limiting factor on the amount of Swing Worker threads one may have?

score 7 · Accepted Answer · answered Aug 27 '10 at 22:22

7

The behavior I'm looking for is all 12 threads start working at the same time & finish at the same time.

A CountDownLatch is designed for this very purpose. Here's a good example using a single SwingWorker and a number of subsidiary threads controlled by the latch.

answered Aug 27 '10 at 22:22

trashgod

203,806
29
246
1,045

my learn item of the day :-) Only don't like one aspect of the example: the tasks access the textComponent off the EDT (which at that time still was documented to be be thread-safe ... which always was argued ...) In short: better not rely on it and wrap in an invokeLater – kleopatra Mar 20 '12 at 11:17
@kleopatra: Well spotted! This [example](http://stackoverflow.com/a/3245805/230513) had a similar (latent) problem; its `display()` method illustrates your suggestion. – trashgod Mar 20 '12 at 17:14

YoK · Answer 2 · 2010-08-27T18:55:08.383

2

Your question says:

The behavior I'm looking for is all 12 threads start working at the same time & finish at the same time.

But you can't guarantee for all Swing workers threads starting concurrently and ending at same time.

edited Aug 27 '10 at 18:55

answered Aug 27 '10 at 18:45

YoK

14,329
4
49
67

Why not? What's the reasoning behind that? – Aug 27 '10 at 18:45
Because they are Threads, And execution of Threads depends upon multiple facyors, cpu no., OS , available resources etc. etc. – YoK Aug 27 '10 at 18:47
See my answer for an alernative. – trashgod Aug 27 '10 at 22:24

score 2 · Answer 3 · answered Aug 27 '10 at 18:46

2

SwingWorker class has a static ExecutorService field with MAX_WORKER_THREADS = 10. I'm not certain why you see 6 and not 10. But you cannot go over 10.

    /**
     * number of worker threads.
     */
    private static final int MAX_WORKER_THREADS = 10;

...

    executorService =
                new ThreadPoolExecutor(1, MAX_WORKER_THREADS,
                                       10L, TimeUnit.MINUTES,
                                       new LinkedBlockingQueue<Runnable>(),
                                       threadFactory);

answered Aug 27 '10 at 18:46

Thierry Roy

8,452
10
60
84

Can I manually change the # of MAX_WORKER_THREADS or is that not possible? What's the reasoning of having an arbritrary number of 10 threads? – Aug 27 '10 at 18:49
No, you cannot change the # of MAX_WORKER_THREADS, since it's a final field. As for the reasoning, you need to ask Igor Kushnirskiy (the author of the class). – Thierry Roy Aug 27 '10 at 19:03
1

You could use your own ExecutorService to execute the SwingWorkers, cause they are Futures – keuleJ Aug 31 '10 at 13:26

Swing Worker Threads Not Concurrent

3 Answers3

Linked