On Fri, Jun 21, 2013 at 05:06:35PM +0000, Juan Quintanilla wrote: > Hi, > > We are running CAS 3.4.7 with an Oracle Database and for the past couple of > days we have encountered the error below for about 2 minutes or so and then > goes away. Users then are unable to login during that time. I wanted to know > if anyone would have any suggestions on the error. It seems to me that during > that time the connections are exhausted and can no longer connect. > > Below is the error along with the C3P0 settings: > > id="dataSource" > class="com.mchange.v2.c3p0.ComboPooledDataSource" > p:driverClass="oracle.jdbc.driver.OracleDriver" > p:jdbcUrl="xxxxxxx" > p:user="xxxxxxx" > p:password="xxxxxxxx" > p:initialPoolSize="25" > p:minPoolSize="0" > p:maxPoolSize="50" > p:maxIdleTimeExcessConnections="1800" > p:checkoutTimeout="900" > p:acquireIncrement="5" > p:acquireRetryAttempts="5" > p:acquireRetryDelay="10" > p:idleConnectionTestPeriod="300" > p:preferredTestQuery="select 1 from dual" > ... > 2013-06-21 09:20:09,418 ERROR [org.hibernate.util.JDBCExceptionReporter] - > <An attempt by a client to checkout a Connection has timed out.>
AFAIK, checkoutTimeout value unit is miliseconds, so maybe you could increase it to a higher value. -- ----------------------- Alberto Cabello Sánchez albe...@unex.es -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
