Hi All, Hopefully an easy one...we have a pub/sub setup with a bunch of Groovy consumers using the Java client to listen to a bunch of topics. We terminate these by literally killing the process. When we do this, we seem to lose any dispatched messages that have not yet been processed. That is to say, if the web console shows Dispatched Queue size = 1,000 messages, after restart, we seem to be 1,000 messages short, if I'm reading the web console correctly.
Does that make sense? Is there just a configuration entry I can set which says 'Do not consider a message delivered until the consumer has actually dealt with it' which will make these messages get processed upon startup of the consumer? I've tried looking throught the docs, but I haven't had much luck. Thanks in advance, Matt -- View this message in context: http://www.nabble.com/Loss-of-dispatched-messages-tp21142086p21142086.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
