You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2021/09/27 23:12:00 UTC

[jira] [Closed] (AMQ-7510) Message caching behavior not consistent

     [ https://issues.apache.org/jira/browse/AMQ-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Pavlovich closed AMQ-7510.
-------------------------------
    Resolution: Abandoned

> Message caching behavior not consistent
> ---------------------------------------
>
>                 Key: AMQ-7510
>                 URL: https://issues.apache.org/jira/browse/AMQ-7510
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Vasa
>            Assignee: Matt Pavlovich
>            Priority: Major
>              Labels: close-pending
>
> tl;dr: Broker memory usage not consistent after reboots
> Steps to reproduce the issue:
>  * Created a broker (Both on a personal instance as well as with AmazonMQ)
>  * Started producing messages directly to one or more destination queues without any consumers polling the queue
>  * All messages were sent to the broker with persistent mode
>  * As messages are sent to the queue, the memory % rise as seen from the ActiveMQ console. It can go all the way up to 99% after which it starts rejecting messages
>  * Once the broker is rebooted, the memory percent goes down to 0 even when the queue still has all the messages.
>  * When continuing to send additional messages, the memory percent does not go up
>  
> It almost seems like caching led to memory % rise until broker reboot. After reboot, caching of messages was not active and memory % stayed down



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