Hi
We using activemq5.10.0 in our prod env, yesterday we found a WARN log,
about"Cannot remove a consumer that had not been registered". Please, what's
reason?
Any guidance or assistance is appreciated. Thank you.
2014-12-30 13:24:39,511 | INFO | Apache ActiveMQ 5.10.0 (ROOTNET_AMQ_5.10.
Hello ActiveMQ community:
TL;DR: I now think this is really a mis-configuration on our part but it took
quite a lot of digging before we nailed the issue, I am reporting this to save
others time in the future.
We are running a "store and forward network of brokers" where each broker is
connect
Your broker was up for a long time; theirs dies immediately. You're using
tightEncoding=true; they have it set to false. Your problem and theirs are
not related.
Increasing the JVM's Xmx should help, but do you know if 2GB is enough for
your expected broker load? I'd encourage you to spend the
That sounds like a plausible explanation of why you DLQ filled in that
situation. The more interesting question is what caused the GCing behavior.
I assume you don't have any GC logs/memory dumps to do forensics against,
so you're stuck trying to reproduce the problem so you can have something
to
If you have JMX enabled, just attach JConsole and look at the Memory tab;
it's easier than enabling GC logging for this basic use-case, and doesn't
require a broker restart. If you do find lots of full GCs, then it might
be worth turning on GC logging to figure out why, but it's overkill for
figur
I suspect this is full GC. Enable GC logging. You might already have a
gc.log and I’d take a look at that. If you tail -F the file and you’re
seeing constant “Full GC” back to back at like 1 second apart you’re in a
GC storm and you need to increase your memory.
I *suspect* there’s a memory leak
I think I figured out a realistic theory as to why my broker died last week
and ended up with my entire queue moving to the dead letter queue.
The problem happens when ActiveMQ goes into a full-GC loop where it
continually spends 100% CPU doing full -GCs.
messages are still served, but only say 1
Thank you for the response.
Well, it's just that the instance was up since from some time now. And not
much significant processing was involved.
Earlier broker -Xmx was set to 1G, after facing the above issue I have
increased to 2G. And this resolved the issue for now.
During this process, encou
Hello,
I'm using ActiveMQ 5.10.0 in Java 8. I'm not using any container, just
*two* simple Java SE applications on the same machine. My goal is to have
*one* application launch an *embedded* broker and have the other connect to
it using tcp. I am perfectly fine with using ActiveMQ specific code, I
You can start by using jstack to dump all threads' current stack traces to
give you an idea of what code is being run, though you won't know what data
it's being run against. If you identify a suspicious block, you could then
start the broker with the debugging port enabled (either uncomment the l
What makes you believe that your problem is the same as that bug, given
that you're using different options than what's described in the bug?
Either way, it should be easy to step through that code in a debugger and
confirm whether that problem really is what you're running into.
On Dec 30, 2014 1:
Hi there,
I need your precious help again. Scenario: I want to listen to all Advisory
topics, read messages and, at the moment, I need only to print them.
I wrote this code:
--
private static String ADVISORY_TOPIC = "ActiveMQ.Adviso
For reasons that I cannot figure out the ActiveMQ broker will spike its CPU
to 90-100% and stay there. I can kill the broker and restart the process
(consumers will then reconnect) and it works fine again with low CPU
utilization (0-1%).
How can I troubleshoot this? There are hundreds of consume
13 matches
Mail list logo
