Re: Datasource connections not released when reloading context

2003-10-06 Thread Jose Alfonso Martinez
nal 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"

RE: Datasource connections not released when reloading context

2003-10-06 Thread Phillip Qin
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

RE: Datasource connections not released when reloading context

2003-10-03 Thread Matt Raible
ain. Matt -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 1 and then to test

RE: Datasource connections not released when reloading context

2003-10-03 Thread Matt Raible
ing does 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

Re: Datasource connections not released when reloading context

2003-10-03 Thread Adam Hardy
Sorry, but I didn't see which datasource you were using. With DBCP, you have these optional parameters: removeAbandoned true removeAbandonedTimeout 60 logAbandoned true I think if you set the timeout to 1 or 2, then you may see a stacktrace from abandoned connection

Re: Datasource connections not released when reloading context

2003-10-02 Thread Jose Alfonso Martinez
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 t

RE: Datasource connections not released when reloading context

2003-10-01 Thread Phillip Qin
ECTED] 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 additiona

RE: Datasource connections not released when reloading context

2003-10-01 Thread Matt Raible
riginal Message- From: 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 con

RE: Datasource connections not released when reloading context

2003-10-01 Thread Phillip Qin
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

Re: Datasource connections not released when reloading context

2003-10-01 Thread Adam Hardy
ent: 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: implement destroy method in your servlet class to close them. - to prevent connect

Re: Datasource connections not released when reloading context

2003-10-01 Thread Adam Hardy
or tell me 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

RE: Datasource connections not released when reloading context

2003-09-29 Thread Matt Raible
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 if y

RE: Datasource connections not released when reloading context

2003-09-29 Thread Phillip Qin
- 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