Adriano- from what I've seen the normal way of handling the webapp reload is to clean off the work folder *.ser files this would be considered 'normal behaviour' since your webapp configuration has changed the attributes for any previous serialised objects would be changed as well.. thus any serialised objects should NOT be deserialised back into the webapp
does this not make sense ? Martin ______________________________________________ Disclaimer and confidentiality note This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided. > Date: Wed, 25 Mar 2009 20:11:33 +0100 > Subject: Re: Session lost when app. is redeployed > From: joseph.mil...@gmail.com > To: users@tomcat.apache.org > > Not sure this might be of use but Apache normally has a *graceful *restart > option that's normally tailored to such needs. > > On Wed, Mar 25, 2009 at 1:17 PM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Adriano, > > > > On 3/24/2009 7:13 AM, Adriano dos Santos Fernandes wrote: > > > So my question is how to update an application, when it have full > > > serializable sessions, and the new application classes are compatible > > > with the serialized session? > > > > > > I didn't see any way to do it with Tomcat... > > > > I use 5.5.27 and, in development where autoreload=true, I trigger > > auto-redeployments all the time by changing web.xml, adding libraries, > > or updating classes. My sessions remain in-tact without a problem > > (unless, of course, I change a class for an object that is actually in a > > live session). > > > > No logs at all, eh? > > > > What about the serialized sessions file? Under the circumstances when > > the sessions /are/ persisted, can you locate the serialized sessions > > file (while the app is stopped, that is)? Copy it to a temporary location. > > > > What about in the case where the sessions file is /not/ persisted > > (again, while the app is stopped and/or undeployed). Is the file still > > there? If not, what happens if you take the file from above and use it > > as a surrogate, placing it in the right place at the right time? > > > > I'm wondering if the problem is in saving the sessions or loading them. > > I suspect that Tomcat is not saving them when you undeploy. I'm not sure > > why, since Tomcat claims to do it: > > > > http://tomcat.apache.org/tomcat-5.5-doc/config/manager.html#Restart%20Persistence > > > > If you put <distributable> in your web.xml, do you get any errors? > > > > - -chris > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.9 (MingW32) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > > > iEYEARECAAYFAknKIMoACgkQ9CaO5/Lv0PC0fQCgjGDckxzlxMrrA6RY7Yovaxpw > > sZAAoKN9qtucZn7/NlAMRJg6GJt1Be+g > > =Lcp/ > > -----END PGP SIGNATURE----- > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > _________________________________________________________________ Express your personality in color! Preview and select themes for Hotmail®. http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=TXT_MSGTX_WL_HM_express_032009#colortheme
