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
I set authorizationPlugin plugin as belolw, assign "user" can create &
publish any queues and topics. When I publish 2,000 message/sec with 60,000
wildcard topics (E.g. stock.01), whole ActiveMQ server performance is
down, CPU usage eat up to 50% and too many topic JMS messages are pending in
Can you provide any details from your root-cause analysis that shed light
onto the specific problem and how it might be solved?
ActiveMQ is a community project, and I personally trust that all community
members are working in good faith to help improve it. I'm not sure I'd say
there is a special "
Sorry, I isolated the problem the root cause is *authorizationPlugin *not
simpleAuthenticationPlugin
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
This is bad solution.
I figured out that if implemented simpleAuthenticationPlugin for security
control, it will cause this problem even standalone ActiveMQ.
If removed simpleAuthenticationPlugin from activemq.xml, the problem is
solved.
simpleAuthenticationPlugin is root cause, ActiveMQ Develop
If that plugin doesn't do exactly what you want, it's possible to write a
custom plugin that's more tuned for your use case. See
http://activemq.apache.org/interceptors.html for more information.
Tim
On Mon, Feb 18, 2019, 3:11 AM Franco Ng I found the cause is that add simpleAuthenticationPlugin
I found the cause is that add simpleAuthenticationPlugin to control security,
the the B Broker connect to A Broker with login (define in
"networkConnector"). If large no. of topic message sent, it would slow than
whole ActiveMQ server.
Anyone can help to solve this, thanks.
userName="system"
p
I use ActiveMQ as market data distribution and would create over 60,000
wildcard topics (e.g. stock.01) and send 2,000 message/sec. However,
ActiveMQ server CANNOT handle this kind of volume and consumer would receive
delay message (over 3 mins delay). When I stop message generator, the
Activ
