Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #29195
| From | Eric Sosman <esosman@comcast-dot-net.invalid> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: thread pool |
| Date | 2014-07-22 09:11 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <lqlntl$gcc$1@dont-email.me> (permalink) |
| References | <lqlna0$23fm$1@ariadne.rz.tu-clausthal.de> |
On 7/22/2014 9:00 AM, Philipp Kraus wrote:
> Hello,
>
> I would like to create a thread pool with threads, which are should
> stopped by the user.
> So I create my pool with
>
> m_pool = Executors.newCachedThreadPool();
> for (int i = 0; i < m_barrier.getParties(); i++)
> m_pool.submit(new Worker(m_barrier));
>
> my Worker implements Runnable with the run-method
>
> while (!Thread.currentThread().isInterrupted()) {
> // do something
> }
>
> Within the while-loop I run my barrier and I catch the InterruptedException
>
> I would like to create a thread pool with a number of threads, which
> runs until the user
> sends a stop signal. At the moment I run m_pool.shutdown() and/or
> shutdownNow(), but
> which way is the correct Java structure. My target is, that a method
> creates all threads
> of the pool, each thread runs unlimited time until the user sends a stop
> signal.
If "each thread runs unlimited time," why use a thread pool? The
purpose of this kind of pool is to run many short-lived (usually) tasks
on a set of threads, with each thread handling many tasks in succession.
You don't need that (it seems), so wouldn't it be simpler to launch
as many threads as you want and just let them run? When it's time to
stop you can interrupt them all (telling them to quit) and join them
all (so you'll know when all the quitting's finished).
If that doesn't seem to meet your need, please describe what you're
trying to do in more detail.
--
esosman@comcast-dot-net.invalid
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
thread pool Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-07-22 15:00 +0200
Re: thread pool Eric Sosman <esosman@comcast-dot-net.invalid> - 2014-07-22 09:11 -0400
Re: thread pool Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-07-22 16:32 +0200
Re: thread pool Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-07-22 21:38 +0200
Re: thread pool Eric Sosman <esosman@comcast-dot-net.invalid> - 2014-07-22 16:29 -0400
Re: thread pool Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-07-22 23:01 +0200
Re: thread pool Eric Sosman <esosman@comcast-dot-net.invalid> - 2014-07-22 17:14 -0400
Re: thread pool Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-07-23 08:11 +0200
Re: thread pool Eric Sosman <esosman@comcast-dot-net.invalid> - 2014-07-23 07:24 -0400
Re: thread pool Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-07-23 15:57 +0200
Re: thread pool Eric Sosman <esosman@comcast-dot-net.invalid> - 2014-07-23 11:41 -0400
Re: thread pool Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-07-24 09:55 +0200
Re: thread pool Eric Sosman <esosman@comcast-dot-net.invalid> - 2014-07-24 08:39 -0400
Re: thread pool Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-07-24 20:50 -0700
csiph-web