-
Enhancement
-
Resolution: Done
-
Optional
-
2.0.1.Final
-
None
With the current provided init.d script, one cannot start several instances of Wildfly. Indeed, the script will associate the same files (pid file, log) to both instance. If we rename those files using, for instance, the name of the script we can easily use the exact same script for all local instances:
# ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-1 # ln -s ..../init.d/wildfly-initd-redhat.sh /etc/init.d/wildfly-2
And to take the example of the PIDFILE:
JBOSS_PIDFILE=/var/run/$(basename $0)/jboss-as-domain.pid
Each links will then look up and creates its own separate file:
/var/run/wildfly-1/jboss-as-domain.pid
/var/run/wildfly-2/jboss-as-domain.pid
- is cloned by
-
JBEAP-3444 (7.0.z) Use script name for file related to Wildfly to allow multiple instances easily
- Verified
-
WFCORE-1391 Use script name for file related to Wildfly to allow multiple instances easily
- Closed
- is related to
-
WFCORE-1615 Make wildfly-init-redhat.sh consistent with wildfly-init-debian.sh
- Resolved
- relates to
-
JBEAP-763 EAP_HOME/bin/init.d folder is not productized
- Closed