On Tue, Oct 7, 2008 at 3:04 PM, activemqny <[EMAIL PROTECTED]> wrote: > > We use a network of brokers and topic to do messaging. All our message > producers and consumers talk to the local VM broker. We reply on bridges > between network of brokers to move messages between brokers. > > I attached two files to show this memory leak problem. TryJmsClient keeps > sending persistent messages to a Topic. TryJmsManager has a message > consumer. Start TryJmsManager first and then start TryJmsClient. After > running about 10 seconds, TryJmsClient stops sending because of getting > "SystemUsage memory limit reached" error. About 24K messages are sent and > consumer shows it get all messages. Now examine ActiveMQ MemoryUsage > printout of TryJmsClient, MemoryUsage percentage stays at 100% or 99% > forever. Producer can never send any more messages. > > Note1: If I slow down sending by adding a sleep, I don't see memory leak > immediately. I am not sure for longer running time. > Note2: If I use Queue instead of Topic, there is no memory leak.
This is not a memory leak, it's directly related to the way that producer flow control works: http://activemq.apache.org/producer-flow-control.html Try disabling producer flow control in conf/activemq.xml to see if that takes care of the issue. Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache ActiveMQ - http://activemq.org/ Apache Camel - http://activemq.org/camel/ Apache ServiceMix - http://servicemix.org/ Blog: http://bruceblog.org/
