Hi, we are using prefetch=0 with Spring, works well, still we are seeing the same issue but for _non-persistent_ messages. (With prefetch=0 and with prefetch=1.) Any ideas if this could correlate to the issues mentioned here?
As an interesting side-effect, the consumption starts again if we delete the queue with the stuck messages and/or purge it. Could useCache=false help in this case as well? We are using a file-based cursor: <pendingQueuePolicy> <fileQueueCursor /> </pendingQueuePolicy> Best regards, Martin On Thu, Apr 7, 2011 at 5:49 PM, Gary Tully <gary.tu...@gmail.com> wrote: > one other thought is to use a prefetch=0 such that any cached > consumers are out of the mix. > > On 7 April 2011 15:53, lernen.2007 <erpolat.er...@googlemail.com> wrote: >> The problem should be resolve as soon as possible. Otherwiese we must look >> after an another messaging system. >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-tp3244342p3433651.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > > > -- > http://blog.garytully.com > http://fusesource.com >
