-
Feature Request
-
Resolution: Done
-
Major
-
None
-
Documentation (Ref Guide, User Guide, etc.), Release Notes
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.
- blocks
-
WFLY-2443 JMS service shutsdown and doesn't recover after disk fills up.
- Closed