[
https://issues.apache.org/jira/browse/ARTEMIS-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-2404.
-------------------------------------
Resolution: Abandoned
> Crash if the size of scheduled messages at a particular delivery time is
> greater than queue max size
> ----------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2404
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2404
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.6.2
> Reporter: Dave Myron
> Priority: Critical
>
> In our use case, we need to schedule many messages for delivery at specific
> times of day (on occasion, 1-2 million messages will be scheduled for 8am the
> next day). We use paging. Our messages are 2-3KB in size. This leads to
> scheduled messages spread across several hundred page files (we use the
> default 10MB page size).
> At the scheduled delivery time, when getting the referenced messages, Artemis
> appears to naively attempt to read all the scheduled messages from the pages
> and, if there are enough messages, get itself into a situation where it runs
> out of memory.
> We're working on recreating the issue in a docker image (but will likely be
> unable to share it externally). We'll then be attempting to see if moving to
> 2.9.0 has any positive impact (though, looking at the code, it doesn't look
> like it will). In our usage, Artemis runs in a docker container and docker
> actually OOM killed the image (and then removed the image entirely, in its
> wisdom) – that was a very bad day. SMH…
> I see no other issues referencing this type of failure from depaging lots of
> scheduled deliveries. Are there suggestions on mitigating this kind of
> behavior?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
