[
https://issues.apache.org/jira/browse/DAEMON-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved DAEMON-404.
--------------------------------
Fix Version/s: 1.2.1
Resolution: Fixed
Newer versions of Java do not install a separate JRE. The search algorithm used
by procrun only looked in the registry for the runtime lib and the JRE. It did
not look for the JDK. I've added the JDK to the search and updated the docs to
document the search order used when looking for jvm.dll.
> Crash: Openjdk not detected from registry
> -----------------------------------------
>
> Key: DAEMON-404
> URL: https://issues.apache.org/jira/browse/DAEMON-404
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Affects Versions: 1.1.0, 1.2.0
> Environment: Windows Server 2016 / 1607
> Reporter: Michael Lemke
> Priority: Major
> Fix For: 1.2.1
>
>
> I have openjdk 12 installed and {{Jvm=auto}} set. When I start procrun 1.2.0
> the service crashes with an access violation. With procrun 1.1.0 the service
> doesn't find the dll at all.
> Openjdk is from
> [https://github.com/ojdkbuild/ojdkbuild/releases/download/12.0.1-1/java-12-openjdk-12.0.1.12-1.windows.ojdkbuild.x86_64.msi]
> and installed such that it only sets the keys under {{HKLM\JavaSoft\JDK}} and
> updates {{PATH}}. No {{JAVA_HOME}} set. There are no other Java installations
> besides OpenJdk.
> If I change {{HKLM\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun
> 2.0\servicename\Parameters\Java}} from {{auto}} to the actual path of the
> OpenJdk jvm.dll the service starts just fine.
> The situation is the same with the OpenJdk build from AdoptOpenJDK. The keys
> created under {{HKLM\JavaSoft}} are slightly different, though.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
