Thanks for your answer Chris. Exactly, I solved my problem by using HttpSessionListener AND tomcat 6.0.29.
Note: There were a bug in the Tomcat version I used: 6.0.18, the DeltaManager was not notifying the SessionListener after a full replication, when you get all Session from a new cluster node. Thx. Romain -----Original Message----- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Friday, October 01, 2010 11:48 AM To: Tomcat Users List Subject: Re: WAR Deployment before starting the cluster -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Romain, On 10/1/2010 10:06 AM, Romain Petit wrote: > My HttpSessionBindingListener was not notified because the session > replicated were deserialized, there were no attributes binding. > > So to get notified a session is replicated on a new server you can wrap > the readObject(ObjectInputStream in) or use the other session listener. Sounds like what you really want is HttpSessionActivationListener or HttpSessionListener, not HttpSessionBindingListener. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkymAskACgkQ9CaO5/Lv0PCqFwCeIUsKvDtA5tGJNYRnQiktM0AP 6mQAn20B2CdEJTiRK/c+BJKp3nebgCld =FB62 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
