-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck,
On 10/11/2011 1:49 AM, Caldarale, Charles R wrote: >> From: Violeta Georgieva [mailto:miles...@gmail.com] Subject: Re: >> Fwd: SessionListener.sessionDestroyed is not called when stopping >> web application > >> I can confirm that in all three scenarios sessionDestroyed method >> is not invoked and session.expire(false) is invoked. > > This may be because the sessions are not actually destroyed. > Tomcat normally persists sessions in the work directory under the > name Catalina/[host]/[appName]/SESSIONS.ser when it stops so that > the sessions can be recovered when it restarts. This is exactly why I was asking about undeploy versus stop. Stopping a webapp should (by default) persist sessions to SESSIONS.ser, but undeploying a webapp should kill the sessions. That the sessions are not killed during a webapp undeploy is confusing to me, but that may have been done to avoid wiping-out a cluster when one node is taken out of service. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6UY0kACgkQ9CaO5/Lv0PAg9gCfVK6+/FAc7Bk87zldhDnQcheO WlsAn2Knl7318lFPJW97L6Mak1gwZGRz =jUiQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
