You should set the maxWait parameter.
On Sun, Mar 16, 2008 at 5:29 PM, rohitmp [EMAIL PROTECTED] wrote:
HI All,
I too am facing the same issue.
But in contrast i have my resource setup in context.xml only
But still tomcat is waiting indefinitely to to get a connection.
My context file
HI All,
I too am facing the same issue.
But in contrast i have my resource setup in context.xml only
But still tomcat is waiting indefinitely to to get a connection.
My context file is as below
?xml version=1.0 encoding=UTF-8?
Context path=/mycontextpath
Resource name=jdbc/connPool
Hi.
1. Please post this in a separate thread as it's a separate issue.
2. Is this happening immediately (in the first request) after start or
does it take a few requests to make it wait for a connection? If it
takes a few requests, your code is not closing connection as it should.
They
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Clay,
Clay Collier wrote:
| I'm running Tomcat 5.5.25, but I think I've found the problem. When I
| deployed the application onto the production server, the server was
| unable to set up the connection pool until I added an additional
| Resource
Hi all-
I'm running into a recurring problem with an application that uses
DBCP pooling to access a database. The application initially seems to
run fine; in the test environment, it has no problem dealing with a
large volume of connections and responds to everything the way that
you would
On Jan 27, 2008 4:32 PM, Clay Collier [EMAIL PROTECTED] wrote:
Hi all-
I'm running into a recurring problem with an application that uses
DBCP pooling to access a database. The application initially seems to
run fine; in the test environment, it has no problem dealing with a
large volume of
What version of Tomcat are you running? If (as is likely currently)
it is one that bundles Commons Pool 1.3, there is something funny
going on because the line number where wait on borrowObject is
occurring in the thread dumps would indicate that
a) the pool is exhausted and
b) the maxWait
