Hi Arjan, What Wicket version are you using?
In addition, you can try to identify components that keep references to objects outside the page structure. In wicket 2 this will all be serialized so you need to keep your components lean. If you use clustering this is also important in wicket 1. Erik. A. Zwaan schreef: > > Hello Erik, > > > > We are running in deployment mode, I’m afraid we already tried that. > > It seems to be the PageMaps that are causing the problems by writing a > lot of data to an outputstream. Also having multiple PageMaps is > unnecessary in our case, but the Application seems to keep making new > ones. I have tried various settings for PageMaps, but none of them > seem to work. > > > > The settings I tried were: > > - getApplication().getPageSettings().setMaxPageVersions(0); > > - getApplication().getPageSettings().setVersionPagesByDefault(false); > > - getApplication().getSessionSettings().setMaxPageMaps(1); > > > > > > Regards, > > > > Arjan Zwaan. > -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user