[concurrency-interest] Single-threaded ForkJoinPool
viktor.klang at gmail.com
Sat Feb 6 05:21:31 EST 2016
What happens if you supply it with a thread factory which only allows a
single thread to be alive at a time, and returns null if it already has
returned a still living thread?
On Feb 6, 2016 05:19, "cowwoc" <cowwoc at bbs.darktech.org> wrote:
> Is this the correct mailing list for discussing ForkJoinPool in JDK9? If
> not, please point me to the right place.
> I have a feature request for ForkJoinPool which doesn't seem to be possible
> to implement without a JDK change:
> Specifically, I need to be able to an application that uses Random and
> ForkJoinPool in a deterministic manner when debugging/profiling but run
> full-speed in normal execution mode. I have all the moving parts nailing
> down except for ForkJoinPool.
> If I create ForkJoinPool with a parallelism of 1, sometimes I see two
> threads getting used. I am guessing that this is caused by
> ForkJoinTask.get() invoking ForkJoinPool.common.externalHelpComplete(), but
> maybe something else is going on.
> Is there a way for me to guarantee that ForkJoinThread will use exactly 1
> worker thread, no less, no more? Would you like me to file a formal feature
> Thank you,
> View this message in context:
> Sent from the JSR166 Concurrency mailing list archive at Nabble.com.
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Concurrency-interest