Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-10663

bin/runjava tries to evaluate an empty value as a candidate JVM pathname



    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 24.0.0
    • Fix Version/s: 24.0.0
    • Component/s: Build / Packaging
    • Security Level: Default (Default Security Scheme)
    • Labels:
    • Environment:
    • Sprint:
      Horizon - April 17th 2019


      Installing in a Vagrant box, which previously came up ready to roll. I recently noticed that OpenNMS was not coming up on its own and tracked it down to the lack of a java.conf. It appears there's a twofold problem:

      1) No JDK is installed (previously we grabbed whatever Oracle JDK was in the Horizon repo)
      2) runjava thinks it has a candidate JVM when in fact it's dealing with a phantom empty value and treating it as a pathname

      [vagrant@horizon-24-0-0 ~]$ sudo /opt/opennms/bin/runjava -s
      runjava: Looking for an appropriate JRE...
      runjava: Checking for an appropriate JRE in JAVA_HOME...
      runjava: skipping... JAVA_HOME not set
      runjava: Checking JRE in user's path: ""...
      runjava:  is not a supported JVM.
      runjava: You can use the '-f' option to ignore this check, but you will be on your own for support.
      runjava: did not find an appropriate JRE in user's path: ""
      runjava: searching for a good JRE...
      runjava: /opt/opennms/bin/find-java.sh failed to find a valid JDK. Falling back to the old algorithm.
      runjava: did not find an appropriate JRE while searching for one
      runjava: Could not find an appropriate JRE.
      runjava: You can set a particular JRE by using
      runjava: "runjava -S <JRE>".




            • Assignee:
              ranger Benjamin Reed
              jeffg Jeff Gehlbach
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created: