We are running a high-volume environment on a 4 server tomcat cluster. Every so often (about 1 time per month) during peak load times, our Tomcats will start to thrash on garbage collection. We've traced the problem down to the sessions being created are taking up all the heap space - even though the vast majority of sessions are unnecessary because the user is completely unauthenticated at the time the session is created.
We have a 6GB heap space on each server - but the authenticated users take up less then 1/10th of this space, the rest is going to unauthenticated users. We have tuned our session durations down for unauthenticated users to 1 seconds, but we can still encounter loads that generate sessions for unauthenticated users so fast that we run out of heap. (Not because we generate sessions faster than they are being expired - but because Tomcat's expiration code is very slow, so "old" (past expiration time) sessions linger for more than an hour during peak load. To us, the ideal solution would be to not create sessions if the user is unauthenticated. We're using Tapestry 5.1.05, and we can't figure out how to make a page that does not create a session in Tapestry. Can someone point us in the direction of the documentation on this (if there is any)? -- View this message in context: http://old.nabble.com/I%27d-like-to-have-a-page-with-no-session-for-unauthenticated-users%2C-and-with-a-session-when-the-user-is-authenticated-tp27116942p27116942.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
