Hi, We use CAS 3.4.7 along with an oracle database using the c3p0 connection pooling. We have run into the situation were we have had to increase the number of minimum connections available to the database to over 100 in order to avoid users encountering the checkout timeout limit. It seems that the time it takes to create the new connections and for the old connection to free up is taking longer than the set time of 20 seconds for the checkout time limit. When the user does reach the time limit they see a CAS unavailable message. So we reach certain times were we have more users try to login than the allocated connections available.
Since the number of connections can only be set when the environment is brought down has anyone found any problems with setting the open database connections to a high number and leaving them that way. Has anyone encountered a similar situation. Thanks! ___________________ Juan Quintanilla [email protected]<mailto:[email protected]> -- 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
