couple of questions: -what wicket version are you using? -are you using httpsessionstore or secondlevelcachesessionstore (default)? -what application server/container are you using? -are you running the application in clustered environment? if yes, what kind of load balancing do you have? -do the expirations happen during normal operation or only when using back button (or using application in multiple tabs)
-Matej On Thu, Jan 22, 2009 at 7:47 PM, UPBrandon <bcr...@up.com> wrote: > > In some of our Wicket applications, as the number of users has started to > ramp up, we seem to be experiencing a scalability issue. Some users have > had problems with pages expiring quickly. This is second-hand information > so I can't elaborate much but supposedly, during peak times, pages are > expiring after just a few minutes of inactivity. It would be nice to be > able to set a minimum retention time but I don't seem to see an option like > that. I've found information about how Wicket stores pages and revisions > (http://cwiki.apache.org/WICKET/page-maps.html) but I haven't been able to > find much on how Wicket manages that data when things start "filling up." > Are there any good explanations out there on the web? > > -Brandon > -- > View this message in context: > http://www.nabble.com/Page-Maps-and-Expirations-tp21610595p21610595.html > Sent from the Wicket - User 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
