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 GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/21 12:45:27 UTC

[jira] [Commented] (ARTEMIS-273) Server moveData does not support relative paths

    [ https://issues.apache.org/jira/browse/ARTEMIS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966625#comment-14966625 ] 

ASF GitHub Bot commented on ARTEMIS-273:
----------------------------------------

GitHub user mtaylor opened a pull request:

    https://github.com/apache/activemq-artemis/pull/207

    ARTEMIS-273 Use data locations not dir in moveData

    

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

    $ git pull https://github.com/mtaylor/activemq-artemis ARTEMIS-273

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

    https://github.com/apache/activemq-artemis/pull/207.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 #207
    
----
commit 41e3fec3c2ceeb690076227cbd814ee11240b71c
Author: Martyn Taylor <mt...@redhat.com>
Date:   2015-10-20T14:43:03Z

    ARTEMIS-273 Use data locations not dir in moveData

----


> Server moveData does not support relative paths
> -----------------------------------------------
>
>                 Key: ARTEMIS-273
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-273
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.1.0
>            Reporter: Martyn Taylor
>
> The moveData method in ActiveMQServerImpl does not support relative paths.  This was causing problems when using failback with replication as journal logs were not getting moved causing duplicate entries.  This surfaced upstream when users tried runnign failback examples.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)