[jboss-user] [JBoss Messaging] - Behavior with selector and fullSize cache

Hi! I am using one of the latest versions of the 1_4 branch We are using one queue where multiple bridges/clients consume/transport messages using a selector. Try to visualize it: :-) Queue A Bridge X fetch messages with selector destnode=X Bridge Y fetch messages with selector destnode=Y Bridge Z fetch messages with selector destnode=Z The business logic always create one message per destinationnode with the header property destnode set to X,Y or Z The messages in the queue are added in a sequence like: a(x),a(y),a(z), b(x),b(y),b(z),.... Our messages are really big. from 20k to 20 megabyte so we want to limit the fullSize from default 200000 to 100 or similar. What happens now if destination X is not reachable for a longer time. What implications does this fullSize setting have then. This means that all message with destination (x) can not be delivered for that offline time. The messages in the queue then should look like this a(X),b(x),c(x),....t(x),t(y),t(z) Lets say we set it to 100 and there are 120 (x) messages in the queue. If we now add 3 new messages for x,y and z, does this now mean that the y and z message is not cached in the memoryqueue. Are those messages then delivered? And if so is each message then fetched from the database? to summarize: What happens is I use a selector and set the fulSize setting to a very low value. THX for a short explanation! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233312#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...