[
https://issues.redhat.com/browse/WFCORE-5092?page=com.atlassian.jira.plug...
]
Walter Raaflaub commented on WFCORE-5092:
-----------------------------------------
my_keycloak_service-stderr.2020-08-30.log:
{code:java}
2020-08-30 11:08:21 Commons Daemon procrun stderr initialized
Das System kann den angegebenen Pfad nicht finden.
{code}
my_keycloak_service-stdout.2020-08-30.log:
{code:java}
...
11:09:29,046 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 11.0.1
(WildFly Core 12.0.3.Final) started in 66165ms - Started 588 of 886 services (601 services
are lazy, passive or on-demand)
11:09:29,217 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management
interface listening on
http://127.0.0.1:9990/management
11:09:29,334 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console
listening on
http://127.0.0.1:9990
Drcken Sie eine beliebige Taste . . .{code}
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.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)