I really agree on the fact that connection pools need connection validation on return or on borrow. A connection pool without connection validation isnt worth much. But its certainly the last step to do while creating an application. The last fine tuning before the app goes live. Not the first thing to setup. Because the underluying functionality might change one needs to carefully test that the applied parameters is working and not trust a connection pool template as suggested by the comments on this blog entry!
Database Connection Pooling In Grails – solving the idle timeout issue | Javalobby.
Post a Comment