activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARTEMIS-336) Don't hard-code instance path
Date Wed, 13 Jan 2016 19:24:39 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Justin Bertram resolved ARTEMIS-336.
------------------------------------
    Resolution: Fixed

> Don't hard-code instance path
> -----------------------------
>
>                 Key: ARTEMIS-336
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-336
>             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: http://activemq.2283324.n4.nabble.com/Artemis-incomplete-use-of-ARTEMIS-INSTANCE-td4705750.html
> 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
(v6.3.4#6332)

Mime
View raw message