As I understand it, the cursor spools out to disk messages that have been
committed into the memory store. If they're participating in a transaction,
they're not committed and are instead just sitting in memory in the
org.apache.activemq.store.memory.MemoryTransactionStore. (I assume we're
talking
I have been able to successfully have large number of persistent messages
spool over to the filesystem exactly as intended by using the
cursorMemoryHighWaterMark for messages that have been enqueued to the queue.
The issue I am running into, it happens only a few times per day in our
system, is th
