Created a little admin app to do just that, and it worked perfectly.
All the connections being shown as busy cleared right out, and only
the minimum number of idle / available connections remained.
Thanks much.
On 1/10/07, Varley, Roger [EMAIL PROTECTED] wrote:
I agree that is probably what
Perhaps I was unclear what it is I'm trying to do. I have a
connection pool set up under Tomcat 5.5, connecting to DB2 on an
iSeries box using Tomcat's DBCP. It is set up for 30 connections. I
am using Lambda Probe (a great open source Tomcat monitoring app) to
monitor the datasources. It is
It is possible that whatever procedure is responsible for checking for
abandoned connections only does so when there is actual need for a
connection, similar to how a garbage collector works to reclaim memory. If
there is no seeming stress on the connection resources then it would make
sense not
I agree that is probably what is happening, since the application has
gone idle. However, with garbage collection, while it will only
reclaim memory when necessary, there is a way to force garbage
collection. I am looking for a similar process with abandoned
database connections.
On 1/10/07,
Possible. I'll give it a try...
On 1/10/07, Varley, Roger [EMAIL PROTECTED] wrote:
I agree that is probably what is happening, since the application has
gone idle. However, with garbage collection, while it will only
reclaim memory when necessary, there is a way to force garbage
David,
Any chance you could share with me your connection pool configuration? I've
been struggling with trying to setup my own connection to our DB2 using the
jt400 jar and have not been able to find any documentation for doing this
with a DB2 connection.
Thanks,
Greg
On 1/10/07, David Uctaa
In server.xml, within GlobalNamingResources, include something like this:
Resource
auth=Container
driverClassName=com.ibm.as400.access.AS400JDBCDriver
maxActive=30
maxIdle=2
maxWait=5000
name=jdbc/something
password=password
type=javax.sql.DataSource
url=jdbc:as400://abc.def.com
Tomcat provides the removeAbandoned and removeAbandonedTimeout
parameters when setting up data sources in server.xml. But according
to the documentation I've read, abandoned connections only get closed
and recycled when available connections run low and new connections
are requested.
Is there a
