Hi, "I can stop one of the instances and I'm not logged in" This statement says that you don't really have a properly configured failover. If those two Tomcat instances are in a cluster then the http sessions should be replicated and you should stay logged in no matter which one is serving the request. Wicket will store the used stateful page at the disks for all Tomcats in the cluster, if it the replication is actually working!
On Wed, Mar 22, 2017 at 1:02 PM, Wayne W <[email protected]> wrote: > Hi, > > We have 2 instances of Tomcat running with Apache sitting in front > balancing between the Tomcat instances. I have session replication setup > which seems to work for basic bookmarkable links on the pages. I can stop > one of the instances and I'm not logged in as it failover to the other > instance. > > However for normal Link<?> and ajax links etc I get > ComponentNotFoundException thrown as the new instance cannot find it in > the session it seems. > > Clearly I'm not understanding how wicket manages the page state or I've > configured something wrong. > > Does wicket support full session failover ? > > Many thanks >
