I don't have time to run this down today but this behavior is most likely
caused by DBBroker's singleton implementation.
DBBroker.getInstance caches a global instance of DBBroker in a class static
variable. Since I assume that DBBroker is loaded as a system class, unless
the VM instance is cycled you'll always be looking at the same copy of the
class info and, therefore, the same static variable.
If this is a serious problem, one solution may be to have an explicit
tear-down of the connection pool when Turbine shuts down. Probably want to
do this anyway because, as I noted in a previous mail, the pool currently
shuts itself down in DBBroker's finalize() method which is a bad idea.
I'll have some more time soon to look at this in more detail...
cheers,
PaulO.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Frank Conradie
Sent: Thursday, August 31, 2000 1:05 PM
To: Turbine
Cc: Leon Messerschmidt
Subject: Re: Connections persisting across servlet engine restarts...?
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
[snip]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
