Hi Chris, we encountered similar problems, and wrote two blogposts: One about tweaking all the components, one about zipping the session.
http://www.small-improvements.com/blog/technical/tuning-wicket-session-size http://blog.small-improvements.com/2012/02/19/reducing-wicket-session-size-to-one-third/ You should use a proper profiler (e.g. JProfiler) to figure out the size of your pages and objects, much more efficient than logging stuff youself. And then also you can also write a custom IPageMapEvictionStrategy that takes session size into consideration when evicting pages (e.g. you evict so many pages until the session size is below 1MB again). That's the last resort only, but helps avoiding the nasty blank exception page. All combined, you should be able to work around the session size issue. Cheers, Per -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Page-Session-persistence-on-AppEngine-tp4475827p4518388.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
