activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-6940) Significant memory footprint increase from 5.8.0 to 5.15.3
Date Thu, 29 Mar 2018 17:28:00 GMT

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

Christopher L. Shannon edited comment on AMQ-6940 at 3/29/18 5:27 PM:
----------------------------------------------------------------------

There's a new flag on a policy that you can set called useTopicSubscriptionInflightStats. 
It defaults to true but if you set it to false then it will not store those objects in the
dispatched list and skip that metric.


was (Author: christopher.l.shannon):
There's a new flag on a policy that you can set called useTopicSubscriptionInflightStats. 
It defaults to true but if you set it to false then it will now store those objects in the
dispatched list and skip that metric.

> Significant memory footprint increase from 5.8.0 to 5.15.3
> ----------------------------------------------------------
>
>                 Key: AMQ-6940
>                 URL: https://issues.apache.org/jira/browse/AMQ-6940
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.15.3
>         Environment: Java jdk1.8.0_144
> OS Linux 4.4.19-29.55.amzn1.x86_64
>            Reporter: Johno Crawford
>            Assignee: Christopher L. Shannon
>            Priority: Major
>             Fix For: 5.16.0, 5.15.4
>
>         Attachments: activemq.xml, amq-testing.tar.xz, amq_5.16.0-SNAPSHOT.png, amq_5.8.0.png,
amq_heap2.png, messageid_analysis.png
>
>
> Recently we upgraded from 5.8.0 to 5.15.3 on one of our environments and found the broker
running out of memory with the old broker configurations.
> I suspect this may be related to the new inflight message size calculation but haven't
been able to create a reproducer just yet.
> Broker JVM running with opts 
> {code:java}
> -Xss256k -Xms600m -Xmx600m -Xmn128m -Dfile.encoding=ISO-8859-1 -Dlog4j.watchDelay=60000
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -XX:+PrintPromotionFailure
-XX:PrintFLSStatistics=1 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+PrintClassHistogram
-verbose:gc -Dsun.rmi.dgc.client.gcInterval=7200000 -Dsun.rmi.dgc.server.gcInterval=7200000
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message