> I agree that this is an education/policy issue. But sometimes you need > a stop gap solution to keep something running while the customer fixes > the problem. > > I would like to see this stop gap solution included with the DBCP release. > Along with quality docs on how to properly use a db connection pool and > a big disclaimer that the recovery of abandoned connections should only > be used as a stop gap in an emergency until the customer has time to > fix their code.
Try to implement yourself and I am sure the time to fix a problem will mean forever and crappers will blame you then server or app will crache. Do you want to blame apache for this code ? This problem redirection will not help, but if you want, you can maintain this crap yourself, but do not try to redirect this problem to apache please. > > Regards, > > Glenn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
