[
https://issues.apache.org/jira/browse/ARTEMIS-5741?focusedWorklogId=990385&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-990385
]
ASF GitHub Bot logged work on ARTEMIS-5741:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Nov/25 10:19
Start Date: 05/Nov/25 10:19
Worklog Time Spent: 10m
Work Description: gtully merged PR #6025:
URL: https://github.com/apache/activemq-artemis/pull/6025
Issue Time Tracking
-------------------
Worklog Id: (was: 990385)
Time Spent: 40m (was: 0.5h)
> webcomponent won't stop on shutdown/scaledown
> ---------------------------------------------
>
> Key: ARTEMIS-5741
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5741
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 2.44.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.45.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The scaledown jmx operation stops the broker when complete, but the jvm won't
> terminate because the web console and web component don't stop.
> ARTEMIS-915 introduced this behaviour by default, but the not shutdown
> behaviour should be conditional on being a backup, or some sub set of
> activation. Not sure how this should be wired together.
> calling stop, should shutdown IMHO
> There is a nice comment to this effect on the ARTEMIS-915 issue
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
