]
Lukas Vydra moved WFLY-13537 to WFCORE-5092:
--------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-5092 (was: WFLY-13537)
Component/s: Scripts
(was: Scripts)
Affects Version/s: 11.0.0.Final
(was: 11.0.0.Final)
Windows Service cannot be stopped when using custom JAVA_HOME path
------------------------------------------------------------------
Key: WFCORE-5092
URL:
https://issues.redhat.com/browse/WFCORE-5092
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Affects Versions: 11.0.0.Final
Reporter: Walter Raaflaub
Assignee: Lukas Vydra
Priority: Major
I am running keycloak in a Wildfly container as a Windows service on Windows Server 2019.
The service starts up and works correctly; but it hangs when I try to stop it.
There is no global JAVA_HOME environment variable defined on the server; I'm using a
custom JAVA_HOME path that I have configured in standalone.conf.bat.
While stopping, the service issues the following warning in stdout.log:
{noformat}
JAVA_HOME is not set. Unexpected results may occur.
Set JAVA_HOME to the directory of your local JDK to avoid this message.
Drcken Sie eine beliebige Taste . . .
{noformat}
(Drücken Sie eine beliebige Taste . . . = German vor "Press any key ...")
It seems that when stopping the service, the JAVA_HOME setting is not correctly passed to
the jboss-cli.bat script. The script seems to be waiting for user input, which is akward
in a Windows service. That means that also the NOPAUSE setting is not passed correctly to
the jboss-cli.bat script.