[
https://issues.apache.org/jira/browse/AMQ-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027291#comment-15027291
]
ASF subversion and git services commented on AMQ-5393:
------------------------------------------------------
Commit 29d943429cc0742eaef52095be73c27cc856c34b in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=29d9434 ]
https://issues.apache.org/jira/browse/AMQ-5393
Reverting commit because allowing 0 doesn't actually set the usage to
0 size. It ends up disabling the check all together which was the
opposite intention of the commit.
This reverts commit 3b658f8e1aa8c9170b8d414fe8cd05c6826b490a.
> Update disk based limits periodically
> -------------------------------------
>
> Key: AMQ-5393
> URL: https://issues.apache.org/jira/browse/AMQ-5393
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.10.0
> Reporter: Dejan Bosanac
> Assignee: Timothy Bish
> Fix For: 5.12.0
>
>
> At the moment, we set store and temp limits at broker startup based on the
> configuration and available space. It's possible that other artefacts such as
> logs can reduce available disk space so that our limits does not have effect.
> It'd be good to periodically check for the usable space left and adjust
> limits accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
