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 cursor, which can impact startup time. Typically using the default store based cursor is sufficient. The store cursor will use memory to cache pending messages as much as it can.
On 11 October 2012 15:10, Gilles Harloux <gilles.harl...@gmail.com> wrote: > Hi, > > I am designing a system around an embedded broker using file-based > cursors. I am trying to make sure I understand the way file-based > cursors work: Am I right in thinking that temporary files is > functionally the same as memory with respect to transactions and data > security? If the system was to crash and it somehow lost or corrupted > temporary files, would it be possible to restart and get those > messages (those that ended up in the temporary files) back from the > message store? > > TIA, -- http://redhat.com http://blog.garytully.com
