[jboss-jira] [JBoss JIRA] (WFLY-5366) Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently.

[Thorsten Moeller (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thorsten Moeller updated WFLY-5366:
-----------------------------------
    Fix Version/s: 10.0.0.Final


> 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
>            Assignee: Tomaz Cerar
>            Priority: Critical
>             Fix For: 10.0.0.Final
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)