Hi !
Thx for explanation. But this basics I know already.
I did the test with a limit of 50 and added a lot of messages for x y and z to
my queue. I also undeployed all bridges.
Then I deploy bridge x. All messages in the memory which contains the header
property destination=x are bridged
Yes selectors do not work well with paged messages.
To implement it otherwise would be difficult - we'd have to scan the entire
file store for matching messages every time a consumer is added.
If you find yourself needing functionality like this, then it sounds like you
need a database not a
Hi,
Using fullSize you can limit the max number of messages in memory of a queue.
If the queue's messages (not delivered) reaches fullSize, any more messages
that are routed to the queue will be 'paged' to DB. As messages in memory are
delivered, more messages are 'fetched' from the DB into
