-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jerry,
On 4/15/2009 11:58 PM, jerrySheen wrote: > So u mean to say, that if I were to prolong the JSESSIONID cookie's expiry > time, the server would take care of repopulating the session state(stored in > the db) even after a browser restart? > > Well, this seems like a much simpler solution,ill give it a try, hope it > works. You have to modify the cookie that Tomcat creates. By default, the cookie has a max age of -1, which means "forget me when the browser closes". Note that this is different than the "maxInactiveInterval" for the session itself, which is the expiration date for the /session/ (no the cookie). You'll have to write a filter or something like that to modify the cookie sent to the browser. You want to grab the appropriate cookie and change the max age to something else. You probably want to make it something like "tomorrow" (relative to today, of course) so that the cookie is persisted across browser restarts. Note that an expired session on the server side is non-recoverable. Good luck. Post back if you develop a decent solution. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknooOEACgkQ9CaO5/Lv0PDVIQCeL/EVSixGDiz02Orzk4LuxLKa K08AoKqmrENfD1zsh17+3eWgLkClQhhT =RG+p -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
