> 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 thi
> 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 t
Hi,
On Mon, Apr 22, 2024 at 6:46 PM Justin Bertram wrote:
> This was caused by ARTEMIS-4582 [1]. I've opened ARTEMIS-4742 [2] and
> sent a PR [3] to address the problem.
Thanks Justin.
On Tuesday, April 23, 2024 3:27 PM Stephen Baker
wrote:
> Can you clarify what condition triggers this (i.
On Mon, Apr 22, 2024 at 6:46 PM Justin Bertram 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 conf
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.
Justin
[1] https://issues.apache.org/jira/br
Hi All,
We have faced problem when upgrading one of ActiveMQ Artemis servers from
2.32.0 to 2.33.0.
Artemis cannot start and writes an error to the log:
2024-04-18 13:31:44,975 ERROR [org.apache.activemq.artemis.core.server]
AMQ224000: Failure in initialisation
java.lang.IndexOutOfBoundsExcepti
