Please, review another revision of the fix for
the enhancement:
https://bugs.openjdk.java.net/browse/JDK-8061228
CSR:
https://bugs.openjdk.java.net/browse/CCC-8061228
The SCR is in the DRAFT state.
Joe suggested to consider this C
Ping!
Unless I hear back otherwise, I'll attempt to add the extra exception
handling, finish up testing (sans running all tests under docker), and
send out a review.
thanks,
Chris
On 8/17/17 5:15 PM, Chris Plummer wrote:
Hi TJ,
JDK-8179498 is assigned to me. I've been playing around with
Thanks for your comments, Mandy.
On pondělí 21. srpna 2017 12:42:09 CEST mandy chung wrote:
> cc'ing serviceability-dev which is the right mailing list for platform
> management discussion.
>
> JVMCI is currently named as `jdk.internal.vm.ci` (a JDK internal
> module). I suppose this new module
On 8/22/17 6:19 AM, Jaroslav Tulach wrote:
Thanks for your comments, Mandy.
On pondělí 21. srpna 2017 12:42:09 CEST mandy chung wrote:
cc'ing serviceability-dev which is the right mailing list for platform
management discussion.
JVMCI is currently named as `jdk.internal.vm.ci` (a JDK interna
Hi,
jcmd GC.run to invoke GC fails if -XX:+DisableExplicitGC is set: this
seems like a mistake?
This behaviour is obstructive for a live app that _needs_ a GC, and was
started with -XX:+DisableExplicitGC.
DisableExplicitGC to protect from Java code calling System.gc frequently
makes sense,
Kindly review the changes made.
Before these changes tests fail on windows if we execute them from any
Drive other than C.
grant codebase "file:/-" {} is granting permissions only to code
present in C Drive on windows.
Hence changing'grant codebase "file:/-" {} ' to grant {} will sol
