Subject Tomcat contexts and pooled connections
Author Natal Vande Casteele
Hello,

We're currently using the latest Firebird-Java driver release (with
pooled connections) with Firebird 1.0.3 CS and Tomcat 4.

Everything is working smoothly, except for the fact that when we restart
a servlet context (via the Tomcat application manager), the connections
are not returned to the pool (a 'netstat -a | grep "gds"' confirms
this). Restarting the complete tomcat server solves the problem (returns
all connections) but this is not desired as all our servlet-contexts
will be offline for a second or 5. Reloading a context via the
application manager is almost instantaneous.

Is there a way to return the database connections to the pool when the
servlet context is reloaded? I presume they're removed from memory and
reloaded but different from restarting the tomcat server, the
connections aren't returned.

Greetings,
Natal Vande Casteele
Software Engineer
Pocket and Soul