Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

OpenNMS 1.11.91 requires a JDK to be installed for Jetty to display the login page

Description

If using (only) Java runtime packages ("openjdk-7-jre" or "openjdk-7-jre-headless"), OpenNMS 1.11.90 and 11.11.91-0.20130422.3 (the current snapshot) will not display the web login page when going to /opennms.

daemon/uncategorized.log seems to have the reason:

2013-04-22 23:07:59,472 WARN [qtp1991606348-386] /opennms: Something went horribly awry.
org.apache.jasper.JasperException: java.err.nojdk
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:89)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:375)
...

This message at the jetty-users mailing list says "The issue is that we updated the version of jasper (jsp engine from Glassfish) that we use in 7.5.0 and it insists on using the in-jvm compiler if you're using jdk1.6 or above. Therefore, you need to have a full jdk installed (until we can get a patch into a release, stay tuned for that)."

http://dev.eclipse.org/mhonarc/lists/jetty-users/msg01629.html

This appears to be the case with OpenNMS 1.11.9x. After installing a Java compiler package ("openjdk-7-jdk"), the login screen appeared.

Environment

Ubuntu 12.04.2 LTS 64-bit, Java 7

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Markus von Rüden October 2, 2019 at 12:32 PM

Then let's just close this off. However feel free to reopen if this is still an issue with newer versions of OpenNMS.

Benjamin Reed October 2, 2019 at 12:25 PM

Since OpenJDK 11 only comes as a JDK and they dropped the distinctions I would think this isn’t really relevantly anymore…

Markus von Rüden October 2, 2019 at 12:15 PM

is this still a thing? To me it looks like we can just close this. What do you say?

Robert Drake June 10, 2014 at 8:03 PM

Just ran into this. I'm running debian and 1.12.5 and switched from sun-java6-jre to openjdk7-jre-headless. I had the sun-java6-jdk package installed because I used to compile opennms on the box. update-alternatives did not work for me.

I just removed the old sun-java6 and it installed normal openjdk7-jre:

rdrake@nms3:/etc/default$ sudo apt-get purge sun-java6-bin sun-java6-jdk sun-java6-jre
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libasyncns0 libatk-wrapper-java libatk-wrapper-java-jni libflac8 libgif4 libjson0 libogg0 libpulse0 libsndfile1 libvorbis0a libvorbisenc2 openjdk-7-jre
Suggested packages:
pulseaudio icedtea-7-plugin
Recommended packages:
libgnome2-0 libgnomevfs2-0 libgconf2-4
The following packages will be REMOVED:
sun-java6-bin* sun-java6-jdk* sun-java6-jre*
The following NEW packages will be installed:
libasyncns0 libatk-wrapper-java libatk-wrapper-java-jni libflac8 libgif4 libjson0 libogg0 libpulse0 libsndfile1 libvorbis0a libvorbisenc2 openjdk-7-jre
0 upgraded, 12 newly installed, 3 to remove and 36 not upgraded.
Need to get 1,272 kB of archives.

Once this was done a restart of opennms cured it.

rdrake@nms3:/etc/default$ dpkg -l | grep jdk
ii openjdk-7-jre:amd64 7u55-2.4.7-1~deb7u1 amd64 OpenJDK Java runtime, using Hotspot JIT
ii openjdk-7-jre-headless:amd64 7u55-2.4.7-1~deb7u1 amd64 OpenJDK Java runtime, using Hotspot JIT (headless)

So, no JDK required. I would say that the error message might be cryptic or wrong, but it's probably a bug in Jetty more than opennms.

Alejandro Galue April 15, 2014 at 3:48 PM

I've found on a customer site this issue with 1.12.5 on CentOS 6.5.

He had OpenJDK installed. I've suggested to use Oracle JDK 7u45 instead, and the problem has disappeared, so I think the issue is related with OpenJDK somehow.

Won't Fix

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created April 23, 2013 at 12:10 AM
Updated October 2, 2019 at 12:32 PM
Resolved October 2, 2019 at 12:32 PM

Flag notifications