> > But in a production environment where I host the applications, not write > them, I don't want to be called at 2PM on a Sunday to reboot the app > server > if a customer's application stops working because their bad code exhausted > their db connection pool. > > I really think this feature is important. If you don't need it, don't > enable it. In my current project we have somewhere close to a million lines of code. Problems popup. We made resource management magical. We inspect the returning thread of each request and make sure that it has released its resources. We can handle bad code (which does happen when you are moving fast).
We found that we had to have an option to turn off the background connection reaper for standalone applications that need connections for extended periods of time and we came up with another solution. . . . Aaron -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
