The cache has nothing todo with persistence.
It just flushes messages to disk that would otherwise
use up memory.
If a message is persistent and you are using durable
subscriptions or a permenant queue, the message is
persisted before it is made availble to the queue.
It is only removed from the persistent store at
> The cache has nothing todo with persistence.
> It just flushes messages to disk that would
> otherwise use up memory.
You mean that after a message is persisted it gets available to the queue it's loaded into the main memotry? And amount of such messages is configured by the cache?
It tries to keep a copy of the message in memory for
If memory exceeds the highmemorymark it starts flushing messages to disk to keep memory below the maxmemorymark
For jdbc2 this is a no-op for persistent messages
because the cache and pm are the same store.
The other persistent managers don't know about the cache
so you can get two copies of the message on disk.
I got it! Thx.