[concurrency-interest] java.util.concurrent.ThreadPoolExecutordoes not execute jobs in some cases
davidcholmes at aapt.net.au
Sun May 9 00:18:03 EDT 2010
In this case I can't see that the bug report ever actually became a CR. In
the earlier email exchanges I thought the problem was with setting a zero
Not only do many (most?) OpenJDK6 bugs not get fixed in the Sun/Oracle JDK
releases but many/most fixes that went into OpenJDK7 prior to openJDK6
existing, are also not in OpenJDK6.
Martin Buchholz writes on Sunday, 9 May 2010 11:39 AM:
> Unfortunately, I don't think the ThreadPool fixes
> were backported to the proprietary JDK 6 code base,
> but they are in OpenJDK6 and OpenJDK7.
> You can try using the ThreadPoolExecutor from openjdk6,
> or from Doug's CVS.
> On Sat, May 8, 2010 at 11:33, Ashwin Jayaprakash
> <ashwin.jayaprakash at gmail.com> wrote:
> > This is an old email, but I found out today that there were
> still strange
> > problems on JDK 6_18 related to this coreThread count.
> > Even with coreThreads=maxThreads, some pools would never start and would
> > never process any job. The solution required calling
> > prestartAllCoreThreads(). I will investigate more later, but
> for anyone else
> > facing this problem it will help. Calling just
> prestartCoreThread() might
> > also work, but I haven't tried.
> > Ashwin.
> > _______________________________________________
> > Concurrency-interest mailing list
> > Concurrency-interest at cs.oswego.edu
> > http://cs.oswego.edu/mailman/listinfo/concurrency-interest
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
More information about the Concurrency-interest