You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/03/01 21:23:00 UTC
[jira] [Commented] (ARTEMIS-1718) Do not programmatically set
"artemis.instance.etc" system property
[ https://issues.apache.org/jira/browse/ARTEMIS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382659#comment-16382659 ]
ASF subversion and git services commented on ARTEMIS-1718:
----------------------------------------------------------
Commit 25bb816652035d4cf8c436a5ed14db37294e47d9 in activemq-artemis's branch refs/heads/master from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=25bb816 ]
ARTEMIS-1718 don't set 'artemis.instance.etc' prop
> Do not programmatically set "artemis.instance.etc" system property
> ------------------------------------------------------------------
>
> Key: ARTEMIS-1718
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1718
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.5.0
>
>
> If the "artemis.instance.etc" system property is set programmatically it will break examples which create multiple brokers because when the "stop" command is run it won't find the right "etc" dir for the stop file which means brokers will potentially be left running. This isn't a problem when such an example is run by itself, but it is a problem when multiple examples are run at once (e.g. using {{mvn -Pexamples verify}} from the examples directory).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)