JMH 1.4.2

[Aleksey Shipilev]

On 15.01.2015 14:01, Aleksey Shipilev wrote:
>  * Normally, we expect users to shutdown all their threads at the end of
> the benchmark, because forked VM would not exit if non-daemon threads
> are still running. However, there are semi-legitimate use cases when
> users do not control all the threads, and this precludes the use of JMH.
> We have implemented a shutdown timeout to cover for these cases:
>    https://bugs.openjdk.java.net/browse/CODETOOLS-7901238
> 
>  * As the follow-up for introducing a shutdown timeout, we strengthened
> the recovery from other types of stuck user code, like stuck shutdown
> hooks, finalizers, etc:
>    https://bugs.openjdk.java.net/browse/CODETOOLS-7901239

Sorry, these two should be:
 https://bugs.openjdk.java.net/browse/CODETOOLS-7901244
and
 https://bugs.openjdk.java.net/browse/CODETOOLS-7901245,

...respectively.

Thanks,
-Aleksey