On 6/27/2012 8:35 PM, Christopher Schultz wrote:
100 active db connections sounds like a lot. Do you really need to
support 100 simultaneous connections to your database? Can your
database support that many connections with active queries from each?
Do you have a cluster? Remember that each
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kiran,
On 6/26/12 7:24 PM, Kiran Badi wrote:
Resource name=jdbc/mysitedb auth=Container
type=javax.sql.DataSource maxActive=100 maxIdle=30
maxWait=1
100 active db connections sounds like a lot. Do you really need to
support 100 simultaneous
在 2012-6-26，13:11，Kiran Badi ki...@poonam.org 写道：
Hi All,
While testing the pagination links ,I am getting below error,
SEVERE: null
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool
error Timeout waiting for idle object
at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kiran,
On 6/26/12 1:11 AM, Kiran Badi wrote:
While testing the pagination links ,I am getting below error,
SEVERE: null org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot
get a connection, pool error Timeout waiting for idle object
Probably
On 6/26/2012 12:09 PM, Steven Sinclair wrote:
You can use java jmx console to monitor the number of db connections.
Thanks Steven, I will check this.Actually servlet was leaking connection
and I had forgot to close connection.Fixed it now.
But I still need to monitor DB side.I will check jmx
Probably waited too long for a connection. What does your pool
configuration look like? Look in META-INF/context.xml or, I suppose, in
conf/server.xml for Resource elements.
Resource name=jdbc/mysitedb auth=Container
type=javax.sql.DataSource
maxActive=100 maxIdle=30
Hi All,
While testing the pagination links ,I am getting below error,
SEVERE: null
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection,
pool error Timeout waiting for idle object
at
org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)
