the fileQueueCursor should work well for you but the error with the journal
looks like an issue that requires a jira entry. It should be better able to
deal with wrap around.
If you have time to produce a simple test case that demonstrates this usage
pattern and attach it to a new jira, it would be
Hi all,
I have done some more test and now seems to me that the problem has
nothing to do with journal files but with journal files in cursor storage.
My previous thoughts were wrong as messages are committed into the
database every 5 minutes or as soon as the cursor memory reaches 70%
