-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Susan,
Susan G. Conger wrote: | Can someone tell me from experience what happens if a user is using a web | app and I do an update and reload=true. Will the user get kicked off and | have to re-sign on? Will they lose whatever they are working on? That depends on your configuration and the exact timing of the reload. If the request is accepted for processing before the reload, then the user should notice nothing -- the webapp will complete all in-progress requests before it shuts down. If the request is accepted during the re-load, the user might get a 503 or 500 error, depending on exactly when the request comes in. After the reload, the request should be handled normally. If you are using server sessions, and you are not using a PersistentManager to save the sessions to a file during webapp reloads, then any active sessions will be lost during the restart. If you are using FORM-based logins, then you will also lose those logins and your users will have to re-authenticate. If you are using BASIC or CLIENT-CERT authentication, then the user should not have to re-authenticate, but the user's session will still be gone. Finally, if you have stored any objects in a user's session that are not Serializable, then that session will certainly be lost during the restart... and might possibly preclude the loading of /all/ sessions (meaning that one bad session could disable session persistence across restarts entirely). Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkg0igYACgkQ9CaO5/Lv0PA0oACdGU8dtZC17WJslxkshVVMNiyL bRYAn17ICgSmjZS6UB4L24C20d4AArjg =u1wP -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
