you using a transacted consumer by any chance. You may be experiencing: https://issues.apache.org/activemq/browse/AMQ-2032 that is resolved on trunk so you can try a snapshot.
if not, this sounds like a bug. Any chance you could produce a small test case and attach it to a jira? 2008/12/23 deadfolk <nab...@deadfolk.com>: > > Thanks for your reply Gary. > > We are using durable subscriptions...any messages which have not yet been > delivered will arrive once the consumers start again. > > The problem seems to be that any messages which have been prefetched but not > handled are not rolled back if the consumer terminates, but the "reads" are > committed and so never redelivered. > > That last link was useful, however, as it shows how I can change the > prefetch value, which should at least reduce the number of messages > lost...it's not a system where a few messages between the cracks > occasionally is the end of the world. ;) > > > -- > View this message in context: > http://www.nabble.com/Loss-of-dispatched-messages-tp21142086p21146111.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source SOA http://FUSESource.com
