Selector and paging : messages are not loaded from storage ----------------------------------------------------------- Key: JBMESSAGING-1823 URL: https://jira.jboss.org/browse/JBMESSAGING-1823 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.5.GA, 1.4.0.SP3.CP10, 1.4.0.SP3.CP09, 1.4.0.SP3.CP08, 1.4.0.SP3.CP07, 1.4.0.SP3.CP06, 1.4.0.SP3.CP05, 1.4.0.SP3.CP04, 1.4.0.SP3_CP03, 1.4.0.SP3.CP02, 1.4.0.SP3_CP01, 1.4.0.SP3 Environment: Jboss Messaging 1.4.0SP3 (also 1.4.5.GA) Reporter: CYRIL GERBIER Attachments: SelectorPagingPb.zip My problem concern the use of selector on paging queues: as long as the first message in memory is not consumed, jboss messaging 1.4.0 SP3 (also 1.4.5.GA) doesn't load messages from storage. For example, I create a queue with following paging parameters: FullSize=20, PageSize=10, DownCacheSize=10. I send 35 messages in this queue (with JMS property test set from 0 to 35). So I have 20 messages in memory and 15 on storage. Then, I try to consume messages except the one with test=2. I use selector on test property to consume my messages. The result is I can consume all messages in memory, but I can't for those in storage: they are staying in storage, and JBoss Messaging doesn't load these messages from storage. Actually, the messages in storage are loaded only when first message in memory is consumed. In my case, I don't consume message 2 which is the first message in memory. How avoid this behaviour that block all my product with thousands of messages blocked in my queue? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira