-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sandy,

I am about to go live with my campus' implimentation, and our setup is
much the same as yours is described.

1. We use the webflow method. It's what worked for us.

2. We were having some serious database side issues and proformance
problems *until* we indexed the foreign keys in the database on (I
believe) the ticket registry table, and all the problems disappeared. We
have run the same tests (with Canoo and Selenium) against our cas
install, and we went from 80%+ of simply login/logout/repeat
transactions failing, to 0%

3. I would like this answer as well.

Jeff

Sandy Gordon wrote:
> 
> Hi,
> 
> I'm working on a project to provide CAS on our campus.  We're hoping to 
> cluster two instances of CAS 3.3.5 on Tomcat 6 behind a load balancer.
> In reading through the list archives and the wiki pages, it seems there 
> are a number of different ways to cluster CAS.  I'm hoping to get some 
> advice regarding these different options:
> 
> 1. Tomcat session replication vs Spring Web Flow "request state"
> 
> Configuring Web Flow to use repository-type "client" seems simpler
> to implement than clustering the two tomcat servers with multicast.
> Are there any trade-offs or disadvantages to doing it this way?
> 
> 2. JpaTicketRegistry and table locking issues
> 
> In our test deployment (one server) we're using the JpaTicketRegistry.
> I've read the past discussions on the table locking issues that some 
> sites have experienced.  Are these common to all implementations, or 
> are there some databases that don't suffer from this problem?  We're 
> considering both a single Oracle database and multiple Postgres 
> databases with replication via pgpool.  Has anyone had success using 
> pgpool with CAS?  If so, do you still use c3p0, or do you use pgpools 
> own connection pooling?
> 
> 3. Ticket Registry Cleaners
> 
> Is it a good idea to run the Ticket Registry Cleaner on both servers in
> the cluster, or just one?  Or is it better to remove this altogether and
> run external SQL deletes against the database to remove expired tickets?
> 
> Any advice is appreciated.  Thanks in advance...
> 
> Sandy
> 
> 
> --
> Sandy Gordon
> Unix Systems Administrator
> University of Victoria Libraries
> [email protected] / 250-721-8266
> 
> 


- --
Jeff Chapin,
Assistant Systems/Applications Administrator
ITS-IS, University of Northern Iowa
Phone: 319-273-3162 Email: [email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkvgcOgACgkQQiaEUfQoY7QS3QCgjLHMdkpIDCNe9d6zXYGeN+z0
TesAnjTCGRoR26Qcs5DEY0nJnCSs26xg
=PAXA
-----END PGP SIGNATURE-----

-- 
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

Reply via email to