I tried to reproduce this using a fresh instance of 2.40.0 with 2,500
queues defined in broker.xml (thanks to a bash script), but the console
loaded in just a few seconds.
I then created a fresh instance of 2.39.0 with 2,500 queues defined in
broker.xml. Then I ran "artemis data exp" to export the
You may need to add to your etc/jolokia-access.xml. A PR
[1] recently updated the upgrade documentation [2].
Justin
[1] https://github.com/apache/activemq-artemis/pull/5612
[2]
https://activemq.apache.org/components/artemis/documentation/latest/versions.html#upgrading-from-2-39-0
On Mon, Apr 7
> I'm wondering what is the performance penalty of having
auto-delete-queues/auto-delete-addresses enabled on a broker with tens of
thousands of queues versus using temporary queues?
Predicting performance is tricky given all the variables, but just looking
only at the relative "cost" of using a t
Hi All,
Has anyone installed ActiveMQ Artemis 2.40.0 in an environment with a
significant number of addresses and queues?
I have several problems with performance of the new Artemis console and
message broker. I have installed Artemis 2.40.0 and imported data from a
file which was exported from th
> When I connect using the Ingress route URL, I get the blank screen, but
authentication is still fine.
This sounds like a problem with your etc/jolokia-access.xml configuration.
How is it configured? If the problem was related to the HAWTIO_ROLES
configuration I don't think it would work in any c
Greetings.
Im upgrading to 2.40.0 - and have read the minor changes that are needed for
the upgrade (in this case HAWTIO_ROLE > ROLES), the instance itself works fine.
I’ve deployed in an environment to test and I’m not receiving the correct role
when using an external URL. The interface is
