> What happens is that the broken app ends up sucking up resources for > each concurrent request being made to it which is waiting for the > db connection timeout. Usually this is set to 5-10 seconds. > This can suck up alot of resources. Memory, threads, etc.
Web server with limited request/thread count will hung if app leaks connections and workarounds will not help, it will hung later, but it can be a solution for people who want to blame pool and ignore problems in application. It moves crap from application and makes it "reusable component", is not it ? I see no problems if people want to produce crap at home, but I see no place for "Observers" in DBCP. > > 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]
