Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Additional fixes pushed to 1.8 in commit 758b39c0c41d0c6a891ea6f3da53c7d6c736a93d and cherry-picked to master in commit 3d441165408e1f65750e5f918387588f88c84e3c.
Jeff Gehlbach April 25, 2011 at 3:05 PM
Found a couple more NPE sources. Also, we should indicate to the user when we don't have any data and provide a hint on configuring logging so that we'll get some.
Seth Leger February 10, 2011 at 10:36 PM
This was caused by trying to inspect the modification time on a null log entry (probably when the instrumentation log is empty). I've added a check for this case that will prevent this problem. Marking as fixed.
commit e1373eda83c1df87b54e485be6f6bb05d9de94cb
Adam Monsen August 31, 2010 at 2:26 AM
Created an attachment (id=1078) javax.el.ELException: java.lang.NullPointerException from jetty.log
When I click on Admin ? Instrumentation Log Reader I get an error.
This is a stock install of opennms 1.8.3 (via http://debian.opennms.org package archive) on Ubuntu 10.04.
I'll attach the relevant error from jetty.log.