Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
2.11.0
-
None
-
None
-
PROD
Description
Hello Team,
Need your advise in case we can improve situation by making configuration changes:
We are observing frequent paging due to low consumption rate on certain occasion (which is business need to limitation on 3rd party system)
frequent paging is also triggering high GC and broker end up utilizing 95%+ heap memory.
We have LB --> 2 qpids --> 4 pair master/slave
Below is address setting which is common for all addresses.
And we have not defined global-max-size anywhere in broker.xml
<address-settings>
<!-- if you define auto-create on certain queues, management has to be auto-create -->
<address-setting match="activemq.management#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<!-- with -1 only the global-max-size is in use for limiting -->
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
</address-setting>