Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 19.0.1
-
Fix Version/s: 20.0.0, 20.0.1, Meridian-2017.1.0
-
Component/s: Installation
-
Security Level: Default (Default Security Scheme)
-
Labels:None
Description
There are some people reporting issues when they try to install OpenNMS with OpenJDK JRE instead of the JDK. See here:
http://ask.opennms.eu/?qa=1155/centos-install-fails-with-java-class-issues&show=1156#a1156
Especially when a Server with graphical environment installs an OpenJDK runtime environment. With installing OpenNMS OpenJDK development kit will not be installed when a JRE is present. The documentation should have a hint about checking the OpenJDK environment to prevent users running in this kind of issues.
Activity
It's an issue with how redhat has messed up their RPM dependencies for OpenJDK again. :/
The only real solution is for us to start depending on the actual Oracle JDK again, rather than being able to use the java-1.8.0 virtual dependency and letting it choose between Oracle JDK and OpenJDK.
Benjamin Reed
added a comment - It's an issue with how redhat has messed up their RPM dependencies for OpenJDK again. :/
The only real solution is for us to start depending on the actual Oracle JDK again, rather than being able to use the java-1.8.0 virtual dependency and letting it choose between Oracle JDK and OpenJDK. I know that people might use OpenJDK with OpenNMS, and I know that OpenNMS can run with OpenJDK, specially for testing purposes, but we always suggest people to use Oracle JDK, specially for production. Have that changed recently ? Are there people out there using OpenJDK with OpenNMS in production (medium to large environments) ?
Alejandro Galue
added a comment - I know that people might use OpenJDK with OpenNMS, and I know that OpenNMS can run with OpenJDK, specially for testing purposes, but we always suggest people to use Oracle JDK, specially for production. Have that changed recently ? Are there people out there using OpenJDK with OpenNMS in production (medium to large environments) ? The problem starts when you run apt install opennms or yum install opennms. The dependency will install the OpenJDK. The behavior installing packages from repositories behaves differently than what we say and this is confusing. Some suggestions:
- Remove the Java dependency completely and let the user ensure a suitable Java Environment is installed and tell them Oracle Java is recommended for production and OpenJDK just for testing.
- Depend on Oracle Java Development Kit 8+
Ronny Trommer
added a comment - - edited The problem starts when you run apt install opennms or yum install opennms . The dependency will install the OpenJDK. The behavior installing packages from repositories behaves differently than what we say and this is confusing. Some suggestions:
Remove the Java dependency completely and let the user ensure a suitable Java Environment is installed and tell them Oracle Java is recommended for production and OpenJDK just for testing.
Depend on Oracle Java Development Kit 8+
I agree with your suggestions.
Alejandro Galue
added a comment - I agree with your suggestions. Alejandro Galue which one the first or the second? 
Both options are valid, but there is no right option here. It is a matter of taste and personal perferences.
My personal preference would be the first one, as that gives me more flexibility, like install the JDK I want, and more importantly, the version of the JDK I want.
That being said, the second one makes easier for end users the installation process of OpenNMS (which is what I think we have right now). This will reduce the time and effort of installing OpenNMS but will reduce flexibility unless we spend time on updating our repository every time a new version of the JDK is used (which is why the first is my personal preference).
Makes sense ?
Alejandro Galue
added a comment - Both options are valid, but there is no right option here. It is a matter of taste and personal perferences.
My personal preference would be the first one, as that gives me more flexibility, like install the JDK I want, and more importantly, the version of the JDK I want.
That being said, the second one makes easier for end users the installation process of OpenNMS (which is what I think we have right now). This will reduce the time and effort of installing OpenNMS but will reduce flexibility unless we spend time on updating our repository every time a new version of the JDK is used (which is why the first is my personal preference).
Makes sense ? There is nothing stopping you from also installing the JDK you want in addition to the one that comes from the repo. It's only there to make it so people who just go "yum install opennms" don't think we're idiots for having the installation fail with dependency errors. I think we should go back to requiring oracle JDK.
Benjamin Reed
added a comment - There is nothing stopping you from also installing the JDK you want in addition to the one that comes from the repo. It's only there to make it so people who just go "yum install opennms" don't think we're idiots for having the installation fail with dependency errors. I think we should go back to requiring oracle JDK. 
The install guide clearly states that you need to have the Development Kit installed. The OpenNMS RPMs shoulds also require the JDK to be installed before they can be installed. Is this an issue with the standalone installer or is there an issue with the RPM dependencies?