[jboss-jira] [JBoss JIRA] (WFLY-5645) Use script name for file related to Wildfly to allow multiple instances easily
RH Bugzilla Integration (JIRA)
issues at jboss.org
Fri Nov 6 08:36:00 EST 2015
[ https://issues.jboss.org/browse/WFLY-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
RH Bugzilla Integration updated WFLY-5645:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1265740
> Use script name for file related to Wildfly to allow multiple instances easily
> ------------------------------------------------------------------------------
>
> Key: WFLY-5645
> URL: https://issues.jboss.org/browse/WFLY-5645
> Project: WildFly
> Issue Type: Enhancement
> Components: Scripts
> Affects Versions: 10.0.0.CR4
> Reporter: Romain Pelisse
> Assignee: Tomaz Cerar
> Priority: Optional
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> 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:
> {code:bash}
> # 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
> {code}
> And to take the example of the PIDFILE:
> {code:bash}
> JBOSS_PIDFILE=/var/run/$(basename $0)/jboss-as-domain.pid
> {code}
> 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
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list