Aside from the obvious metrics such as cpu, heap, active connections,
producer/consumer count, and persistent store usage, are there any subtle
metrics to monitor over JMX for maintaining complete operational coverage of
this product?
Is there a limit to the number of threads, connections, or
This is normal and expected behavior for ActiveMQ with KahaDB as well.
I've never used LevelDB, so I can't speak to its behavior, though I have no
reason to believe it would behave differently than the other two.
ActiveMQ can't work without a backing store if you've configured it to
require one.
Of course it fails, but it should not put the service down.
The service should keep running until it can reconnect.
I believe this is not a normal behavior of ActiveMQ,
and if it is, how can I config it otherwise?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Crushing-
Please provide your full broker config and the full stack trace.
Also, does browsing via the web console work but browsing via JConsole
doesn't?
On Oct 21, 2015 2:15 AM, "spamtrap"
wrote:
> [ActiveMQ 5.11.1]
> If I try to browse an ActiveMQ queue which contains one or more
> messages with JConso
This sounds like a bug. Since Tim Bish (the only person I've seen support
ActiveMQ-CPP) didn't comment on it here, please submit a bug report in
JIRA, ideally with your consumer code (better: a stripped down minimal
version that produces the behavior without any irrelevant extras) to help
recreate
