Re: ThreadPoolExecutor backport
- From: Lew <lew@xxxxxxxxxxxxx>
- Date: Thu, 31 Jul 2008 09:08:42 -0700 (PDT)
Philipp wrote:
Q: Why does the boolean flag isPaused need not be volatile?
As I see it, it will be polled and set by different threads and
nothing guarantees a memory barrier.
Nothing but the 'pauseLock.lock()', that is.
Thanks for your non-answer. It made me look harder.
"non-answer"? It turned to to be exactly the answer, as your
description clearly shows.
Happy to help.
--
Lew
.
- References:
- ThreadPoolExecutor backport
- From: Philipp
- Re: ThreadPoolExecutor backport
- From: Lew
- Re: ThreadPoolExecutor backport
- From: Philipp
- ThreadPoolExecutor backport
- Prev by Date: Selector.select() won't work on MacOS X (JVM 1.6.0_05)
- Next by Date: Apache Tomcat 6.0.18
- Previous by thread: Re: ThreadPoolExecutor backport
- Next by thread: Re: ThreadPoolExecutor backport
- Index(es):