> It could be great to have some API method to export all persisted security settings.
It's not part of the management API, per se, but the "data print" command will print all the entries from the bindings journal - included PersistedSecuritySetting records. The simplest way to do this is with this command while the broker is stopped: ./artemis data print --skip-journal Justin On Tue, Apr 23, 2024 at 11:04 AM Justin Bertram <jbert...@apache.org> wrote: > > Can you clarify what condition triggers this...? > > Security settings are persisted to the bindings journal when they are > added via the management API (e.g. via addSecuritySettings on the > ActiveMQServerControl MBean). If this was done before upgrading to 2.33.0 > then the broker will fail to decode these settings after the upgrade. > > > Justin > > On Tue, Apr 23, 2024 at 7:27 AM Stephen Baker > <stephen.ba...@motorolasolutions.com.invalid> wrote: > >> On Mon, Apr 22, 2024 at 6:46 PM Justin Bertram <jbert...@apache.org> >> wrote: >> >> > This was caused by ARTEMIS-4582 [1]. I've opened ARTEMIS-4742 [2] and >> sent >> > a PR [3] to address the problem. >> > >> > To be clear, this has nothing to do with replication or load/throughput. >> > It's just a buffer formatting issue caused by a configuration change. >> > >> >> Can you clarify what condition triggers this (i.e. when would there be a >> peristable security setting with an empty write or view buffer)? >> >> -- >> >> >> *For more information on how and why we collect your personal >> information, please visit our Privacy Policy >> < >> https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement >> >.* >> >
