activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-914) Max saved replicated journal size on Live node should not be -1
Date Wed, 11 Jan 2017 17:49:48 GMT


ASF GitHub Bot commented on ARTEMIS-914:

GitHub user jbertram opened a pull request:

    ARTEMIS-914 use defaults for ReplicaPolicy


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

    $ git pull master_work

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #957
commit 5da9a71c611ebe62a131188a3f1838b0ac10ff19
Author: Justin Bertram <>
Date:   2017-01-11T17:40:13Z

    ARTEMIS-914 use defaults for ReplicaPolicy


> Max saved replicated journal size on Live node should not be -1
> ---------------------------------------------------------------
>                 Key: ARTEMIS-914
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.5.1
>            Reporter: Erich Duda
>            Assignee: Justin Bertram
> The max-saved-replicated-journal-size on Live node is {{-1}} what can lead to fill the
disk by old replicas. The value is hard coded in Artemis code and cannot be changed. I think
the default value should be some small number, e.g. 2.
> I hit this issue with Wildfly. There are plans to update Artemis in Wildfly to 1.5.2
version. It would be great if the fix was included in 1.5.2 release. Thanks :)

This message was sent by Atlassian JIRA

View raw message