Hi,
thanks for your response.
There will be ~250 clients and all clients are almost connected at the same
time. All messages expire after 150 seconds.
best regard
Shine
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Performance-queues-topics-vs-selectors-tp4652915p46529
Hey, I am facing same issue in AMQ 5.6 version and topic size keeps growing.
Will it ever decrease as there is no indication of whatsoever whether
messages are actually discarded or expired.
So this enqueued count will never decrease, and how do you verify that your
messages are getting discarded.
How many clients will you have? i.e. potential destinations if you follow
the 1-destination-per-chatter model? Will they all be connected at the same
time? Do messages expire? Are messages volatile, or do you need to save
them in case chatters have disconnected?
If you can avoid a "single destinat
Definitely upgrade to 5.5.1 or later.
What does your JMX instrumentation tell you when the problem occurs?
- Is the connection active?
- Does the # of consumers in the destination match what you expect?
- Does a subscription for that client exist?
My questions boil down to: at that poin
ActiveMQ comes bundled with quick, easy yet powerful Ant-based consumer and
producer scripts.
Look at the example/ directory of the base installation. Run "ant" there
and you'll get instructions.
Anyway, for your use case, this command would do the trick:
ant consumer -Durl=tcp://10.10.10.10:61616
Hello,
I'm currently planning to realize high availability of an Active MQ broker
instance through the use of a Pacemaker HA resource manager on a Debian
Linux system. I'm currently using Active MQ 5.5.1.
1. Are there any tips, tutorials, best practices, common mistakes on how to
setup Active MQ
