[jboss-jira] [JBoss JIRA] (WFCORE-1121) Use script name for file related to Wildfly to allow multiple instances easily

Brian Stansberry (JIRA) issues at jboss.org
Fri May 20 14:11:01 EDT 2016


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

Brian Stansberry updated WFCORE-1121:
-------------------------------------
    Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1225  (was: https://github.com/jbossas/jboss-eap/pull/2625)


> Use script name for file related to Wildfly to allow multiple instances easily
> ------------------------------------------------------------------------------
>
>                 Key: WFCORE-1121
>                 URL: https://issues.jboss.org/browse/WFCORE-1121
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Scripts
>    Affects Versions: 2.0.1.Final
>            Reporter: Romain Pelisse
>            Assignee: Romain Pelisse
>            Priority: Optional
>             Fix For: 2.2.0.CR1, 3.0.0.Alpha1
>
>   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