I'm creating this dev post as a continuation of the user's post about paging and management destinations: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159288 What should be the meaning of paging-global-max-size? Current definition: "The global max size is the max memory the server will be able to accept. After the limit was reach, the server won't accept anything protecting itself from Out of Memory Exceptions." But this seems too much, as when a single destinations puts the server into global page, this will mean... nothing else gets inside the server. My expectation was the user configuring page-max-size individually at address level, and having the global-max-size as an *extra* protection. If we want to allow routing when in global-page-mode, we will need to change the global-max-size definition a little bit. New definition?: The global max size is the limit where all the destinations enter into page mode. And any destination will have at least a minimal limit of data in memory equivalent to 1 page. the default will be 10MiB). This will also mean: We won't be able to protect the server from OMEs. If the user created a huge ammount of addresses (say.... 1000), each address will have at least 10MiB (pre-configured) in memory. Any thoughts? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247881#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...