As an ActiveMQ developer, I think the best reference (if you can call it
that) is the test-suite itself. If I'm curious about a configuration method
then I usually just do a search for where/how it's used in the test-suite.
Past that I look at the artemis-configuration.xsd since just about every
pr
Newcomer here looking for documentation, examples or tests describing how
to programmatically configure Artemis.
There are tons of examples on how to configure Artemis using XML, JMS and
JNDI but very few describing how to use
org.apache.activemq.artemis.core.config.Configuration. Take the
configu
JVisualVM's CPU sampler, which attaches to the JVM via the JMX port (open
by default in ActiveMQ), would be my recommended way to do the profiling
(sampling, in this case) that Chris mentioned.
Tim
Tim
On Tue, Feb 19, 2019, 4:39 AM Christopher Shannon <
christopher.l.shan...@gmail.com wrote:
>
The authorization plugin has to do a lot of processing as it is tracking
and checking ACLs for all of your topics (which is a ton) for every message
going through the broker and is going to eat up a lot of CPU. Your best bet
is to try and isolate which part is causing high cpu usage using a profile
