On Thu, 09 Oct 2014 10:54:35 +0200, Kristian Rosenvold wrote:
> Wow, that certainly fixed the problem. Stuff seems noticeably faster,
> too ! Do you know if this has been reported to the JDK ?
Good to know that you see the same effect. :)
I think I read that the JRuby folks set this by default as
Hi Holger,
> I am quite certain the problem has to do with tiered compilation being
> on by default in JDK8 and kicking in/still
Isn't it on by default in JDK7 as well (last I can remember it was
turned on in one of the builds and stayed on).
Dawid
--
Hi Kristian,
you can log an incident at bugs.sun.com. Pass me the incident number and
I will monitor it's progress.
Rgds,Rory
On 09/10/2014 09:38, Kristian Rosenvold wrote:
Making minimal test cases is always interesting :)
It appears there is some additional constraint that needs to be
satisf
Wow, that certainly fixed the problem. Stuff seems noticeably faster,
too ! Do you know if this has been reported to the JDK ?
Kristian
2014-10-09 10:41 GMT+02:00 Holger Hoffstätte
:
> On Thu, 09 Oct 2014 08:18:34 +0100, Rory O'Donnell Oracle, Dublin Ireland
> wrote:
>
>> Can you log a Java Inci
On Thu, 09 Oct 2014 08:18:34 +0100, Rory O'Donnell Oracle, Dublin Ireland
wrote:
> Can you log a Java Incident and I will follow up ?
I am quite certain the problem has to do with tiered compilation being
on by default in JDK8 and kicking in/still running while the VM tries
to exit after a brief
Making minimal test cases is always interesting :)
It appears there is some additional constraint that needs to be
satisfied, so further research needs to be done to determine the exact
cause of the problem.
It does seem to affect most of the forking code in maven, which should
imply some kind of
Hi Kristian,
Can you log a Java Incident and I will follow up ?
Rgds,Rory
On 09/10/2014 07:14, Kristian Rosenvold wrote:
It would appear that the ThreadPoolExecutor in UNIXProcess can keep
the vm running for up to 12 seconds after the last process has been
forked. Once you see the symptom it is
It would appear that the ThreadPoolExecutor in UNIXProcess can keep
the vm running for up to 12 seconds after the last process has been
forked. Once you see the symptom it is clearly visible; maven appears
to finish the build normally, but there is a short pause after this
message and the return of
