> On May 18, 2017, at 1:29 PM, Alan Bateman <alan.bate...@oracle.com> wrote:
> 
> On 18/05/2017 20:39, Alan Snyder wrote:
> 
>> As far as I can tell, the latest VisualVM (1.3.9) is unable to do CPU 
>> sampling or profiling on the latest EA build 
>> (9-ea+169-jigsaw-nightly-h6406-20170517).
>> 
>> Is this really the case, or am I missing something?
>> 
>> Is someone working on this?
> I took a quite look.
> 
> As Mandy said in the previous mail, the JMX interop issue between JDK 8 and 
> JDK 9 is JDK-8167121. This is fixed in jdk8u-dev but hasn't got into a 
> released JDK 8 update yet.
> 
> So as a test, I ran Visual VM 1.3.9 on a JDK 9 build to attach to an 
> application running on the same JDK 9 build. As VisualVM (or maybe the 
> NetBeans framework that it builds on) makes use of a number of JDK internal 
> APIs. It has encapsulation busting command line options configured in 
> etc/visualvm.conf but the module names aren't quite right - specifically, 
> jdk.jvmstat was renamed to jdk.internal.jvmstat a couple of builds ago. I 
> fixed those and it started up okay. I tried the Monitor, Threads, and Sampler 
> tabs and they seem to work okay.

VisualVM 1.3.9 was released on Oct 2016.  It has to be updated to work with the 
latest JDK 9 release.  You may reference the —-add-opens options used by 
NetBeans Dev version (under etc/netbeans.conf)

Mandy

Reply via email to