[
https://issues.apache.org/jira/browse/ARTEMIS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763966#comment-16763966
]
ASF subversion and git services commented on ARTEMIS-2246:
----------------------------------------------------------
Commit 8edca409f6d0e3fa1a509b4d376a11022e8712ff in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=8edca40 ]
ARTEMIS-2246 Fixing testsuite
> Documentation for configuration max-disk-usage is inaccurate.
> -------------------------------------------------------------
>
> Key: ARTEMIS-2246
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2246
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.6.4
> Reporter: Leo Provido
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.7.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> During the execution of tests involving sending messages to the System, we
> observed that the System started blocking messages before the disk is full.
> According to the Configuration Reference
> ([https://activemq.apache.org/artemis/docs/1.4.0/configuration-index.html])
> documentation, the default value of the configuration max-disk-usage is 100.
> However, we discovered that the actual default value of max-disk-usage is 90.
> The file inspected is ./etc/broker.xml. Thus, the documentation is deemed
> inaccurate.
> We have the opinion that severity of this incident is Major because a) the
> documentation provides an inaccurate piece of information that influences the
> way we design our mitigation strategies for risks surrounding hardware
> resources utilization, and b) we don’t necessarily have the bandwidth to
> review all default configuration values.
> Inaccurate information may cause failure to provide message brokering
> services despite mitigation strategies being in place.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
