And an other question: is there risk changing from wicket 1.3-beta2 to beta3 in nearly completely implemented application?
2007/9/24, Benjamin Ernst <[EMAIL PROTECTED]>: > > Because our Application in an intrannet-Apllication the user should stay > logged-in their whole workday. So our session-timeout is 12 hours and the > sessions don't expire for a long time. Could that be a problem too? > > And it could be that we killed the tomcat a few tims. > I will watch for session-directory size and how it grows. Is there a way > to check wether a session in this dircetory is no longer in use? > > Benjamin > > > 2007/9/24, Johan Compagner <[EMAIL PROTECTED]>: > > > > Yes we listen to unBind events, so they should be deleted. > > The only way that doesn't happen currently that i can think of if you > > kill > > tomcat the hard way > > then the current sessions will never normally expire and will never be > > cleaned > > > > johan > > > > > > > > On 9/24/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > > > On 9/24/07, Johan Compagner < [EMAIL PROTECTED]> wrote: > > > > how do you stop tomcat when you stop it (if you do that) > > > > Make sure that you never kill tomcat, If you do that then you have > > to > > > delete > > > > the dirs yourself. > > > > > > But even without shutting down, those old sessions should be removed, > > > no? I mean, as far as I remember, we explicitly delete them when they > > > expire. > > > > > > Eelco > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > >
