2012/7/5 Philippe MARASSE <[email protected]>: > Member ;-), > > As far as I remember, clustering is not so easy. I've set up a few years ago > a clustered CAS involving a few more steps : > 1 - Clustering tomcat (on-line documentation at apache site is good > enough) > 2 - Make CAS redistributable in web.xml > 3 - Share the tickets registries (JPATicketRegistry if I'm not mistaken) > 4 - Use sticky sessions in the balancer > > Rdgs
It looks like mod_balancer does send the same client more or less to the same backend. So far I got session replication more or less working (the cas clustering wiki page says nothing about authentication so I'm also somewhat worried about session hijacking through the multicast packages that Tomcat sends - after all, everyone can capture those packages and it looks like any server can announce himself as a cluster member). I found a slideshow presentation somewhere that says you don't actually need session replication because it is only used for storing the "webflow state", and recommands adding repository-type="client" to <flow:executor id="flowExecutor" registry-ref="flowRegistry" > ... unfortunately I can't test if that works because it is based on an older Spring version and I can't find the equivalent in newer versions - that is, if it hasn't just been made obsolete at all. Many thanks for the advice and pointers, -- Frank Van Damme No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author. -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
