Thank you for the answer, Justin.
I'm using another Artemis instance with a bridge sending data to this one.
I've seen Artemis enforcing this limit when using Java clients and writing the
corresponding entry in the log file. We sometimes get a log indicating that the
limit is reached:
2021-11-18 15:41:49,529 WARN [org.apache.activemq.artemis.core.server]
AMQ222183: Blocking message production on address 'events.inject'; size is
currently: 56,183,147 bytes; max-size-bytes on address: 52,428,800,
global-max-size is 56,183,147
But the queue still grows regardless of the message:
$ date; /opt/facilities/artemis/conf/broker/bin/artemis queue stat|head -2; for
I in 1 2; do /opt/facilities/artemis/conf/broker/bin/artemis queue stat|grep
events.inject|grep -v relay; sleep 5; done
Thu 18 Nov 15:45:54 UTC 2021
Connection brokerURL = tcp://localhost:61616
|NAME |ADDRESS |CONSUMER_COUNT
|MESSAGE_COUNT |MESSAGES_ADDED |DELIVERING_COUNT |MESSAGES_ACKED
|SCHEDULED_COUNT |ROUTING_TYPE |
|events.inject |events.inject |0 |447121
|447121 |0 |0 |0 |ANYCAST
|
|events.inject |events.inject |0 |457246
|457246 |0 |0 |0 |ANYCAST
|
