Hello all Following on from these threads:
http://www.nabble.com/Blocking-on-UsageManager.waitForSpace-again-tf3031460.html http://www.nabble.com/OutOfMemoryErrors-again-tf3083798.html I've updated my ActiveMQ 4.2 from trunk to include Rob's latest patches, but I'm still having problems. Looking at the example I posted here: http://www.nabble.com/Re%3A-Blocking-on-UsageManager.waitForSpace-again-p8521205.html is there a way in a fast producer, slow consumer scenario to configure ActiveMQ to block the producer until space becomes available for it to send more messages, without spooling to disk or running out of memory (maybe with some kind of configurable timeout on how long the producer blocks before throwing)? We want the messages to move at the speed of the slowest consumer (since we only ever have one consumer), not the producer. Running that example, with the Sun JDK's default heap size, I still run into OutOfMemoryErrors. Increasing the heap size with -Xms256m -Xmx512m causes the program to run, until it promptly fills up the disk on my machine. I've specified both broker.persistent=false and DeliveryMode.NON_PERSISTENT on the producer, but it seems some kind of persistence is still active, since I promptly see my activemq-data directory filling up. Thanks! Cheers, Albert
