[DAEMON-329] Can procrun detect the JVM without consulting the registry

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.15
• Fix Version/s: 1.1.1
• Component/s: Procrun

Environment

Windows Server2012 R2 Java server installed from the tarball

• Assignee: Unassigned
• Reporter: Rod Widdowson
• Created: 26/Jan/15 13:29
• Updated: 14/Jun/19 13:45
• Resolved: 13/Jun/19 22:01

Description

For reasons I do not fully comprehend, Oracle distribute the Windows Server JVM as a tarball.

This means that none of the "usual" registry setting are written.

Our (the Shibboleth protect's) latest IdP release ships with an MSI which bundles Procrun to launch the J2EE container. We set up the HKLM\Software\Wow6432Node\Apache Software Key\Procrun 2.0\ appropriately, specifically setting 'Parameters\Java\JavaHome' appropriately and 'Parameters\Java\jvm' to 'auto'. I can provide full details available if you want.

We recently had a customer raise an issue that the autodetect of the jvm.dll wasn't working. AFAICS this customer installed from the tarball. This is easily fixed by setting 'jvm' appropriately, and I am modifying our documentation to explain what to do..

This RFE is to see if there is anyway that this can be automated inside procun. It knows the home directory and so it should be able to locate the jvm.dll.

Thanks