If your pages are 40MB the problem is not the PageMap - it's that you're doing something wrong with the pages - something that needs to be fixed ASAP. Most likely you are holding collections of data directly in the page instead of using models.
-- Jeremy Thomerson http://www.wickettraining.com On Tue, Apr 6, 2010 at 8:21 AM, Elger van Boxtel <elger.vanbox...@planon.nl>wrote: > Hi, > > Currently, pages are stored in a PageMap for each session when the user > clicks the browser refresh button. > > In our application pages can grow quite quite big (sometimes even up to > 40MB). As you will understand, sessions can grow exponentially when > storing one or more pages and will cause trouble with mulitple users > over time. > > We've looked into the possibility of not storing the pages at all, but > this did not seem to work as Wicket expects a page to be registered in > the PageMap. > > What we did so far is minimizing the number of pages stored in session: > - we disabled versioning > (org.apache.wicket.settings.IPageSettings.setVersionPagesByDefault) > - we set max page maps to 1 > (org.apache.wicket.settings.ISessionSettings.setMaxPageMaps) > - we use LeastRecentlyAccessedEvictionStrategy(1) now, this evicts all > older pages and one leaves 1 page > (org.apache.wicket.settings.ISessionSettings.setPageMapEvictionStrategy) > > Does anyone know if we can disable statefull pages being stored in the > session after a refresh or disable this functionality completely? > > Thanks in advance, > > Elger > >
