Martin, Thanks a lot for the reply. Actually, I would appreciate if you helped me. I tried your tomcat session manager with my wicket app. I followed the configuration instructions for Tomcat you listed on the session manager page. But it didn't seem to work for ajax requests. I believe I used sticky haproxy configuration (to add session id to the request) but it still blew up with PageExpiredException on ajax requests.
And there is even more significant issue: the protocol will eventually be secured (https) and haproxy (used in production) wouldn't be able to support sticky sessions in that case. I can verify one more time my configuration (to make sure I use sticky sessions, sync session storage/retrieval, same request renderng etc.) and will let you know if it worked for me or not. Thanks, Dmitry -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-clustering-without-web-server-clustering-tp2234048p2236689.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
