<systemUsage> entries will set limits for mem, store, temp, etc for entire broker. if you comment them out, they'll revert to default entries http://activemq.apache.org/producer-flow-control.html#ProducerFlowControl-Systemusagewhich are quite low depending on your requirements.
The default for memoryUsage is 64MB but you set your queue memoryLimit to 100MB. That could very well lead to OOM. Please take a look at http://activemq.apache.org/producer-flow-control.html http://activemq.apache.org/javalangoutofmemory.html http://www.christianposta.com/blog/?p=273 On Mon, Mar 18, 2013 at 11:58 PM, comradgre <comrad...@gmail.com> wrote: > Hi! > Current system have about 100 messages per second. Could you pls help me > avoid flooding issue and improve performance of current activeMQ. > Please see attached activemq.xml > activemq.xml > <http://activemq.2283324.n4.nabble.com/file/n4664859/activemq.xml> > Current MQ have 2 queues: inq and outq. > > Sometimes i think, that it will be better to switch off producerFlowControl > and enable <systemUsage>, but i don't understand how to change current conf > file to have it (should I disable memoryLimit of policyEntry, what > systemUsage elements should be enable). > > Please help me, thanks! > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-topic-vs-queue-tp4664859.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
