[JBoss JIRA] (WFLY-13051) provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService
by nimo stephan (Jira)
[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ]
nimo stephan commented on WFLY-13051:
-------------------------------------
It is easy to "reproduce" this error by yourself. Simply try to use "_setRemoveOnCancelPolicy(true)_" in any bean and you see the error.
For example:
{code:java}
@Singleton
public class Start{
@Resource
private ManagedScheduledExecutorService executor;
@PostConstruct
void init(){
...
// this is actually not possible in JEE Environment
((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true);
}
}
{code}
> provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService
> ------------------------------------------------------------------
>
> Key: WFLY-13051
> URL: https://issues.redhat.com/browse/WFLY-13051
> Project: WildFly
> Issue Type: Enhancement
> Components: Concurrency Utilities
> Affects Versions: 19.0.0.Beta1
> Reporter: nimo stephan
> Assignee: Eduardo Martins
> Priority: Major
>
> Using
> {code:java}
> @Resource
> private ManagedScheduledExecutorService executor;
> {code}
> provides no possiblity to setRemoveOnCancelPolicy to true.
> A casting within a method:
> {code:java}
> ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true);
> {code}
> throws the error:
> {code:java}
> Caused by: javax.ejb.EJBException: java.lang.ClassCastException: class org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter cannot be cast to class java.util.concurrent.ScheduledThreadPoolExecutor (org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter is in unnamed module of loader 'org.glassfish.javax.enterprise.concurrent' @a93b7af; java.util.concurrent.ScheduledThreadPoolExecutor is in module java.base of loader 'bootstrap')
> at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246)
> at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388)
> at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68)
> {code}
> Please provide option to cast or if not possible to add the property
> {code:java}
> setRemoveOnCancelPolicy()
> {code}
> within the object ManagedScheduledExecutorService. Because without it, we cannot remove a task from the queue with "future.cancel(false)".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (WFLY-13537) Windows Service cannot be stopped when using custom JAVA_HOME path
by Walter Raaflaub (Jira)
[ https://issues.redhat.com/browse/WFLY-13537?page=com.atlassian.jira.plugi... ]
Walter Raaflaub updated WFLY-13537:
-----------------------------------
Description:
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.
was:
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 jboss-cli.bat script.
> Windows Service cannot be stopped when using custom JAVA_HOME path
> ------------------------------------------------------------------
>
> Key: WFLY-13537
> URL: https://issues.redhat.com/browse/WFLY-13537
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Reporter: Walter Raaflaub
> 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)
3 years, 11 months
[JBoss JIRA] (WFLY-13537) Windows Service cannot be stopped when using custom JAVA_HOME path
by Walter Raaflaub (Jira)
[ https://issues.redhat.com/browse/WFLY-13537?page=com.atlassian.jira.plugi... ]
Walter Raaflaub updated WFLY-13537:
-----------------------------------
Description:
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 jboss-cli.bat script.
was:
I am running Wildfly 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 jboss-cli.bat script.
> Windows Service cannot be stopped when using custom JAVA_HOME path
> ------------------------------------------------------------------
>
> Key: WFLY-13537
> URL: https://issues.redhat.com/browse/WFLY-13537
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Reporter: Walter Raaflaub
> 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 jboss-cli.bat script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (WFLY-13537) Windows Service cannot be stopped when using custom JAVA_HOME path
by Walter Raaflaub (Jira)
[ https://issues.redhat.com/browse/WFLY-13537?page=com.atlassian.jira.plugi... ]
Walter Raaflaub updated WFLY-13537:
-----------------------------------
Description:
I am running Wildfly 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}
(Drcken 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 jboss-cli.bat script.
was:
I am running Wildfly 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:
{{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 . . . }} (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 jboss-cli.bat script.
> Windows Service cannot be stopped when using custom JAVA_HOME path
> ------------------------------------------------------------------
>
> Key: WFLY-13537
> URL: https://issues.redhat.com/browse/WFLY-13537
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Reporter: Walter Raaflaub
> Priority: Major
>
> I am running Wildfly 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}
> (Drcken 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 jboss-cli.bat script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (WFLY-13537) Windows Service cannot be stopped when using custom JAVA_HOME path
by Walter Raaflaub (Jira)
[ https://issues.redhat.com/browse/WFLY-13537?page=com.atlassian.jira.plugi... ]
Walter Raaflaub updated WFLY-13537:
-----------------------------------
Description:
I am running Wildfly 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 jboss-cli.bat script.
was:
I am running Wildfly 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}
(Drcken 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 jboss-cli.bat script.
> Windows Service cannot be stopped when using custom JAVA_HOME path
> ------------------------------------------------------------------
>
> Key: WFLY-13537
> URL: https://issues.redhat.com/browse/WFLY-13537
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Reporter: Walter Raaflaub
> Priority: Major
>
> I am running Wildfly 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 jboss-cli.bat script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (WFLY-13537) Windows Service cannot be stopped when using custom JAVA_HOME path
by Walter Raaflaub (Jira)
[ https://issues.redhat.com/browse/WFLY-13537?page=com.atlassian.jira.plugi... ]
Walter Raaflaub updated WFLY-13537:
-----------------------------------
Steps to Reproduce:
Wildfly Windows service cannot be stopped
# install JDK to a custom path, e.g. {{D:\basedir\java\jdk11}}
# verify: no global JAVA_HOME environment variable
# install Wildfly
# set JAVA_HOME path in standalone.conf.bat (line 35): {{set "JAVA_HOME=D:\basedir\java\jdk11"}}
# register Wildfly as Windows service
# start Windows service
# stop Windows service
# verify contents of stoud.log:
{noformat}
2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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}
was:
Wildfly Windows service cannot be stopped
# install JDK to a custom path, e.g. D:\basedir\java\jdk11
# verify: no global JAVA_HOME environment variable
# install Wildfly
# set JAVA_HOME path in standalone.conf.bat (line 35): {{set "JAVA_HOME=D:\basedir\java\jdk11"}}
# register Wildfly as Windows service
# start Windows service
# stop Windows service
# verify contents of stoud.log:
{noformat}
2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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}
> Windows Service cannot be stopped when using custom JAVA_HOME path
> ------------------------------------------------------------------
>
> Key: WFLY-13537
> URL: https://issues.redhat.com/browse/WFLY-13537
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Reporter: Walter Raaflaub
> Priority: Major
>
> I am running Wildfly 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:
> {{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 . . . }} (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 jboss-cli.bat script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (WFLY-13537) Windows Service cannot be stopped when using custom JAVA_HOME path
by Walter Raaflaub (Jira)
[ https://issues.redhat.com/browse/WFLY-13537?page=com.atlassian.jira.plugi... ]
Walter Raaflaub updated WFLY-13537:
-----------------------------------
Steps to Reproduce:
Wildfly Windows service cannot be stopped
# install JDK to a custom path, e.g. D:\basedir\java\jdk11
# verify: no global JAVA_HOME environment variable
# install Wildfly
# set JAVA_HOME path in standalone.conf.bat (line 35): {{set "JAVA_HOME=D:\basedir\java\jdk11"}}
# register Wildfly as Windows service
# start Windows service
# stop Windows service
# verify contents of stoud.log:
{noformat}
2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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}
was:
Wildfly Windows service cannot be stopped
# install JDK to a custom path, e.g. D:\basedir\java\jdk11
# verify: no global JAVA_HOME environment variable
# install Wildfly
# set JAVA_HOME path in standalone.conf.bat (line 35): {{set "JAVA_HOME=D:\basedir\java\jdk11"}}
# register Wildfly as Windows service
# start Windows service
# stop Windows service
# verify contents of stoud.log:
{{2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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 . . .
}}
> Windows Service cannot be stopped when using custom JAVA_HOME path
> ------------------------------------------------------------------
>
> Key: WFLY-13537
> URL: https://issues.redhat.com/browse/WFLY-13537
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Reporter: Walter Raaflaub
> Priority: Major
>
> I am running Wildfly 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:
> {{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 . . . }} (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 jboss-cli.bat script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (WFLY-13537) Windows Service cannot be stopped when using custom JAVA_HOME path
by Walter Raaflaub (Jira)
[ https://issues.redhat.com/browse/WFLY-13537?page=com.atlassian.jira.plugi... ]
Walter Raaflaub updated WFLY-13537:
-----------------------------------
Steps to Reproduce:
Wildfly Windows service cannot be stopped
# install JDK to a custom path, e.g. D:\basedir\java\jdk11
# verify: no global JAVA_HOME environment variable
# install Wildfly
# set JAVA_HOME path in standalone.conf.bat (line 35): {{set "JAVA_HOME=D:\basedir\java\jdk11"}}
# register Wildfly as Windows service
# start Windows service
# stop Windows service
# verify contents of stoud.log:
{{
2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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 . . .
}}
was:
Wildfly Windows service cannot be stopped
# install JDK to a custom path, e.g. D:\basedir\java\jdk11
# verify: no global JAVA_HOME environment variable
# install Wildfly
# set JAVA_HOME path in standalone.conf.bat (line 35): {{set "JAVA_HOME=D:\basedir\java\jdk11"}}
# register Windows service
# start Windows service
# stop Windows service
# verify contents of stoud.log:
{{
2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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 . . .
}}
> Windows Service cannot be stopped when using custom JAVA_HOME path
> ------------------------------------------------------------------
>
> Key: WFLY-13537
> URL: https://issues.redhat.com/browse/WFLY-13537
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Reporter: Walter Raaflaub
> Priority: Major
>
> I am running Wildfly 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:
> {{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 . . . }} (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 jboss-cli.bat script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (WFLY-13537) Windows Service cannot be stopped when using custom JAVA_HOME path
by Walter Raaflaub (Jira)
[ https://issues.redhat.com/browse/WFLY-13537?page=com.atlassian.jira.plugi... ]
Walter Raaflaub updated WFLY-13537:
-----------------------------------
Steps to Reproduce:
Wildfly Windows service cannot be stopped
# install JDK to a custom path, e.g. D:\basedir\java\jdk11
# verify: no global JAVA_HOME environment variable
# install Wildfly
# set JAVA_HOME path in standalone.conf.bat (line 35): {{set "JAVA_HOME=D:\basedir\java\jdk11"}}
# register Wildfly as Windows service
# start Windows service
# stop Windows service
# verify contents of stoud.log:
{{2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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 . . .
}}
was:
Wildfly Windows service cannot be stopped
# install JDK to a custom path, e.g. D:\basedir\java\jdk11
# verify: no global JAVA_HOME environment variable
# install Wildfly
# set JAVA_HOME path in standalone.conf.bat (line 35): {{set "JAVA_HOME=D:\basedir\java\jdk11"}}
# register Wildfly as Windows service
# start Windows service
# stop Windows service
# verify contents of stoud.log:
{{
2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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 . . .
}}
> Windows Service cannot be stopped when using custom JAVA_HOME path
> ------------------------------------------------------------------
>
> Key: WFLY-13537
> URL: https://issues.redhat.com/browse/WFLY-13537
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Reporter: Walter Raaflaub
> Priority: Major
>
> I am running Wildfly 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:
> {{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 . . . }} (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 jboss-cli.bat script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (WFLY-13537) Windows Service cannot be stopped when using custom JAVA_HOME path
by Walter Raaflaub (Jira)
[ https://issues.redhat.com/browse/WFLY-13537?page=com.atlassian.jira.plugi... ]
Walter Raaflaub updated WFLY-13537:
-----------------------------------
Steps to Reproduce:
# install JDK to a custom path, e.g. D:\basedir\java\jdk11
# verify: no global JAVA_HOME environment variable
# install Wildfly
# set JAVA_HOME path in standalone.conf.bat (line 35): {{set "JAVA_HOME=D:\basedir\java\jdk11"}}
# register Windows service
# start Windows service
# stop Windows service
# verify contents of stoud.log:
{{
2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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 . . .
}}
was:
* install JDK to a custom path, e.g. D:\basedir\java\jdk11
* verify: no global JAVA_HOME environment variable
* install Wildfly
* set JAVA_HOME path in standalone.conf.bat (line 35):
{{set "JAVA_HOME=D:\basedir\java\jdk11"}}
* register Windows service
* start Windows service
* stop Windows service
* verify contents of stoud.log:
{{
2020-05-28 21:42:54 Commons Daemon procrun stdout initialized
Calling "D:\basedir\keycloak-10.0.1\bin\standalone.conf.bat"
Setting JAVA property to "D:\basedir\java\jdk11\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\basedir\keycloak-10.0.1"
JAVA: "D:\basedir\java\jdk11\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED"
===============================================================================
21:43:01,439 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
21:43:04,399 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
21:43:04,414 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
21:43:04,649 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) starting
...
21:43:24,646 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Keycloak 10.0.1 (WildFly Core 11.1.1.Final) started in 28567ms - Started 591 of 889 services (606 services are lazy, passive or on-demand)
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 . . .
}}
> Windows Service cannot be stopped when using custom JAVA_HOME path
> ------------------------------------------------------------------
>
> Key: WFLY-13537
> URL: https://issues.redhat.com/browse/WFLY-13537
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 11.0.0.Final
> Reporter: Walter Raaflaub
> Priority: Major
>
> I am running Wildfly 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:
> {{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 . . . }} (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 jboss-cli.bat script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months