[jboss-jira] [JBoss JIRA] (WFCORE-1383) Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently.
Lin Gao (JIRA)
issues at jboss.org
Wed Jan 3 03:43:00 EST 2018
[ https://issues.jboss.org/browse/WFCORE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Gao reassigned WFCORE-1383:
-------------------------------
Assignee: Lin Gao
> Startup success detection mechanism fails if JBOSS_HOME and jboss.server.base.dir are set differently.
> ------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1383
> URL: https://issues.jboss.org/browse/WFCORE-1383
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.0.0.CR1
> Environment: Linux/Debian
> Reporter: Thorsten Moeller
> Assignee: Lin Gao
>
> 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
(v7.5.0#75005)
More information about the jboss-jira
mailing list