You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/10/13 17:24:00 UTC

[jira] [Commented] (ARTEMIS-4028) properties config - provide checksum read status for properties

    [ https://issues.apache.org/jira/browse/ARTEMIS-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617209#comment-17617209 ] 

ASF subversion and git services commented on ARTEMIS-4028:
----------------------------------------------------------

Commit 3b981b3920dc2214e943d9de81bd991fb7182eb6 in activemq-artemis's branch refs/heads/main from Gary Tully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=3b981b3920 ]

ARTEMIS-4028 - add alder32 checksum to the status of properties files read by the broker


> properties config - provide checksum read status for properties
> ---------------------------------------------------------------
>
>                 Key: ARTEMIS-4028
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4028
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 2.26.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 2.27.0
>
>
> When properties are first applied or updated, seeing the checksum of the applied content allows verification that the application has completed.
> On reload/reapply, where there is a period before the broker detects the need to update, the status can provide a mechanism to verify when changes have been applied.
> To this end, I will add an alder32 checksum field to the properties status and apply the same pattern to the re-loadable properties from the jaas login modules.



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