> > So, what are these more effective ways to prevent pages? > > Not deploying code with resource leaks, training developers on proper > resource cleanup, calling developers responsible for the resource leak > in > the middle of the night to help you fix the problem, etc.
I forgot one: If apps are leaking database connections, just setup a different DataSource for each app. That way they will only affect themselves and not bring down other apps. The database will eventually close connections on its own so the only real issue is the leak in the apps. You could go even further and only give suspect applications a very limited number of connections in the pool (ie. 2) until they prove they're not leaking connections. This is much more of a policy/management problem than one that can be solved in DBCP. David __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
