Here is some more info if that would help. We have four persistent queues A, B, C, and D.
- Client 1 sends a message each to queue A, B, and C at an average rate of about 2 per second. - Client 2 receives a message from queue A, processes it, and sends a result message to queue D. - Client 3 receives a message from queue B, processes it, and sends a result message to queue D. - Client 4 receives a message from queue C, processes it, and sends a result message to queue D. - Client 1 receives and processes result messages from queue D on a separate thread. Client1: useAsyncSend=true Po Po Cheung wrote: > > > Po Cheung wrote: >> >> We got OutOfMemory errors on both the broker and client after >> sending/receiving 600K messages to persistent queues with transactions. >> The memory graph below shows the heap usage of the broker growing >> gradually. Max heap size is 512MB. UsageManager is also at 512MB (will >> that cause a problem? should it be less than the max heap size?). When >> JMS transaction is turned off, the heap usage never exceeds 10MB and we >> do not run out of memory. There is no backlog in the queues so it should >> not be a fast producer, slow consumer issue. Are there any known issues >> of memory leaks in ActiveMQ with transacted messages? >> >> Details: >> - ActiveMQ 4.1.1 SNAPSHOT >> - Kaha >> - Default pre-fetch limit >> >> Po >> > http://www.nabble.com/file/7328/ActiveMQHeap.gif > -- View this message in context: http://www.nabble.com/Out-of-memory-errors-tf3443750s2354.html#a9618502 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
