Hi Seth,

thanks for fixing that.
As I don´t use this feature right now, I´ll wait for 1.8.12.

Daniel

OK it appears that your JVM is throwing a reflection exception when trying to execute the toString() method when gathering the data for the Java information plugin. After asking around, most of the system report testing was done with Java 1.6 instead of the 1.5 version that you are using.

I'm guessing that Sun improved the MXBean classes in Java 1.6 so that they support the toString() method (which would make sense because toString() is a standard object method in Java) but that this call fails when you are using Java 1.5. I've gone ahead and removed the calls inside the plugin that call toString() because they were just for logging anyway.

So to get your system working, you have several options:

• Don't use the Java information plugin when running the system report since it is the plugin that is causing problems.

• Upgrade to Java 1.6 because all of our unit tests indicate that the plugin will always work properly with 1.6.

• Download the latest source code to OpenNMS 1.8 (which contains my toString() fix), rebuild the features/system-report project, copy the resulting JAR file to /opt/opennms/lib/opennms_system_report.jar, and restart OpenNMS. This should fix the issue when using Java 1.5.

• Wait until the next version of 1.8 is released and upgrade to it when it is available.

Thanks!

I used the default with everything checked.
The stacktrace is attached and it looks very similar if I selct text or xml.

system-report stacktrace from jetty.log

Hi Daniel,

If you are not seeing any output when you have all of the plugins selected, then something is wrong. The JVM, OS, OpenNMS, and Top Event plugins should produce output regardless of the formatter. Can you check your jetty.log file to see if any exceptions are being generated when you run the system report from the UI? Thanks,

Seth