I think the question should be: why this _ONLY_ happens with the extended user and not with the _normal_ TurbineUser ? or does anybody have this problem without extending the user?!! regards Akmal ----- Original Message ----- From: "Scott Eade" <[EMAIL PROTECTED]> To: "Turbine Users List" <[EMAIL PROTECTED]> Sent: Wednesday, August 20, 2003 4:42 PM Subject: Re: extended user class not found problem
> Henning P. Schmiedehausen wrote: > > >Michal Frackowiak <[EMAIL PROTECTED]> writes: > > > > > >>I have a diffrent entry in Tomcat's logs. just after a tomcat is > >>started, my app throws an error. what helps is reloading app using the > >>manager application. but when I start tomcat and try to use my app I get > >>an entry in logs: > >> > >> > > > >Do you really need session persistence over container restarts? If not, > >configure your container to not save the sessions. > > > > > While I haven't checked the latest tomcat release, certainly up to now > the mechanism provided to stop the sessions from being persisted across > a context reload/container restart does not in fact work. > > I have made the script I use to start tomcat delete the persisted session > file. If it is a system that I alone am testing the problem usually does > not occur if I logout before I reload the context manually - if you auto > reload then you are probably going to have to restart manually in order > to clear the persisted sessions (as suggested by Michal). > > It would be great to eventually track down the culprit. > > Scott > > -- > Scott Eade > Backstage Technologies Pty. Ltd. > http://www.backstagetech.com.au > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
