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

Clebert Suconic commented on ARTEMIS-5016:
------------------------------------------

Without a reproducer to the issue you are seeing there's no way we can help you.

Most likely your are not consuming messages... or you are not configuring 
paging accordingly.

With such a wide scope your question falls on the scope of a consulting job 
where someone would need to gather more information.

If you want us to take a look you will need to provide a reproducer to the 
issue you are seeing. Such a generic question is impossible to be addressed.

> Memory not getting released
> ---------------------------
>
>                 Key: ARTEMIS-5016
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5016
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.32.0, 2.35.0
>            Reporter: Raghurama laxmikishore vedula
>            Assignee: Clebert Suconic
>            Priority: Major
>         Attachments: broker.xml
>
>
> It seems the Memory usage of artemis active mq cluster is always growing up 
> but memory is not getting freed even there is no load on the broker due to 
> this we have to restart container to free the memory else we get OOM issues 
> and resulted to container restarts.
> we are suspecting a memory leak or any configurations that need to adjusted 
> Config details:
> Container memory : 4 GB
> CPU : 2000m
> JVM Min and Max : 2GB
> Additional JVM ops: "-XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=300m 
> -XX:ReservedCodeCacheSize=256m -XX:NewRatio=2 -Xss256k 
> -XX:MaxDirectMemorySize=200m"



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to