You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy A. Bish (Jira)" <ji...@apache.org> on 2025/11/19 14:35:00 UTC

[jira] [Resolved] (ARTEMIS-5763) reload config on primary activation after lock acquisition

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

Timothy A. Bish resolved ARTEMIS-5763.
--------------------------------------
    Resolution: Fixed

> reload config on primary activation after lock acquisition
> ----------------------------------------------------------
>
>                 Key: ARTEMIS-5763
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5763
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 2.44.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.45.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> If a broker is waiting for an activation shared lock, and configuration is updated while waiting, the files are not reloaded on start.
> the lastmodified is calculated on activation, but the config has been loaded on initial startup so it can be stale.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact