Folks, We are at 3.4.2.1. If the database holding the service registry is offline and then reconnected, CAS will automatically renew the connection and allow service as expected. However, CAS will not automatically restart if our firewalls are down long enough for a time out between the connections upon which it depends .. AD and the back end database. I have noticed it before when an AD server failed on the test system where the connections are not robust, but this is the first time we have systemic failures that blocked all connections.
This is the failure in the localhost.yyyy-mm-dd-log file: SEVERE: Servlet.service() for servlet cas threw exception org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 30 seconds Tomcat is not down and by all appearances, the CAS server is still running. What should I be looking at in our configuration that will allow CAS to re-establish all necessary connections automatically after interruption? Linda Toth University of Alaska - Office of Information Technology (OIT) - Identity and Access Management 910 Yukon Drive, Suite 103 Fairbanks, Alaska 99775 Tel: 907-450-8320 Fax: 907-450-8381 [email protected] | www.alaska.edu/oit/ -- 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
