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. http://www.nabble.com/file/p19867244/TryJmsManager.java TryJmsManager.java http://www.nabble.com/file/p19867244/TryJmsClient.java TryJmsClient.java -- View this message in context: http://www.nabble.com/Nework-of-brokers-and-Topic-leak-memory-tp19867244p19867244.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
