When you get a "DBCP object created..." message then there should also be a stacktrace be written. With version 1.1 the message goes to stdout and the stacktrace to stderr. In the nightly builds they go both go to stderr.

The stacktrace displays the location where is abandoned connection was borrowed.

The removeAbandoned parameter is for removing the active connections.
Idle connections are removed with "minEvictableIdleTimeMillis".

-- Dirk

Sheng Huang wrote:

I have an application running on Tomcat 4.1.18 with dbcp. My configuration
parameters is as follows:
maxActive 4
maxIdle 2
maxWait -1 removeAbandoned 60
logAbandoned true


When I deployed it on a slow machine, a lot of times it will display
We have a connection pool and it has 4 max active connections.
We have a connection pool and it has 2 max idle connections.
We have a connection pool and it has 4 active connections.
We have a connection pool and it has 0 idle connections.
Then the application just stalls since no more new connections can be made
(maxActive=active). I checked the log and saw a lot of "DBCP object created 2004-03-22 12:43:32 by the following code was never
closed" followed by "Already closed". I guess there are some inactive
connections are recycled.
Is there a way that I can find out which application methods are holding
these active connections? Should these active connections also have a
timeout value? Thank you very much.
Best regards,
Sheng




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to