Lazily Loading Queues --------------------- Key: JBAS-1340 URL: http://jira.jboss.com/jira/browse/JBAS-1340 Project: JBoss Application Server Issue Type: Task Security Level: Public(Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Reporter: Adrian Brock This is a major change that is the last obstacle to JBossMQ scalability. The idea is that messages will only be loaded into the server when the destination is activated and then only part of the messages are loaded (enough to deal with the current throughput). An attempt was made to do this and committed on Branch JBoss_3_2_5_JBossMQ_Lazy but the work was abandoned. It does not deal with the more difficult problems. In any case, the BasicQueues should be talking directly with the PersistenceManager. In fact, I would favour that the BasicQueue implementation is actually pluggable and determined by the PM to allow better optimization between these two important layers.