I checked the code for the MaxDepth attribute in the BasicQueue code and it will throw an exception if the queue is at the maxDepth. Here is the functionality that I think would be correct:
1.) Accept messages in memory and presistant store up to maxDepth. 2.) Any messages above maxDepth should only be placed in presisitant store with a special marker that indicates that the message needs to be requeued. The basic queuing FIFO functionality needs to be retain by placing all subsequent messages in the store untill there are no additional marked messages and there is space in memory. 3.) We need an addtional thread in the BasicQueue that reads marked messages from the presistant queue and moves them into memory space and the messages in memory are consumed. This would give us protection against over use of memory and will still retain the speed of using memory. Manuel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830127#3830127 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830127 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
