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
I think there may be a bit of confusion about the presentation of the
information between the two consoles. The ActiveMQ 5.x console presents
information mainly in JMS terms (e.g. queues, topics, durable subscribers,
non-durable subscribers, etc.). However, Artemis was written from the
ground up to
We don't explicitly test against all possible versions of a database,
because our use of the database is simple enough that once ActiveMQ works
with a particular database product, we typically work with all versions of
that product. There could always be exceptions to that rule, of course, but
we'd
My last question in that three-year-old thread applies to you too: are you
using a wrapper such as Tanuki that would detect the broker process exiting
and respond by restarting the ActiveMQ process? This would be the expected
way to handle this situation, so if you're not doing that, it's what I'd
What Clebert is saying is something along the lines of "If you have
concrete, specific improvements you'd like to see for the web console,
please submit them as JIRA enhancement requests, preferably with an
associated pull request that fixes them."
Also, keep in mind that UX preferences can be (no
