[Proxool-developer] Re: Proxool and web apps

[Bill H. <bi...@lo...>]

Martin,

On Wed, 2002-12-11 at 16:57, Martin Crawford wrote:

> What I found after numerous
> unloadings/reloadings of my web app (love the development cycle) is that
> proxool classes that were loaded were keeping alive Connections to my
> database from the previous installation, and then opening a whole new set
> when I reload my web app again 

We added a ReloadMonitor in 0.5 that should fix that. As soon as Proxool
is reloaded then it closes all the old connection pools. Can you try out
0.5 and let us know if it fixes it?

> My thought is that proxool should give up if it cannot connect a certain
> number of times while trying to keep some connections idle. It should still
> reattempt a connection if the client code asks for it again though. Makes
> sense?

Sometimes when a database is down it is nice to see Proxool
automatically pick up the connections when it comes back up again
though. I suppose this should be a configurable nice-to-have.

It shouldn't actually be a very intensive background process. By
default, the house keeping thread runs every 30 seconds and if it fails
to make the first spare connection it gives up on the rest. So the only
process activity is to attempt to build a connection once every 30
seconds. And if the database is down then this activity is less than you
would normally experience. 

But feel free to add it as a feature request if you think it will be
useful.
 
> Also documentation should probably indicate that proxool should be deployed
> to commons folder (or set in the main classpath) for web apps.

If you upgrade to 0.5 then this shouldn't be true.

> Just some input.

Always welcome, Martin.

Bill