I'm looking forward to hear more about this setup. It was my understanding that Wicket can't run in a non-sticky cluster setup due to the required pagemap locks to avoid concurrent updates to the component hierarchy. But I'd be very happy to hear my understanding being disproved.
Martijn On Tue, Feb 10, 2015 at 2:51 AM, Bryan Holladay <holla...@longsight.com> wrote: > Thank you Martin! I was able to get it to work really simply with setting > the following in my WebApplication: > > setSessionStoreProvider > setPageManagerProvider > > The implementations just passively passed and retrieved the data to and > from my Redis server. > > Thanks, > Bryan > > > > On Mon, Feb 9, 2015 at 3:32 PM, Martin Grigorov <mgrigo...@apache.org> > wrote: > >> Hi, >> >> Since I while I want to create an integration with >> https://github.com/spring-projects/spring-session but I haven't had the >> time (and demand). >> The way to do it is to create custom impl of ISessionStore interface. >> >> Otherwise I remember a user in the community successfully using distributed >> sessions with Jetty's JDBC session manager ( >> >> http://www.eclipse.org/jetty/documentation/current/session-clustering-jdbc.html >> ). >> >> Martin Grigorov >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Mon, Feb 9, 2015 at 7:51 PM, Bryan Holladay <holla...@longsight.com> >> wrote: >> >> > Has anyone setup wicket's AuthenticatedWebApplication sessions to use a >> > distributed memory cache (e.g. memcached, redis)? I would like to make >> the >> > sticky sessions fail over to other tomcat's and allow non sticky load >> > balancers. >> > >> > For example, I tested with >> > https://github.com/magro/memcached-session-manager on tomcat 7 with >> > memcached and both ELB and NGINX and it seems to not work with Wicket. I >> > also tested with redis by implementing >> > AuthenticatedWebApplication#fetchCreateAndSetSession. >> > >> > Thanks, >> > Bryan >> > >> -- Become a Wicket expert, learn from the best: http://wicketinaction.com