Re: How to avoid ActiveMQ 5.x OutOfMemory in certain high-pressure conditions?

I want to post a follow-up with an update that this specific OOM was my own mistake. Even though I indeed was running my embedded broker on a separate VM number of times and commented out demo producer/consumer code, I forgot to comment out this line which came right after session creation, which i

Re: How to avoid ActiveMQ 5.x OutOfMemory in certain high-pressure conditions?

Thanks, Tom. This is also valuable insight and a very valuable information. However, I think you got it wrong: final boolean sendProducerAck = !message.isResponseRequired() && producerInfo.getWindowSize() > 0 && !context.isInRecoveryMode(); It essentially says that one of the cond

Re: How to avoid ActiveMQ 5.x OutOfMemory in certain high-pressure conditions?

Not sure if this applies here: http://activemq.2283324.n4.nabble.com/Producer-Window-Size-td4668545.html The way I read the response producer window size stops flow control. -Tom > On Aug 7, 2018, at 5:52 AM, art.licis

Re: fetching queue details

I think your best bet would be to use the REST management interface exposed by Jolokia referenced in the documentation [1]. Justin [1] http://activemq.apache.org/rest.html (see "Rest Management" section) On Wed, Aug 8, 2018 at 2:39 AM, arungujjar wrote: > how to fetch queue details like enque

fetching queue details

how to fetch queue details like enqueue count, dequeue count from activemq using python program -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html