I dont know if this is exactly what is happening with you but the code
below shows that if the broker memory is full, the broker will be unable to
page in messages (and dispatch them).
https://www.paste.org/98451
If this is your case this issue somewhat mitigated by
https://issues.apache.org/jira
If you have properly configured your cluster then core bridges are
automatically created between the nodes behind-the-scenes. If you have 2
independent clusters and you want to connect them together then you would
need to manually configure core bridges.
For configuring core connections see the do
Hi...
Did you guys see some log lines like the following?
WARN Queue - queue://STORE, subscriptions=1,
memory=0%, size=200, pending=0 cursor blocked, no space available to page
in messages; usage: Usage(Main:memory:queue://STORE:memory)
percentUsage=0%, usage=0, limit=1
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 s
Hi,
Following is the stack trace for successful connection to activeMQ:
#
2019-04-30 20:51:52 DEBUG TaskRunnerFactory:91 - Initialized
TaskRunnerFactory[ActiveMQ Task] using ExecutorService:
java.util.concurrent.ThreadPoolExecutor@6504e3b2[Running, pool siz
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 <
christopher.l.
What version of ActiveMQ are you using?
That line is written when a consumer closes with unconsumed messages. Is
that occurring here? Your description of the consumer code sounds like
you're creating a consumer per message consumed (an anti-pattern), in which
case 1) unconsumed messages when closi
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