Fixed
Details
Assignee
Donald DeslogeDonald DeslogeReporter
Andy EllsworthAndy EllsworthLabels
Components
Fix versions
Affects versions
Priority
Critical
Details
Details
Assignee
Donald Desloge
Donald DeslogeReporter
Andy Ellsworth
Andy EllsworthLabels
Components
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created August 8, 2011 at 6:05 PM
Updated January 27, 2017 at 4:20 PM
Resolved September 13, 2011 at 3:56 PM
When attempting to display a specific graph I've created for Netscreen memory utilization, I see the following symptoms:
Page renders everything but the busted graph, and browser shows that the page is still loading, seemingly forever (at least a few minutes)
Reloading the page does not help, and in fact 'top' shows that Java is eating a single CPU's worth of resources for each time I reload and trigger another hung/spinning thread
Deleting the .jrb file and allowing it to be recreated also does not help
I restarted OpenNMS and then triggered the condition via page reload, taking thread dumps at 1, 2, 3, 4, 5, 10, 15, and 20 hung threads. That data is attached in the "thread dumps" zipfile.
I have also attached the corresponding .jrb files for three Netscreen nodes that all exhibit this behavior. I'm using store by group and have included the ds.properties file, as well as the graph definition (report.juniper.netscreen.host.memory is the glitched graph).