Im not an expert on this but i thought that the pool will cache connections that you have created. Maybe someone can clarify this.
Have a look at this http://onjava.com/pub/a/onjava/2006/04/19/database-connection-pooling-with-tomcat.html?page=2 On Wed, Sep 9, 2009 at 9:01 AM, Chris Wiley <cwile...@comcast.net> wrote: > Hello, > I have a web app I have developed under Tomcat 6.0.18 and have added in the > dbcp system. As it stands now, It wants to make connections only after the > first request to the app. I want the dbcp system to initialize x number of > connections on app/server startup. I know if I want to initialize things > on > startup I include the <load-on-startup>1</load-on-startup> in the web.xml > for the app; which will load the servlet and execute what's in the init > method. My question is this: Am I to assume that I need to OPEN and CLOSE > x > number of connections in the init section of the servlet to load the pool > with live connections? Otherwise, I don't see how it will create those > connections and load the pool on startup. I seem to be missing or > overlooking a method call in the api that will actually load the pool with > live connections. Not sure if it makes a difference, but I also have the > dbcp being set up in a ServletContextListener. > > Any Help is greatly appreciated, have spent to much time on this trying to > get it to work like I want or as it's supposed to. > > Thanks! > Chris > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
