I'm considering a 0 downtime deployment but am concerned with the amount of state in the wicket session.
This is the scenario that concerns me. 1) There are 2 tomcats running 2) A change is made to a serializable object and the serial version id is updated 3) 1 tomcat instance is taken down for updating 4) tomcat instance comes back up with new object and now tries to update state from other tomcat and the wicket session has a reference to the old version of the serializable. On Mar 5, 2010, at 12:18 PM, Igor Vaynberg wrote: > yes > > -igor > > On Fri, Mar 5, 2010 at 10:02 AM, Douglas Ferguson > <[email protected]> wrote: >> Has anybody had success with wicket using tomcat's session replication? >> >> D/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
