activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-336) Don't hard-code instance path
Date Tue, 12 Jan 2016 02:18:39 GMT


ASF GitHub Bot commented on ARTEMIS-336:

GitHub user jbertram opened a pull request:

    ARTEMIS-336 don't hard-code instance path


You can merge this pull request into a Git repository by running:

    $ git pull master_work

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #309
commit 96cb0913f3b738d98fc235c2268d9ec5d91f90ac
Author: jbertram <>
Date:   2016-01-12T02:16:33Z

    ARTEMIS-336 don't hard-code instance path


> Don't hard-code instance path
> -----------------------------
>                 Key: ARTEMIS-336
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>             Fix For: 1.3.0
> This was reported via the developer mailing list:
> Artemis uses only partially the ARTEMIS_INSTANCE environment variable and its associated
artemis.instance Java property.
> When creating a new instance with "artemis create mybroker":
> (1) etc/artemis.profile contains the expanded ARTEMIS_INSTANCE path hard-coded in the
JAVA_ARGS line, it should use $ARTEMIS_INSTANCE instead
> (2) etc/bootstrap.xml contains the expanded ARTEMIS_INSTANCE path hard-coded in the server's
configuration attribute, it should use ${artemis.instance} instead
> This way, it would be easier to relocate an Artemis instance.

This message was sent by Atlassian JIRA

View raw message