I'm not sure what your use case is, so I can't say for sure whether throwing away a potentially-large number of messages is a valid option for you. But if it were me, I'd focus on figuring out why your broker can't handle your required workload and on how you can adjust either the broker or your use-case to make it work. Maybe the broker needs larger limits (and the hardware to back them), maybe you need to publish your 40,000 messages to multiple brokers (effectively sharding your destinations so that a single broker doesn't have to handle the full load), maybe you need to publish fewer messages, etc. You seem to be taking for granted that 1) you have to publish 40,000 messages, and 2) the broker's configuration is the best possible one to accept them, and I'd question those assumptions before I started looking at discarding messages.
Tim On Fri, Oct 16, 2015 at 2:00 PM, dhananjay.patkar < dhananjay.pat...@gmail.com> wrote: > Setting broker to fail producer in case its out of resources, instead of > making producer wait forever > > <systemUsage> > <systemUsage sendFailIfNoSpaceAfterTimeout="3000"> > <memoryUsage> > <..... > </memoryUsage> > </systemUsage> > </systemUsage> > > Your views on this? > Broker machine is very high config vm (56 G ARM out of which 70% for broker > and has 8 cores ) > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-consumer-count-is-set-to-0-tp4675930p4703077.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
