So, you obviously have a very slow consumer on that topic and messages keep piling up until they exhaust broker resources.
To deal with that you should use either, pending limit strategy, like you did in the first case. In this case the messages will be discarded to keep broker resources in order The other approach is to use producer flow control, and stop the producers when broker reaches its limits http://activemq.apache.org/producer-flow-control.html Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Fri, Nov 11, 2011 at 9:52 AM, Pete Redhead <peteredh...@googlemail.com>wrote: > Hi Dejan, > > Thanks for your reply. I made the change you suggested, however after 36 > hours the server stopped routing messages again. This time the log > contained > many messages relating to increasing memory usage with > > 2011-11-10 20:01:51,134 | DEBUG | Main:memory: usage change from: 99% of > available memory, to: 100% of available memory | > org.apache.activemq.usage.Usage | ActiveMQ Transport: > tcp:///10.15.81.142:46288 > > at the time the server stopped working. > > To me, this would suggest that there is an underlying problem with messages > becoming stuck somewhere on each topic. The pending message limit strategy > on the topics was stopping the number of messages getting too high and > causing the server to run out of memory. > > Any ideas what to look at / change next? > > Many thanks, > Pete > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Confused-by-ActiveMQ-Discarding-message-on-Topics-tp4007870p4030769.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
