activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6940) Significant memory footprint increase from 5.8.0 to 5.15.3
Date Thu, 29 Mar 2018 13:03:00 GMT

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

ASF subversion and git services commented on AMQ-6940:
------------------------------------------------------

Commit f69fd6f0020290752a7424479821c22d94f9b8b7 in activemq's branch refs/heads/master from
[~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=f69fd6f ]

AMQ-6940 - Reduce memory footprint for inflight statistics

For the TopicSubscription case we can reduce the inflight statistics
memory footprint by not storing the entire message reference for in
flight messages and instead just a subset of the information needed.


> 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
>            Priority: Major
>             Fix For: 5.16.0, 5.15.4
>
>         Attachments: activemq.xml, 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