For the developers of NMS:
There’s a mediation pattern we could use to handle duplicate messages. It
is the idempotent consumer pattern [1]. I believe it's a justifiable
approach to handling situations where the broker and its consumer(s) cannot
resolve the problem of duplicate messaging on the
Evaluating this further it appears the broker is not persisting any
information back to the database when it dispatches messages to consumers.
I verified by removing update privs on the ACTIVEMQ_MSGS table as well as
insert, update, and delete privs on the ACTIVEMQ_ACKS table. Yes we are
using J
