Those two (profiler capture, or thread dump) should also be smaller and you
might be able to attach them directly. If not, just use one of the free
file-posting sites if you don't want to use your own Dropbox or Google
Drive or similar.
Tim
On Thu, May 2, 2019, 7:28 AM Tim Bain wrote:
> A CPU
A CPU sampling capture from a profiler such as JVisualVM will be far more
effective than a thread dump, if it's an option.
A heap dump will probably not be useful here, since it doesn't sound like
you're running out of memory.
Tim
On Thu, May 2, 2019, 4:39 AM Christopher Shannon <
20k messages and 30k topics is quite a bit so I'm not surprised the CPU
usage is very high. The reason the CPU is high after stopping the
publishing is probably because you have a backlog on the broker that the
consumers need to work off. You might also have a lot of messages being
processed for
No problem, I can provide heap dump but the file size is over 1GB. Please
provide location /link to upload, thanks.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Can you provide any dump file:
Just like threaddump or heapdump?
-
Personal Email
-邮件原件-
发件人: Franco Ng
发送时间: 2019年5月2日 9:51
收件人: users@activemq.apache.org
主题: ActiveMQ cannot handle too many topic with redeliveryPlugin
Our market data would publish over 20,000 msg/s
Our market data would publish over 20,000 msg/s within 30,000 topics,
redeliveryPlugin and socketBufferSize, however, ActiveMQ seems unable to
handle this volume that CPU usage % is 50% and cannot publish any message to
subscriber(s) after certain starting time. Even, I stop the market data
