You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by paolo <ma...@gmail.com> on 2007/04/06 11:58:32 UTC
pool exhausted
Hi,
I get this error:
com.ibatis.dao.client.DaoException: Failed to execute queryForObject - id
[id] parameterObject
Cause: org.apache.commons.dbcp.SQLNestedException: Cannot get a connection,
pool exhausted
Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot get a
connection, pool exhausted
at
com.ibatis.dao.client.template.SqlMapDaoTemplate.queryForObject(SqlMapDaoTemplate.java:164)
I don't know exactly when it occurs, I have a web application deployed and
sometimes
I see the error in log.
My configuration is:
<transactionManager type="JDBC">
<dataSource type="DBCP">
<property name="driverClassName" value="${database.driver}"/>
<property name="url" value="${database.url}"/>
<property name="username" value="${database.username}"/>
<property name="password" value="${database.password}"/>
<property name="maxActive" value="10"/>
<property name="maxIdle" value="5"/>
<property name="maxWait" value="60000"/>
<property name="logAbandoned" value="false"/>
<property name="removeAbandoned" value="true"/>
<property name="removeAbandonedTimeout" value="50000"/>
<property name="Driver.DriverSpecificProperty"
value="SomeValue"/>
</dataSource>
</transactionManager>
I have to say that:
everytime I use startTransaction() method I use endTransaction() in a
finally block.
I don't use openSession or other methods to open a session.
I execute all other queries using queryForObject() or queryForList() Ibatis
methods.
I tried to increase maxActive parameter but I don't know if this solve the
problem.
Any ideas?
Thanks a lot in advance
--
View this message in context: http://www.nabble.com/pool-exhausted-tf3536048.html#a9870107
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
RE: pool exhausted
Posted by "James, Steven" <st...@logicacmg.com>.
when i have seen these problems before it is usually because you have more than one sqlmapclient so check to see if you are creating more than one
or if this can happen in your code.
-----Original Message-----
From: paolo [mailto:mainades@gmail.com]
Sent: Fri 06/04/2007 11:58
To: user-java@ibatis.apache.org
Subject: pool exhausted
Hi,
I get this error:
com.ibatis.dao.client.DaoException: Failed to execute queryForObject - id
[id] parameterObject
Cause: org.apache.commons.dbcp.SQLNestedException: Cannot get a connection,
pool exhausted
Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot get a
connection, pool exhausted
at
com.ibatis.dao.client.template.SqlMapDaoTemplate.queryForObject(SqlMapDaoTemplate.java:164)
I don't know exactly when it occurs, I have a web application deployed and
sometimes
I see the error in log.
My configuration is:
<transactionManager type="JDBC">
<dataSource type="DBCP">
<property name="driverClassName" value="${database.driver}"/>
<property name="url" value="${database.url}"/>
<property name="username" value="${database.username}"/>
<property name="password" value="${database.password}"/>
<property name="maxActive" value="10"/>
<property name="maxIdle" value="5"/>
<property name="maxWait" value="60000"/>
<property name="logAbandoned" value="false"/>
<property name="removeAbandoned" value="true"/>
<property name="removeAbandonedTimeout" value="50000"/>
<property name="Driver.DriverSpecificProperty"
value="SomeValue"/>
</dataSource>
</transactionManager>
I have to say that:
everytime I use startTransaction() method I use endTransaction() in a
finally block.
I don't use openSession or other methods to open a session.
I execute all other queries using queryForObject() or queryForList() Ibatis
methods.
I tried to increase maxActive parameter but I don't know if this solve the
problem.
Any ideas?
Thanks a lot in advance
--
View this message in context: http://www.nabble.com/pool-exhausted-tf3536048.html#a9870107
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.