[ 
https://issues.apache.org/jira/browse/ARTEMIS-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317970#comment-17317970
 ] 

Clebert Suconic commented on ARTEMIS-3231:
------------------------------------------

This qualifies it as an user question.. not as a bug...

 

 

you should use the user's list for questions: 
[https://activemq.apache.org/contact]

 

 

JIRAs are for bugs and enhancements.. I don't see anything like that in your 
Jira here.

 

Please, ask the same question on the user's list.. and I will look for it over 
there.

 

 

if you have for some reason a confirmed bug, we can always come back here.

 

 

 

I would recommend you always trying the latest version also.. specially on the 
paging case as we have done a few changes in a few releases.

> Artemis paging | high GC | need configuration advise
> ----------------------------------------------------
>
>                 Key: ARTEMIS-3231
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3231
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: ActiveMQ-Artemis-Native, AMQP
>    Affects Versions: 2.11.0
>         Environment: PROD
>            Reporter: mahendra anil sonawale
>            Assignee: Clebert Suconic
>            Priority: Major
>
> 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>



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to