Github user jbertram commented on the pull request:
https://github.com/apache/activemq-artemis/pull/245#issuecomment-159054551
The scenario you outline (X addresses with Y max-size-bytes and Z heap-size
that would require N addresses to go into paging mode before an OOME occurs) is
just one possible scenario.
The scenario I outlined previously is equally valid (1 address with Y
max-size-bytes and Y/2 heap-size) and no paging would be involved before an
OOME occurred so your suggested message wouldn't make sense.
As far as using getting scared of this WARN message when they have many
shallow destinations that never receive enough messages to reach max-size-bytes
I think they should be scared because their broker is in a vulnerable position.
If something goes wrong and they start getting increased message production
then they'll go OOME due to their sub-optimal configuration.
Whether or not it should be a WARN or an INFO is debatable, IMO. Being
vulnerable to an OOME if someone dumps a bunch of messages on the server seems
fairly serious to me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
