[
https://issues.apache.org/jira/browse/ARTEMIS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389130#comment-16389130
]
Lionel Cons commented on ARTEMIS-528:
-------------------------------------
We are considering moving from ActiveMQ 5.x to Artemis and we would like to
reuse as much as possible as the current infrastructure we use to manage our
brokers.
If the path of the {{cli.lock}} file can be customized then it will be enough
for us to change this path.
Otherwise, more work will be needed on our side to adapt our management code.
> The "lock" directory should be configurable
> -------------------------------------------
>
> Key: ARTEMIS-528
> URL: https://issues.apache.org/jira/browse/ARTEMIS-528
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Lionel Cons
> Assignee: Justin Bertram
> Priority: Major
>
> Artemis allows the broker owner to change most of the paths used, see for
> instance the "*-directory" elements like "paging-directory". There is one
> major exception though.
> The directory holding the {{cli.lock}} file is currently hard-coded in
> {{artemis-cli/src/main/java/org/apache/activemq/artemis/cli/commands/Configurable.java}}
> (sic):
> {code}
> protected File getLockPlace() throws Exception {
> String brokerInstance = getBrokerInstance();
> if (brokerInstance != null) {
> return new File(new File(brokerInstance),"lock");
> }
> else {
> return null;
> }
> }
> {code}
> Could you please allow changing the name of this directory?
> Ideally, it could appear like the other "*-directory" elements in
> {{broker.xml}}. If this is too late, it could come from a Java property such
> as {{artemis.lockdir}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
