Re: ActiveMQ 5.11.0: Out Of Memory, caused by PageFile object tree filling up heap

2018-07-20 Thread Tom Hall
Hi Art, What per destination limit are you looking for? The per destination limits will deal with memory used per queue. http://activemq.apache.org/per-destination-policies.html -Tom > On Jul 20, 2018, at 3:50 AM,

Re: ActiveMQ 5.11.0: Out Of Memory, caused by PageFile object tree filling up heap

2018-07-20 Thread art.licis
300mb memory limit is on a VM having -XmX 4Gb for heap; on 8Gb (most likely) it was more. While I totally agree 300 Mb memory limit is far from the optimal setting, and even better per-destination limits are needed. However, I have stress tested ActiveMQ with much less memory, and I've seen the

Re: ActiveMQ 5.11.0: Out Of Memory, caused by PageFile object tree filling up heap

2018-07-19 Thread Tom Hall
Are you really limiting ram to 300 mb? Why so low if you are on a 8G box? Thanks, Tom > On Jul 19, 2018, at 7:13 AM, art.licis wrote: > > Dear community, > > We've been evaluation AMQ which is based on version 5.11.0. Several tests in > staging environments which would have a big number of

ActiveMQ 5.11.0: Out Of Memory, caused by PageFile object tree filling up heap

2018-07-19 Thread art.licis
Dear community, We've been evaluation AMQ which is based on version 5.11.0. Several tests in staging environments which would have a big number of producers and consumers ended up with OutOfMemory: GC Overhead Limit exceeded exception. However, it looks like it's just one slow consumer that is