Thanks for your reply. Yes, I am in fact handling persistent messages,
so it seems it works the way I understood it.
About file-based cursors use: My system uses (in the worst case) a
large number of queues, each with consumers that (in the worst case)
wants a (in the worst case) large volume of m
yes. on a restart that is what happens, so long as the messages are
persistent. The file cursor is a pending message cursor, so the
messages are pending for a consumer. if the consumer goes away or the
broker restarts, the messages are still pending from the store and are
replayed through the file
