Hi, I am using JDBCPersistence (without journaling) in my product. There are times when : - my broker goes down - there are already some messages in the queue as they were not processed yet. - my broker comes up again and restores the queue(s) On the third step, it seems to be executing a simple 'select id,msg from activemq_msgs where container = ? orderby id' query to get ALL the enqueued data.
This results in the loading of ENTIRE Data on my VM. IS there a way to let that NOT happen? Is there a way to make the adapter read queue data in chunks? (maybe ... 100 messages at a time .. read the next 100 when 90 of the first 100 have been processed) ? Any pointers would certainly help! Thanks! Vipul -- View this message in context: http://www.nabble.com/Queue-Recovery-loads-the-entire-data--tf3793599s2354.html#a10729587 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
