[jboss-jira] [JBoss JIRA] (WFLY-10326) Add setting to control global disk usage for messaging journal

[Jeff Mesnil (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil moved EAP7-995 to WFLY-10326:
-----------------------------------------

                      Project: WildFly  (was: EAP 7 Planning Pilot)
                          Key: WFLY-10326  (was: EAP7-995)
                   Issue Type: Feature Request  (was: Requirement)
                     Workflow: GIT Pull Request workflow   (was: EAP Agile Workflow 2.0)
                  Component/s: JMS
                                   (was: JMS)
               Target Release:   (was: 7.2.0.GA)
    Release Notes Docs Status:   (was: Documented as Feature Request)


> Add setting to control global disk usage for messaging journal
> --------------------------------------------------------------
>
>                 Key: WFLY-10326
>                 URL: https://issues.jboss.org/browse/WFLY-10326
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: JMS
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>              Labels: Previous_RFE
>
> Please see https://issues.apache.org/jira/browse/ARTEMIS-581
> Artemis defines given max amount of memory for each queue (max-size-bytes). If this amount if reached then one of the defined policies BLOCK, PAGE, FAIL or DROP is applied to newly incoming messages. 
> Problem is that with 400 queues and max-size-bytes=10MB, this would require 4 GB of heap memory to avoid OutOfMemoryError and crash of EAP 7 server. Thus new attribute global-max-size should be added to limit how much memory Artemis queues can consume before applying policies BLOCK, PAGE, FAIL or DROP.
> There is also no check how much disk space Artemis journal is consuming. Which should be limited.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)