Geoff, Ehcache seems to perform better than using a database (JPA), there is also jboss, memcache etc. I am sure you will get lot's of replies as there seems to be quite a few that have set it up this way. We are using a Cisco ACE LB hardware for our setup (ehcache for tickets, json for service registry) that we are rolling into production currently.
Scott Massari Owens Community College Senior Systems Administrator Phone: (567) 661-2059 Cell: (567) 277-0638 Fax: (567) 661-7643 >>> On 5/8/2013 at 09:24 AM, in message >>> <ff549b8a8619594b88cc9f92fc3be5d37ee2af1...@jupiter.unfcsd.unf.edu>, >>> "Whittaker, Geoffrey" <[email protected]> wrote: Good morning, We have a hardware load balancer/proxy that we'd like to use for a distributed deployment of CAS using a central database. While we were discussing it this morning, we stumbled on the question of whether or not CAS will have a problem with all of the connections having the same source IP (the balancer/proxy). Has anyone ever configured CAS like this... with a proxy/load balancer in front of two servers and a central database? Is this a terrible idea, fraught with peril and heartache? Is there a better way to ensure redundancy? Geoff -- 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
