I have configured CAS to persist the Services Registry into MySQL as documented at:
https://wiki.jasig.org/display/CASUM/Configuring I have attached a snippet of my deployerConfigContext.xml that contains this configuration. However, I was surprised to find CAS was completely unresponsive to web requests when the MySQL server was down for maintenance. I read the following from the wiki: ----------------------------------------------------------------------- Notes on the availability of Services Management Application Database If the Services Management Application database happens to be unavailable you will still be able to perform service authorization. CAS maintains an in-memory collection of services that is periodically refreshed from the database. If the database is down, the periodic refresh process will fail. But the in-memory data will continue to be available to support service authorization. ----------------------------------------------------------------------- I used some iptables rules to simulate the MySQL server being unavailable. The following log entries appeared: 2013-01-23 16:09:34,309 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] - The last packet successfully received from the server was 774,962,088 milliseconds ago. The last packet sent successfully to the server was 774,962,089 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. 2013-01-23 16:16:40,322 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] - Could not create connection to database server. Attempted reconnect 3 times. Giving up. etc. Is there something wrong with my configuration? Is the wiki note about availability wrong? Thanks, Andy -- 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
deployerConfigContext.xml
Description: XML document
