Leon and I have noticed the same behaviour (we only have a 4 concurrent user
Interbase license!) - just haven't had time to look into it yet. I will ask
Leon to have a look first thing tomorrow morning (African time). In the mean
time, if you find out anything, please let us know.
Frank
----- Original Message -----
From: "Jeff Brekke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 31, 2000 9:49 PM
Subject: Connections persisting across servlet engine restarts...?
We're seeing behavior I can't explain: We are using the connection pooling,
and when the servlet engine restarts, due to say a jar/class change, the
connections that were in the pool are still there, but not used. It seems
as
if a new pool is created, which is correct, but the old one is never
destoyed
properly ( or the connections are not closed properly ). I've looked
through
the code for DBBroker/ConnectionPool and all seems to be properly done. If
I
stop/kill the app server, the connections are closed. Anyone have an idea?
I've tried this on Tomcat and JServ, both exhibit the same behavior.
jb
Jeff Brekke
mailto:[EMAIL PROTECTED]
http://sites.netscape.net/ekkerbj
____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at
http://home.netscape.com/webmail
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
