activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johno Crawford (JIRA)" <>
Subject [jira] [Commented] (AMQ-6940) Significant memory footprint increase from 5.8.0 to 5.15.3
Date Thu, 29 Mar 2018 11:12:00 GMT


Johno Crawford commented on AMQ-6940:

{quote}In flight messages by definition are messages that have not been processed but have
simply been dispatched to a consumer. Messages are not "processed" until a consumer acknowledges
the message so the broker does not drop a message until then.{quote}

So based on your definition shouldn't updateStatsOnAck be invoked in here? (just a shot in
the dark haven't had time to test it)

} else if (ack.isDeliveredAck()) {
    // Message was delivered but not acknowledged: update pre-fetch counters.
    // missing call to updateStatsOnAck?
} else if (ack.isRedeliveredAck()) {

> Significant memory footprint increase from 5.8.0 to 5.15.3
> ----------------------------------------------------------
>                 Key: AMQ-6940
>                 URL:
>             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
>         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

View raw message