Why would you want to use a future? Say in a web application, I can't really think of a reason why I would use the future (asych) connection retrieval pattern. The # of connections is always fixed, I guess in a very high traffic environment where the # of connections is the pool are used up, calling via a future will block he request until a connection frees up right?
Could you also do this: Send a sql query to the pool that you want to execute in the beginning of the page, but you don't really care about the return value until the end so you can let it go and then at the bottom you call .get(), is that possible? On Sun, Mar 25, 2012 at 6:41 PM, Konstantin Kolinko <knst.koli...@gmail.com>wrote: > 2012/3/26 S Ahmed <sahmed1...@gmail.com>: > > Is the jdbc pool somehow married to tomcat or can I use it with other > > containers potentially? ( > > 1. You certainly can use it with other containers. > But it depends on Tomcat version of logging library (That is > tomcat-juli.jar). You have to copy that jar as well. > > > >> http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html) > > 2. The above link is obsolete. > > The current version of this pool implementation comes bundled with > Tomcat 7.0 releases. The correct documentation is here: > > http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html > > Best regards, > Konstantin Kolinko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
