CAS becomes unavailable due to inactivity

[Supriya Prakash]

Hi,

I have deployed cas server 3.0.5 on tomcat 5.5.23. CAS talks to MySQL 5.0 for authentication purpose. For this I made following modification to deployerConfigContext.xml.

<bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource">
         <property name="driverClassName">
          <value>com.mysql.jdbc.Driver</value>
         </property>
         <property name="url">
          <value>jdbc:mysql://localhost:3306/db</value>
         </property>
         <property name="username">
          <value>user1</value>
         </property>
         <property name="password">
          <value>user1</value>
         </property>
        </bean>



                <bean id="SearchModeSearchDatabaseAuthenticationHandler"
                      class="org.jasig.cas.adaptors.jdbc.SearchModeSearchDatabaseAuthenticationHandler"
                      abstract="false" singleton="true" lazy-init="default" autowire="default" dependency-check="default">
                  <property  name="tableUsers">
                   <value>users</value>
                  </property>
                  <property name="fieldUser">
                   <value>userid</value>
                  </property>
                  <property name="fieldPassword">
                   <value>password</value>
                  </property>
                  <property name="dataSource" ref="dataSource" />
                </bean>
               
 The applications deployed on tomcat are then integrated with CAS by modifying their respective web.xml (s) and server.xml of tomcat. When I try to login to my application the login is successful and everything works fine. If I leave tomcat and mysql running overnight and if I again try to login to my application next day I get CAS in Unavailable error. If I restart tomcat everything works fine again. What could be the possible reason for this? What is the solution to this problem?




_______________________________________________
Yale CAS mailing list
cas@...
http://tp.its.yale.edu/mailman/listinfo/cas

[scott_battaglia]

My guess is you haven't configured the data source to look for stale connections and remove them.  MySql's jdbc url has methods to do this (check their documentation) as does the BasicDataSource.

-Scott

On Thu, May 8, 2008 at 6:42 AM, supriya prakash <supriya_prakash1@...> wrote:

Hi,

I have deployed cas server 3.0.5 on tomcat 5.5.23. CAS talks to MySQL 5.0 for authentication purpose. For this I made following modification to deployerConfigContext.xml.

<bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource">
         <property name="driverClassName">
          <value>com.mysql.jdbc.Driver</value>
         </property>
         <property name="url">
          <value>jdbc:mysql://localhost:3306/db</value>
         </property>
         <property name="username">
          <value>user1</value>
         </property>
         <property name="password">
          <value>user1</value>
         </property>
        </bean>



                <bean id="SearchModeSearchDatabaseAuthenticationHandler"
                      class="org.jasig.cas.adaptors.jdbc.SearchModeSearchDatabaseAuthenticationHandler"
                      abstract="false" singleton="true" lazy-init="default" autowire="default" dependency-check="default">
                  <property  name="tableUsers">
                   <value>users</value>
                  </property>
                  <property name="fieldUser">
                   <value>userid</value>
                  </property>
                  <property name="fieldPassword">
                   <value>password</value>
                  </property>
                  <property name="dataSource" ref="dataSource" />
                </bean>
               
 The applications deployed on tomcat are then integrated with CAS by modifying their respective web.xml (s) and server.xml of tomcat. When I try to login to my application the login is successful and everything works fine. If I leave tomcat and mysql running overnight and if I again try to login to my application next day I get CAS in Unavailable error. If I restart tomcat everything works fine again. What could be the possible reason for this? What is the solution to this problem?




_______________________________________________
Yale CAS mailing list
cas@...
http://tp.its.yale.edu/mailman/listinfo/cas

--
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
cas@...
http://tp.its.yale.edu/mailman/listinfo/cas