Hi,
I'm using appfuse 2.x.
I'm getting connection pool exhausted error after a few logins. I was
simply logging out and logging in with a single browser.
My applicationContext-resources.xml has the following:
<bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<property name="driverClassName" value="${jdbc.driverClassName}"/>
<property name="url" value="${jdbc.url}"/>
<property name="username" value="${jdbc.username}"/>
<property name="password" value="${jdbc.password}"/>
<property name="maxActive" value="10"/>
<property name="maxWait" value="60"/>
<property name="poolPreparedStatements" value="true"/>
<property name="defaultAutoCommit" value="true"/>
</bean>
My web.xml has the following:
<session-config>
<session-timeout>30</session-timeout>
</session-config>
I have also tried c3p0 as as suggested in one of the thread. When I use
this, after after a few logins, the browser just hangs (apparently server
is waiting for more connection).
Is this because leaking hibernate sessions? What is the hibernate session
closing policy? and where this is specified?
Please help! Thanks in advance!!
Environment:
-------------
Windows, Tomcat 6, appfuse.version-2.0.2, spring.version-2.5.4
BTW I was able to reproduce the same in jetty as well.
Shan
--
View this message in context:
http://www.nabble.com/connection-pool-exhausted-error-tp22093714s2369p22093714.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
For additional commands, e-mail: users-h...@appfuse.dev.java.net
