[
https://issues.apache.org/jira/browse/ARTEMIS-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699315#comment-16699315
]
Justin Bertram commented on ARTEMIS-2180:
-----------------------------------------
I've tried to reproduce this, but was not successful. Here's what I did:
* Using Artemis 2.6.3 I made a copy of the "replicated-transaction-failover"
example to have a simple starting point for a replicated live/backup pair.
* Started the live & backup individually (i.e. not as part of running the
example).
* Started a multi-threaded consumer: {{./artemis consumer --threads 30
--message-count 100000}}
* Started a multi-threaded producer: {{./artemis producer --threads 30
--message-count 100000}}
* Stopped the backup about 1/4 of the way through the run of 100,000 messages.
* Monitored heap utilization on the live broker using JConsole.
I didn't see anything out of the ordinary.
> Host and broker runs out of memory when stopping a backup in a cluster
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-2180
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2180
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.6.3
> Reporter: Simon Chalmers
> Priority: Critical
> Attachments: hs_err_pid15534.log
>
>
> When running a live-backup cluster pair and stopping the backup, the live
> broker starts leaking memory, runs out of memory and core dumps.
> This occurs during a performance test when the broker is under load; the
> slave has been running successfully but is then terminated whilst the broker
> is still under load.
> Core dump attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
