[
https://issues.apache.org/jira/browse/ARTEMIS-4702?focusedWorklogId=914479&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914479
]
ASF GitHub Bot logged work on ARTEMIS-4702:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Apr/24 21:42
Start Date: 12/Apr/24 21:42
Worklog Time Spent: 10m
Work Description: jbertram opened a new pull request, #4885:
URL: https://github.com/apache/activemq-artemis/pull/4885
(no comment)
Issue Time Tracking
-------------------
Worklog Id: (was: 914479)
Remaining Estimate: 0h
Time Spent: 10m
> Only run command needs custom JVM settings
> ------------------------------------------
>
> Key: ARTEMIS-4702
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4702
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now every {{artemis}} command uses the same JVM settings from
> {{artemis.profile}}. So, for example, if the settings included {{-Xms8G
> -Xmx8G}} for running the broker (i.e. the {{run}} command) those same
> settings would be used for the {{queue stat}}, {{consumer}}, {{producer}},
> etc. commands as well. At best, it's overkill to use 8G of memory for these
> secondary commands and at worst it can actually prevent them from operating
> at all (e.g. if the machine is low on memory).
> JVM settings really only need to apply to the {{run}} command.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
