«

I have 25 threads that start at once. I need to wait until the last
one completes. Is there a better way to handle that than using a
ThreadPoolExecutor which seems overkill.
--
Roedy Green Canadian Mind Products http://mindprod.com
Students who hire or con others to do their homework are as foolish
as couch potatoes who hire others to go to the gym for them.

On 1/11/2013 1:56 PM, Roedy Green wrote:
> I have 25 threads that start at once. I need to wait until the last
> one completes. Is there a better way to handle that than using a
> ThreadPoolExecutor which seems overkill.
>

The Executors class has convenience methods to make thread pools easier
to use.

ExecutorService es = Executors.newFixedThreadPool( 25 );
// submit jobs here
es.shutdown();

The shutdown() will wait for all jobs to finish. I don't think you can
get easier than that. It's two lines of code!

On Fri, 11 Jan 2013 14:05:10 -0800, markspace
<> wrote, quoted or indirectly quoted someone
who said :

>
> ExecutorService es = Executors.newFixedThreadPool( 25 );
> // submit jobs here
> es.shutdown();

Excellent!
--
Roedy Green Canadian Mind Products http://mindprod.com
Students who hire or con others to do their homework are as foolish
as couch potatoes who hire others to go to the gym for them.

On 1/11/2013 2:14 PM, Roedy Green wrote:
> On Fri, 11 Jan 2013 14:05:10 -0800, markspace
> <> wrote, quoted or indirectly quoted someone
> who said :
>
>>
>> ExecutorService es = Executors.newFixedThreadPool( 25 );
>> // submit jobs here
>> es.shutdown();
>
> Excellent!
>

Oops, sorry, it's awaitTermination() that you want, not shutdown().

On 1/11/2013 6:11 PM, markspace wrote:
> On 1/11/2013 2:14 PM, Roedy Green wrote:
>> On Fri, 11 Jan 2013 14:05:10 -0800, markspace
>> <> wrote, quoted or indirectly quoted someone
>> who said :
>>
>>>
>>> ExecutorService es = Executors.newFixedThreadPool( 25 );
>>> // submit jobs here
>>> es.shutdown();
>>
>> Excellent!
>
> Oops, sorry, it's awaitTermination() that you want, not shutdown().

If the Java docs are to be believed he actually wants both.

<quote>
Blocks until all tasks have completed execution after a shutdown
request, or
</quote>

Arne

On 1/11/2013 1:56 PM, Roedy Green wrote:
> I have 25 threads that start at once. I need to wait until the last
> one completes. Is there a better way to handle that than using a
> ThreadPoolExecutor which seems overkill.
>

You can always join() them.

--

Knute Johnson

On Fri, 11 Jan 2013 15:11:17 -0800, markspace
<> wrote, quoted or indirectly quoted someone
who said :

>
>Oops, sorry, it's awaitTermination() that you want, not shutdown().

Working great. Thanks.
--
Roedy Green Canadian Mind Products http://mindprod.com
Students who hire or con others to do their homework are as foolish
as couch potatoes who hire others to go to the gym for them.

On Fri, 11 Jan 2013 15:11:17 -0800, markspace
<> wrote, quoted or indirectly quoted someone
who said :

>
>Oops, sorry, it's awaitTermination()

I think there is a bug. If there are no threads submitted it hangs.
--
Roedy Green Canadian Mind Products http://mindprod.com
Students who hire or con others to do their homework are as foolish
as couch potatoes who hire others to go to the gym for them.

On 01/11/2013 05:56 PM, Roedy Green wrote:
> I have 25 threads that start at once. I need to wait until the last
> one completes. Is there a better way to handle that than using a
> ThreadPoolExecutor which seems overkill.
>
Any reason why you couldn't use CyclicBarrier?

AHS

On 1/12/2013 5:20 AM, Roedy Green wrote:
> On Fri, 11 Jan 2013 15:11:17 -0800, markspace
> <> wrote, quoted or indirectly quoted someone
> who said :
>> Oops, sorry, it's awaitTermination()
>
> I think there is a bug. If there are no threads submitted it hangs.

You meed to call shutdown first.

It is documented.

http://mindprod.com/jgloss/rtfm.html



Arne