Would you mind run netstat to see what kind of connection they are, e.g.
port, host, status?
-Original Message-
From: Matt Raible [mailto:[EMAIL PROTECTED]
Sent: October 3, 2003 11:52 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
I
]
Sent: Friday, October 03, 2003 9:52 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
I tried changing the removeAbandonedTimeout to value1/value and then
to test it was working - here's what I did.
1. My app opens 2 connections to MySQL
Sorry, but I didn't see which datasource you were using. With DBCP, you
have these optional parameters:
!-- abandoned dB connections are removed and recycled --
parameter
nameremoveAbandoned/name
valuetrue/value
/parameter
!-- set the number of seconds a dB connection has been idle
not work on Tomcat 4.1.27/WinXP/JDK 1.4.2.
Thanks,
Matt
-Original Message-
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Friday, October 03, 2003 1:22 AM
To: Tomcat Users List
Subject: Re: Datasource connections not released when reloading context
Sorry, but I didn't see which datasource
-Original Message-
From: Matt Raible [mailto:[EMAIL PROTECTED]
Sent: Friday, October 03, 2003 9:52 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
I tried changing the removeAbandonedTimeout to value1/value and then
to test it was working - here's
On Wed, Oct 01, 2003 at 11:37:39AM -0500, Matt Raible wrote:
I already do this, but when I reload my context, I get two database
connections, rather than one. So each time I reload, I get an additional
connection - eventually resulting in an OutOfMemory Error (which I'm
attributing to this)
to RTFM.
Matt
-Original Message-
From: Phillip Qin [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 8:04 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
- to release your DB connections when your app is shutdown or reloaded
, 2003 8:04 AM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
- to release your DB connections when your app is shutdown or reloaded:
implement destroy method in your servlet class to close them.
- to prevent connections getting exhausted, use evictor
and nullify the data source.
-Original Message-
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: October 1, 2003 5:20 AM
To: Tomcat Users List
Subject: Re: Datasource connections not released when reloading context
actually that doesn't really close them, since it's a connection pool
: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 3:20 AM
To: Tomcat Users List
Subject: Re: Datasource connections not released when reloading context
actually that doesn't really close them, since it's a connection pool,
but it tells the connection pool that they're free
]
Sent: October 1, 2003 12:38 PM
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
I already do this, but when I reload my context, I get two database
connections, rather than one. So each time I reload, I get an additional
connection - eventually
- to release your DB connections when your app is shutdown or reloaded:
implement destroy method in your servlet class to close them.
- to prevent connections getting exhausted, use evictor if your use commons
pooling and dbcp.
-Original Message-
From: Jose Alfonso Martinez [mailto:[EMAIL
To: 'Tomcat Users List'
Subject: RE: Datasource connections not released when reloading context
- to release your DB connections when your app is shutdown or reloaded:
implement destroy method in your servlet class to close them.
- to prevent connections getting exhausted, use evictor if your use commons
13 matches
Mail list logo
