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 deadf
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
You may just need to make your subscriptions durable:
http://activemq.apache.org/how-do-durable-queues-and-topics-work.html
but also check out -
http://activemq.apache.org/subscription-recovery-policy.html
which determines whether a subscription can see messages published
before it existed.
and f
