prashubk
asked on
com.mchange.v2.c3p0.ComboPooledDataSource
Hi Experts,
i keep getting "Connection Time out" while obtaining a connection using following datasource setup. I open the connection,update a table immediately,close the connection ( no looping or no complex logic written after opening a connection).Not sure why.I'm not getting it consistently rather i get it once in a while.Experts please have your say on this and please guide me how to go about resolving this.
Or is there some property i'm missing from my datasource definition
i keep getting "Connection Time out" while obtaining a connection using following datasource setup. I open the connection,update a table immediately,close the connection ( no looping or no complex logic written after opening a connection).Not sure why.I'm not getting it consistently rather i get it once in a while.Experts please have your say on this and please guide me how to go about resolving this.
Or is there some property i'm missing from my datasource definition
<bean id="dataSource" class="com.mchange.v2.c3p0.ComboPooledDataSource" destroy-method="close">
<property name="driverClass">
<value>${db.driver}</value>
</property>
<property name="jdbcUrl">
<value>${db.connection.uri}</value>
</property>
<property name="user">
<value>${db.username}</value>
</property>
<property name="password">
<value>${db.password}</value>
</property>
<property name="initialPoolSize">
<value>0</value>
</property>
<property name="minPoolSize">
<value>0</value>
</property>
<property name="maxPoolSize">
<value>80</value>
</property>
<property name="acquireIncrement">
<value>1</value>
</property>
<property name="maxStatements">
<value>4000</value>
</property>
<property name="numHelperThreads">
<value>11</value>
</property>
</bean>
are you sure you are closing connections
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks all,Hi Murali i tried this in my local machine it dint time out.Let me see it in SIT and come back if i face this issue again.