Hi Peter,
a default cursor for persistent messages is store based cursor, which
keeps only a batch of messages in the memory. For non-peristent
messages a default cursor is file-based cursor. VM cursor must be
explicitly set and is suitable only for high-throughput environments
with producer flow
Good Day,
If you disable producer flow control and set per destination policy, isn't it
advisable to also move away from vmCursor since all the message are dispatched
from memory. Doesn't using vmCursors defeats the whole purpose of trying to
offline the message to a temporary storage ?. Isn't
