You could try lowering the prefetch size to reduce the amount of Message objects which are loaded into the consumer....
http://incubator.apache.org/activemq/what-is-the-prefetch-limit-for.html Try set it to a low value like 100 and see if that fixes it. On 5/31/06, skarthik <[EMAIL PROTECTED]> wrote:
Only the consumer JVM (JDK 1.5) runs out of memory. I am using the default JVM heap sizes which I think is 64MB. But I put some logging statements in the consumer code to display memory statistics after receiving every message (using Runtime.maxMemory(), Runtime.totalMemory() and Runtime.freeMemory()). I see that max memory is 64MB and the total memory used slowly creeps up to that max mark and then encounters the OutOfMemoryError. Also I am using a non-durable subscriber, and am using subscriber.receive () with timeout to pull the messages from the Topic (NOT using MessageListener interface). Also the TopicSessions used are non-transacted with Session.AUTO_ACKNOWLEDGE mode. Hope this helps. karthik -- View this message in context: http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4645070 Sent from the ActiveMQ - User forum at Nabble.com.
-- James ------- http://radio.weblogs.com/0112098/
