[
https://issues.apache.org/jira/browse/ARTEMIS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457189#comment-16457189
]
ASF GitHub Bot commented on ARTEMIS-1836:
-----------------------------------------
GitHub user acemanace opened a pull request:
https://github.com/apache/activemq-artemis/pull/2051
ARTEMIS-1836 Bug with broker when running on Windows,
cannot find login.config
The Windows variable ARTEMIS_ETC_INSTANCE was not set correctly,
as it was used as ARTEMIS_INSTANCE_ETC. So the fix is to make sure
that the two match, and additionally they it was renamed to more
closely match the other variables naming convention. This was done
in two files; so when 'artemis create mybroker' is run on a Windows
machine, the broker is correctly configured with login.config.
Minor fix of changing use of single quotes to correct usage of
double quotes when declaring variable.
Issue: https://issues.apache.org/jira/browse/ARTEMIS-1836
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/acemanace/activemq-artemis master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2051.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2051
----
----
> Artemis broker for Windows does not set login.config path correctly
> -------------------------------------------------------------------
>
> Key: ARTEMIS-1836
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1836
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.5.0
> Reporter: Joaquin Nadal
> Priority: Minor
>
> On windows when creating a broker, the login.config file cannot be reached
> due to missing path.
> The issue can be replicated on a Windows machine by running _{{artemis create
> mybroker}}_, and trying to use that broker. An exception is printed to
> console saying file _/login.config_ cannot be found.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)