]
Eduardo Silva commented on WFLY-5366:
-------------------------------------
The JBOSS_MARKERFILE variable can be defined, on your shell script. for instance:
JBOSS_MARKERFILE=$JBOSS_HOME/standalone/tmp/startup-marker
Take a look at:
wildfly-VERSION/docs/contrib/scripts/init.d/wildfly-init-redhat.sh
Startup success detection mechanism fails if JBOSS_HOME and
jboss.server.base.dir are set differently.
------------------------------------------------------------------------------------------------------
Key: WFLY-5366
URL:
https://issues.jboss.org/browse/WFLY-5366
Project: WildFly
Issue Type: Bug
Components: Scripts
Affects Versions: 10.0.0.CR1
Environment: Linux/Debian
Reporter: Thorsten Moeller
Fix For: Awaiting Volunteers
If the property `jboss.server.base.dir` and the environment variable `JBOSS_HOME` point
to different directories (which we do, for instance, to start multiple JBoss/Wildfly
instances, each with its own standalone directory) then the startup success detection
mechanism implemented by the script <WILDFLY_HOME>/bin/init.d/wildfly-init-debian.sh
wrongly reports startup as failed even if it actually succeeded.
Tracing it down, I found that since Wildly 10 the startup script searches for the file
`<JBOSS_HOME>/standalone/tmp/startup-marker`. However, that file is actually written
to `jboss.server.base.dir/tmp/startup-marker`; hence, it is not found if the directories
are not the same.
I don't see a way how to fix this. As far as I can seen, it's not possible to
access the jboss.server.base.dir property within the startup script. But the use case of
having separate directories should be supported and it should work.