hi, perhaps you should wait for CAS 3.5 which contains support for EHCache (see [1]). I think the release is planed for this june.
cheers odilo [1] https://wiki.jasig.org/display/CASUM/EhcacheTicketRegistry On May 28, 2012, at 19:58 PM, Myn Harry wrote: > Hi: > > I have read the CAS clustering doc at > https://wiki.jasig.org/download/attachments/28574591/Clustering+CAS.pdf?version=1&modificationDate=1268947376041 > > Our University is still evaluating CAS 3.4.11 and the evaluation has moved on > to maintainability and operational tasks etc. > > Based on the University's expectation of future loads etc, we will probably > have 3 CAS servers runnung concurrently behind a load balancer. > > The two options most available to us to making the CAS server HA are: > > 1) jBoss Cache > 2) JPA (using Oracle as the DB) > > We are not familiar with jBoss and are learning towards experimenting with > JPA, on an Oracle DB, but were worried w.r.t issues reported at > http://jasig.275507.n4.nabble.com/JpaTicketRegistry-A-Sinking-Ship-td4256973.html > > We do not want to use TerraCotta/MemCache. > > Can the lists provide guidance on whether to use the jBoss or JPA approach > for CAS server high availability? > > Thanks. > -- > 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 -- 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
