[Bug 3054] New: Intermittent NPE on launch causes agent to fail to pickup jvms

[bugzilla-daemon at icedtea.classpath.org]

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

            Bug ID: 3054
           Summary: Intermittent NPE on launch causes agent to fail to
                    pickup jvms
           Product: Thermostat
           Version: hg
          Hardware: x86_64
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Thermostat
          Assignee: unassigned at icedtea.classpath.org
          Reporter: jkang at redhat.com
                CC: thermostat at icedtea.classpath.org

Sometimes when launching thermostat local/web-storage/web-storage-service there
is an NPE in the logs and no jvms can be seen in the gui apart from the
local/web-storage/webstorage-service jvm.

This has been seen in 1.4 (from dnf install on F23), 1.6 (repo) and HEAD
(1.99.x repo).


Exception in thread "Timer-1" java.lang.NullPointerException
    at
com.redhat.thermostat.thread.harvester.ThreadHarvester.updateHarvestingStatus(ThreadHarvester.java:198)
    at
com.redhat.thermostat.thread.harvester.ThreadHarvester.addThreadHarvestingStatus(ThreadHarvester.java:189)
    at
com.redhat.thermostat.thread.harvester.ThreadBackend.vmStatusChanged(ThreadBackend.java:122)
    at
com.redhat.thermostat.backend.system.VmStatusChangeNotifier.notifyVmStatusChange(VmStatusChangeNotifier.java:125)
    at
com.redhat.thermostat.backend.system.JvmStatHostListener.sendNewVM(JvmStatHostListener.java:142)
    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)


It looks like a timing issue where the DAO is still null when attempted to be
used at:
com.redhat.thermostat.thread.harvester.ThreadHarvester.updateHarvestingStatus(ThreadHarvester.java:198)

-- 
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/20160627/f0909b27/attachment.html>