[Bug 3237] New: JvmStatDataExtractor might throw monitor exception on retrieving certain info of a JVM

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3237

            Bug ID: 3237
           Summary: JvmStatDataExtractor might throw monitor exception on
                    retrieving certain info of a JVM
           Product: Thermostat
           Version: hg
          Hardware: x86_64
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: agent
          Assignee: unassigned at icedtea.classpath.org
          Reporter: sgehwolf at redhat.com
                CC: thermostat at icedtea.classpath.org

I'm seeing an issue where the JVM does not get detected by thermostat due to an
exception being thrown before the actual vm-info record gets created:

Nov 23, 2016 3:15:35 PM
com.redhat.thermostat.backend.system.JvmStatHostListener vmStatusChanged
WARNING: error getting info for new vm 1
sun.jvmstat.monitor.MonitorException: Could not synchronize with target
    at
sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.synchWithTarget(PerfDataBuffer.java:277)
    at
sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.buildMonitorMap(PerfDataBuffer.java:131)
    at
sun.jvmstat.perfdata.monitor.PerfDataBufferImpl.findByName(PerfDataBufferImpl.java:241)
    at
sun.jvmstat.perfdata.monitor.AbstractPerfDataBuffer.findByName(AbstractPerfDataBuffer.java:100)
    at
sun.jvmstat.perfdata.monitor.AbstractMonitoredVm.findByName(AbstractMonitoredVm.java:85)
    at
com.redhat.thermostat.backend.system.JvmStatDataExtractor.getJavaVersion(JvmStatDataExtractor.java:78)
    at
com.redhat.thermostat.backend.system.JvmStatHostListener.createVmInfo(JvmStatHostListener.java:161)
    at
com.redhat.thermostat.backend.system.JvmStatHostListener.sendNewVM(JvmStatHostListener.java:135)
    at
com.redhat.thermostat.backend.system.JvmStatHostListener.vmStatusChanged(JvmStatHostListener.java:103)
    at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.fireVmStatusChangedEvents(MonitoredHostProvider.java:177)
    at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.access$300(MonitoredHostProvider.java:41)
    at
sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider$NotifierTask.run(MonitoredHostProvider.java:218)
    at java.util.TimerThread.mainLoop(Timer.java:555)
    at java.util.TimerThread.run(Timer.java:505)

The JVM itself (the pid) is there, but figuring out the Java Version for that
JVM process fails. This looks a lot like these JDK bugs:

http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6637230
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6602355

I'll try to create a simple reproducer for this. Either way, it should not fail
to create the vm-info record. Instead, it should fill in some
place-holder-value like "X unavailable" and once it does become available it
should update it.

Running jps on this system returns:
1 -- main class information unavailable

and once that JVM properly settles it changes to:
1 Bootstrap

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20161123/d371662c/attachment-0001.html>