Hi, It should also be interesting that you switch your persistence manager from JDBC to KahaStore because KahaStore is faster than JDBC. If the KahaStore is created on a SAN with RAID disks, this one should not be a point of failure in your architecture
Kind regards, Charles competitor consumers = several clients or same client using several threads for consuming messages from broker Charles lucious wrote: > > Ohh I got it ;) thanks a lot!!! BTW. What is competitors consumers? > > M. > > > > cmoulliard wrote: >> >> Hi Marcin, >> >> I think that too much messages are produced and consumers does not have >> enough time/memory to consume them. So the memory consumption continue to >> growth till to reach a limit. As you have configured the vm for the >> MessageCursor (http://activemq.apache.org/message-cursors.html), this >> behavior is logic and corresponds to what was designed in ActiveMq 4.x >> (see the link that I post). I propose that you removed them to let >> ActiveMq to use the new one which is the store front message cursor >> (messages are paged on disk if the memory limit is reached) or adapt the >> architecture to use competitors consumers. >> >> Kind regards, >> >> > > ----- Charles Moulliard SOA Architect My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ -- View this message in context: http://old.nabble.com/AMQ-%285.3.0%29-with-CMS-3.01--%3E-consumes-all-memory-and-stops-clients-and-producers-tp27771356p27818449.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
