Hi Guys,
Currently I am using 5.0.5 in production. I was trying to upgrade to 5.0.15 or 5.0.16.
I made necessary changes to server.xml to create informix DBCP. Unfortunately, I am
getting Connection Pool Exhausted error while trying to obtain the connection from
Datasource. Is it a bug in these
Hmm maybe you are not returning connections after using them ?
In the tomcat docs they do give a pattern you could use in your code, like
try {
}catch(SQLException e) {
}finally {
try {
//Perform your close statements here.
}catch(SQLException e) {
}
}
HIH .
Kausik Dey wrote:
Hi Guys,
Currently I am using 5.0.5 in production. I was trying to upgrade to 5.0.15 or 5.0.16.
I made necessary changes to server.xml
to create informix DBCP. Unfortunately, I am getting Connection
Pool Exhausted error while trying to obtain the connection
from Datasource.
Isn't removeAbandoned deprecated ? If so is it still usable ?
Hmm... are you getting the error right away or only after a few requests?
Hard to say anything without further information. It is always a good
idea to make sure you properly close all Statements, ResultSets anc
Connections
: Monday, December 15, 2003 8:44 PM
Subject: Re: Tomcat 5.0.16 DBCP Connection Pool Exhausted Error
Isn't removeAbandoned deprecated ? If so is it still usable ?
Hmm... are you getting the error right away or only after a few
requests?
Hard to say anything without further information
Hi!
Kwok Peng Tuck wrote:
Isn't removeAbandoned deprecated ? If so is it still usable ?
I can't find a word about it being deprecated on
http://jakarta.apache.org/commons/dbcp/configuration.html
I am using this parameter quite successfully.
Phil
This is where I saw it :
http://jakarta.apache.org/commons/dbcp/apidocs/org/apache/commons/dbcp/AbandonedConfig.html
But I think the code is still in there, just marked as deprecated :D
Philipp Taprogge wrote:
Hi!
Kwok Peng Tuck wrote:
Isn't removeAbandoned deprecated ? If so is it still
